[one-users] Can´t start VMware ESX 3.5 with OpenNebula
Javi Gironda Diaz
javigironda at hotmail.com
Tue Feb 9 09:34:36 PST 2010
Hi Tino,
But i can´t introduced any string like INIT, when executed $ONE_LOCATION/lib/mads/one_im_vmware the comand return the prompt, i can´t introduced anything.
what i can do?
A lot of thanks, sincerely.
> From: tinova at fdi.ucm.es
> Date: Tue, 9 Feb 2010 18:10:14 +0100
> Subject: Re: [one-users] Can´t start VMware ESX 3.5 with OpenNebula
> To: javigironda at hotmail.com
> CC: users at lists.opennebula.org
>
> Hi Javi,
>
> Sweet, thanks for the log. It seems that the drivers are not properly loaded:
>
> ---8<--
> Tue Feb 9 12:27:03 2010 [VMM][I]: Loading Virtual Machine Manager drivers.
> Tue Feb 9 12:27:03 2010 [VMM][I]: Loading driver: vmm_vmware (XML)
> Tue Feb 9 12:27:06 2010 [MAD][E]: MAD did not answer INIT command
> Tue Feb 9 12:27:06 2010 [InM][I]: Loading Information Manager drivers.
> Tue Feb 9 12:27:06 2010 [InM][I]: Loading driver: im_vmware
> Tue Feb 9 12:27:07 2010 [MAD][E]: MAD did not answer INIT command
> ---->8--
>
> Ok, let's try again running the driver by hand. Execute
>
> --8<--
> $ONE_LOCATION/lib/mads/one_im_vmware
> --->8--
>
> This should wait for a standar input string (it shouldn't return
> prompt). If you type in INIT, an INIT SUCCESS should come back (this
> is what the OpenNebula core is not getting).
>
> --8<--
> $ONE_LOCATION/lib/mads/one_im_vmware
> INIT
> INIT SUCCESS
> --->8--
>
> Is this working for you,
>
> -Tino
>
> --
> Constantino Vázquez, Grid & Virtualization Technology
> Engineer/Researcher: http://www.dsa-research.org/tinova
> DSA Research Group: http://dsa-research.org
> Globus GridWay Metascheduler: http://www.GridWay.org
> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
>
>
>
> On Tue, Feb 9, 2010 at 5:44 PM, Javi Gironda Diaz
> <javigironda at hotmail.com> wrote:
> > OK,
> >
> > it is the full content of oned.log (I cutt some of the repeated lines from
> > the end to taht I should take in the maximum size of mail):
> >
> >
> > Tue Feb 9 12:27:01 2010 [ONE][I]: Init OpenNebula Log system
> > Tue Feb 9 12:27:01 2010 [ONE][I]: Log Level: 3
> > [0=ERROR,1=WARNING,2=INFO,3=DEBUG]
> > Tue Feb 9 12:27:01 2010 [ONE][I]:
> > ----------------------------------------------
> > Tue Feb 9 12:27:01 2010 [ONE][I]: OpenNebula Configuration File
> > Tue Feb 9 12:27:01 2010 [ONE][I]:
> > ----------------------------------------------
> > Tue Feb 9 12:27:01 2010 [ONE][I]:
> > --------------------------------------------
> > DEBUG_LEVEL=3
> > HM_MAD=EXECUTABLE=one_hm
> > HOST_MONITORING_INTERVAL=60
> > IM_MAD=ARGUMENTS=--username root --password
> > 123456,EXECUTABLE=one_im_vmware,NAME=im_vmware
> > MAC_PREFIX=00:03
> > MANAGER_TIMER=30
> > NETWORK_SIZE=254
> > PORT=2633
> > TM_MAD=ARGUMENTS=tm_nfs/tm_nfs.conf,EXECUTABLE=one_tm,NAME=tm_nfs
> >
> > TM_MAD=ARGUMENTS=tm_vmware/tm_vmware.conf,EXECUTABLE=one_tm,NAME=tm_vmware
> > VM_DIR=/home/one/nebula/var
> > VM_MAD=ARGUMENTS=--username root --password
> > 123456,EXECUTABLE=one_vmm_vmware,NAME=vmm_vmware,TYPE=xml
> > VM_POLLING_INTERVAL=60
> > --------------------------------------------
> > Tue Feb 9 12:27:01 2010 [VMM][I]: Starting Virtual Machine Manager...
> > Tue Feb 9 12:27:01 2010 [LCM][I]: Starting Life-cycle Manager...
> > Tue Feb 9 12:27:01 2010 [InM][I]: Starting Information Manager...
> > Tue Feb 9 12:27:01 2010 [TrM][I]: Starting Transfer Manager...
> > Tue Feb 9 12:27:01 2010 [DiM][I]: Starting Dispatch Manager...
> > Tue Feb 9 12:27:01 2010 [ReM][I]: Starting Request Manager...
> > Tue Feb 9 12:27:01 2010 [ReM][I]: Starting XML-RPC server, port 2633 ...
> > Tue Feb 9 12:27:01 2010 [VMM][I]: Virtual Machine Manager started.
> > Tue Feb 9 12:27:01 2010 [LCM][I]: Life-cycle Manager started.
> > Tue Feb 9 12:27:01 2010 [TrM][I]: Transfer Manager started.
> > Tue Feb 9 12:27:01 2010 [DiM][I]: Dispatch Manager started.
> > Tue Feb 9 12:27:01 2010 [ReM][I]: Request Manager started.
> > Tue Feb 9 12:27:01 2010 [HKM][I]: Starting Hook Manager...
> > Tue Feb 9 12:27:01 2010 [InM][I]: Information Manager started.
> > Tue Feb 9 12:27:01 2010 [HKM][I]: Hook Manager started.
> > Tue Feb 9 12:27:03 2010 [VMM][I]: Loading Virtual Machine Manager drivers.
> > Tue Feb 9 12:27:03 2010 [VMM][I]: Loading driver: vmm_vmware (XML)
> > Tue Feb 9 12:27:06 2010 [MAD][E]: MAD did not answer INIT command
> > Tue Feb 9 12:27:06 2010 [InM][I]: Loading Information Manager drivers.
> > Tue Feb 9 12:27:06 2010 [InM][I]: Loading driver: im_vmware
> > Tue Feb 9 12:27:07 2010 [MAD][E]: MAD did not answer INIT command
> > Tue Feb 9 12:27:07 2010 [TM][I]: Loading Transfer Manager drivers.
> > Tue Feb 9 12:27:07 2010 [VMM][I]: Loading driver: tm_nfs
> > Tue Feb 9 12:27:07 2010 [TM][I]: Driver tm_nfs loaded.
> > Tue Feb 9 12:27:07 2010 [VMM][I]: Loading driver: tm_vmware
> > Tue Feb 9 12:27:08 2010 [TM][I]: Driver tm_vmware loaded.
> > Tue Feb 9 12:27:08 2010 [HKM][I]: Loading Hook Manager driver.
> > Tue Feb 9 12:27:09 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 12:27:09 2010 [HKM][I]: Hook Manager loaded
> > Tue Feb 9 12:27:20 2010 [ReM][D]: HostInfo method invoked
> > Tue Feb 9 12:27:20 2010 [ReM][D]: HostDelete method invoked
> > Tue Feb 9 12:27:22 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 12:28:08 2010 [ReM][D]: HostAllocate method invoked
> > Tue Feb 9 12:28:11 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 12:28:22 2010 [ReM][D]: HostInfo method invoked
> > Tue Feb 9 12:29:40 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:29:40 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:30:32 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:30:32 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:31:25 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:31:25 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:32:20 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:32:20 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:33:14 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:33:14 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:34:08 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:34:08 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:35:02 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:35:02 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:35:56 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:35:56 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:36:50 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:36:50 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:37:44 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:37:44 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:38:37 2010 [InM][I]: Monitoring host 158.49.245.220 (5)
> > Tue Feb 9 12:38:37 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:38:59 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 12:39:06 2010 [ReM][D]: HostInfo method invoked
> > Tue Feb 9 12:39:06 2010 [ReM][D]: HostDelete method invoked
> > Tue Feb 9 12:39:37 2010 [ReM][D]: HostAllocate method invoked
> > Tue Feb 9 12:39:41 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 12:40:29 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 12:41:17 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:41:17 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:42:12 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:42:12 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:43:05 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:43:05 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:43:58 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:43:58 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:44:51 2010 [InM][I]: --Mark--
> > Tue Feb 9 12:44:51 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:44:51 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:44:51 2010 [VMM][I]: --Mark--
> > Tue Feb 9 12:45:44 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:45:44 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:46:37 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:46:37 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:47:30 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:47:30 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:48:24 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:48:24 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:49:18 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:49:18 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:50:12 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:50:12 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:51:07 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:51:07 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:52:01 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:52:01 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:52:55 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:52:55 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:53:50 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:53:50 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:54:38 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 12:54:44 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:54:44 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:55:38 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:55:38 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:56:32 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:56:32 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:57:27 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:57:27 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:58:22 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:58:22 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 12:59:15 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 12:59:15 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:00:08 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:00:08 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:01:03 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:01:03 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:01:57 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:01:57 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:02:51 2010 [InM][I]: --Mark--
> > Tue Feb 9 13:02:51 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:02:51 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:02:51 2010 [VMM][I]: --Mark--
> > Tue Feb 9 13:03:45 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:03:45 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:04:39 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:04:39 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:05:32 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:05:32 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:06:26 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:06:26 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:07:20 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:16:20 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:16:20 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:17:14 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:17:14 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:18:08 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:18:08 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:19:02 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:19:02 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:19:56 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:19:56 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:20:49 2010 [InM][I]: --Mark--
> > Tue Feb 9 13:20:49 2010 [VMM][I]: --Mark--
> > Tue Feb 9 13:20:49 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:20:49 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:21:43 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:21:43 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:22:37 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:22:37 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:23:31 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:23:31 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:24:25 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:24:25 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:25:19 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:25:19 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:26:13 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:26:13 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:27:06 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:27:06 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:27:59 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:27:59 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:28:52 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:28:52 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:29:46 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:29:46 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:30:39 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:30:39 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:31:34 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:31:34 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:32:28 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:32:28 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:33:22 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:33:22 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:34:16 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:34:16 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:35:10 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:35:10 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:36:04 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:36:04 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:36:58 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:48:38 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:48:38 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:49:18 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 13:49:31 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:49:31 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:50:24 2010 [InM][I]: Monitoring host ESX-nebula (6)
> > Tue Feb 9 13:50:24 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:50:58 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 13:51:06 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 13:51:11 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 13:51:11 2010 [ReM][D]: HostInfo method invoked
> > Tue Feb 9 13:51:12 2010 [ReM][D]: HostDelete method invoked
> > Tue Feb 9 13:52:43 2010 [ReM][D]: HostAllocate method invoked
> > Tue Feb 9 13:52:48 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 13:52:54 2010 [ReM][D]: HostInfo method invoked
> > Tue Feb 9 13:53:54 2010 [ReM][D]: HostPoolInfo method invoked
> > Tue Feb 9 13:53:59 2010 [InM][I]: Monitoring host ESX-nebula (7)
> > Tue Feb 9 13:53:59 2010 [InM][E]: Could not find information driver
> > im_vmware
> > Tue Feb 9 13:54:54 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >
> > Thanks.
> >
> >> From: tinova at fdi.ucm.es
> >> Date: Tue, 9 Feb 2010 17:28:03 +0100
> >> Subject: Re: [one-users] Can´t start VMware ESX 3.5 with OpenNebula
> >> To: javigironda at hotmail.com
> >> CC: users at lists.opennebula.org
> >>
> >> Hi,
> >>
> >> I will need the whole file, or at least the first, say, 200 lines.
> >> There is where driver loading information shows.
> >>
> >> Regards,
> >>
> >> -Tino
> >>
> >> --
> >> Constantino Vázquez, Grid & Virtualization Technology
> >> Engineer/Researcher: http://www.dsa-research.org/tinova
> >> DSA Research Group: http://dsa-research.org
> >> Globus GridWay Metascheduler: http://www.GridWay.org
> >> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
> >>
> >>
> >>
> >> On Tue, Feb 9, 2010 at 5:21 PM, Javi Gironda Diaz
> >> <javigironda at hotmail.com> wrote:
> >> > Sorry,
> >> >
> >> > the content of $ONE_LOCATION/var/oned.log is:
> >> >
> >> >
> >> > Tue Feb 9 17:51:50 2010 [ReM][D]: HostPoolInfo method invoked
> >> > Tue Feb 9 17:52:18 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:52:18 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:53:12 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:53:12 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:54:05 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:54:05 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:54:57 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:54:57 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:55:51 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:55:51 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:56:43 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:56:43 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:57:35 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:57:35 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:58:28 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:58:28 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> > Tue Feb 9 17:59:22 2010 [InM][I]: Monitoring host ESX-nebula (7)
> >> > Tue Feb 9 17:59:22 2010 [InM][E]: Could not find information driver
> >> > im_vmware
> >> >
> >> > The logs shows the same as before, not finding the driver information
> >> >
> >> > Thanks.
> >> >
> >> >
> >> >> Hi,
> >> >>
> >> >> Ok, configuration seems ok. Can you send the oned.log through?
> >> >>
> >> >> Thanks,
> >> >>
> >> >> -T
> >> >>
> >> >> --
> >> >> Constantino Vázquez, Grid & Virtualization Technology
> >> >> Engineer/Researcher: http://www.dsa-research.org/tinova
> >> >> DSA Research Group: http://dsa-research.org
> >> >> Globus GridWay Metascheduler: http://www.GridWay.org
> >> >> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
> >> >>
> >> >>
> >> >>
> >> >> On Tue, Feb 9, 2010 at 4:55 PM, Javi Gironda Diaz
> >> >> <javigironda at hotmail.com> wrote:
> >> >> > Thank you for the response.
> >> >> >
> >> >> > But the execution of $ONE_LOCATION/lib/mads/one_im_vmware don´t
> >> >> > reports
> >> >> > any
> >> >> > problem, it's executed succesfull.
> >> >> >
> >> >> > The content of $ONE_LOCATION/etc/oned.conf is:
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # OpenNebula Configuration file
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> >
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # Daemon configuration attributes
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # HOST_MONITORING_INTERVAL: Time in seconds between host
> >> >> > monitorization
> >> >> > #
> >> >> > # VM_POLLING_INTERVAL: Time in seconds between virtual machine
> >> >> > monitorization
> >> >> > #
> >> >> > # VM_DIR: Remote path to store the VM images, it should be shared
> >> >> > between
> >> >> > all
> >> >> > # the cluster nodes to perform live migrations. This variable is the
> >> >> > default
> >> >> > # for all the hosts in the cluster.
> >> >> > #
> >> >> > # PORT: Port where oned will listen for xmlrpc calls.
> >> >> > #
> >> >> > # DEBUG_LEVEL: 0 = ERROR, 1 = WARNING, 2 = INFO, 3 = DEBUG
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> >
> >> >> > HOST_MONITORING_INTERVAL = 60
> >> >> >
> >> >> > VM_POLLING_INTERVAL = 60
> >> >> >
> >> >> > VM_DIR=/home/one/nebula/var
> >> >> >
> >> >> > PORT=2633
> >> >> >
> >> >> > DEBUG_LEVEL=3
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # Physical Networks configuration
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # NETWORK_SIZE: Here you can define the default size for the virtual
> >> >> > networks
> >> >> > #
> >> >> > # MAC_PREFIX: Default MAC prefix to be used to create the
> >> >> > auto-generated
> >> >> > MAC
> >> >> > # addresses is defined here (this can be overrided by the Virtual
> >> >> > Network
> >> >> > # template)
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> >
> >> >> > NETWORK_SIZE = 254
> >> >> >
> >> >> > MAC_PREFIX = "00:03"
> >> >> >
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # Information Driver Configuration
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # You can add more information managers with different configurations
> >> >> > but
> >> >> > make
> >> >> > # sure it has different names.
> >> >> > #
> >> >> > # name : name for this information manager
> >> >> > #
> >> >> > # executable: path of the information driver executable, can be an
> >> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
> >> >> > (or
> >> >> > # /usr/lib/one/mads/ if OpenNebula was installed in /)
> >> >> > #
> >> >> > # arguments : for the driver executable, usually a probe
> >> >> > configuration
> >> >> > file,
> >> >> > # can be an absolute path or relative to
> >> >> > $ONE_LOCATION/etc
> >> >> > (or
> >> >> > # /etc/one/ if OpenNebula was installed in /)
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> >
> >> >> > #IM_MAD = [
> >> >> > # name = "im_xen",
> >> >> > # executable = "one_im_ssh",
> >> >> > # arguments = "im_xen/im_xen.conf" ]
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # VMWare Information Driver Manager sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > IM_MAD = [
> >> >> > name = "im_vmware",
> >> >> > executable = "one_im_vmware",
> >> >> > arguments = "--username root --password 123456"]
> >> >> >
> >> >> >
> >> >> > #------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # KVM Information Driver Manager sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #IM_MAD = [
> >> >> > # name = "im_kvm",
> >> >> > # executable = "one_im_ssh",
> >> >> > # arguments = "im_kvm/im_kvm.conf" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # EC2 Information Driver Manager sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #IM_MAD = [
> >> >> > # name = "im_ec2",
> >> >> > # executable = "one_im_ec2",
> >> >> > # arguments = "im_ec2/im_ec2.conf" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # Virtualization Driver Configuration
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # You can add more virtualization managers with different
> >> >> > configurations
> >> >> > but
> >> >> > # make sure it has different names.
> >> >> > #
> >> >> > # name : name of the virtual machine manager driver
> >> >> > #
> >> >> > # executable: path of the virtualization driver executable, can be
> >> >> > an
> >> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
> >> >> > (or
> >> >> > # /usr/lib/one/mads/ if OpenNebula was installed in /)
> >> >> > #
> >> >> > # arguments : for the driver executable
> >> >> > #
> >> >> > # default : default values and configuration parameters for the
> >> >> > driver,
> >> >> > can
> >> >> > # be an absolute path or relative to $ONE_LOCATION/etc
> >> >> > (or
> >> >> > # /etc/one/ if OpenNebula was installed in /)
> >> >> > #
> >> >> > # type : driver type, supported drivers: xen, kvm, xml
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> >
> >> >> > #VM_MAD = [
> >> >> > # name = "vmm_xen",
> >> >> > # executable = "one_vmm_xen",
> >> >> > # default = "vmm_xen/vmm_xen.conf",
> >> >> > # type = "xen" ]
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # KVM Virtualization Driver Manager sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #VM_MAD = [
> >> >> > # name = "vmm_kvm",
> >> >> > # executable = "one_vmm_kvm",
> >> >> > # default = "vmm_kvm/vmm_kvm.conf",
> >> >> > # type = "kvm" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # VMWare Virtualization Driver Manager sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > VM_MAD = [
> >> >> > name = "vmm_vmware",
> >> >> > executable = "one_vmm_vmware",
> >> >> > arguments = "--username root --password 123456",
> >> >> > type = "xml" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # EC2 Virtualization Driver Manager sample configuration
> >> >> > # arguments: default values for the EC2 driver, can be an absolute
> >> >> > path
> >> >> > or
> >> >> > # relative to $ONE_LOCATION/etc (or /etc/one/ if
> >> >> > OpenNebula
> >> >> > was
> >> >> > # installed in /).
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #VM_MAD = [
> >> >> > # name = "vmm_ec2",
> >> >> > # executable = "one_vmm_ec2",
> >> >> > # arguments = "vmm_ec2/vmm_ec2.conf",
> >> >> > # type = "xml" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # Transfer Manager Driver Configuration
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # You can add more transfer managers with different configurations
> >> >> > but
> >> >> > make
> >> >> > # sure it has different names.
> >> >> > # name : name for this transfer driver
> >> >> > #
> >> >> > # executable: path of the transfer driver executable, can be an
> >> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
> >> >> > (or
> >> >> > # /usr/lib/one/mads/ if OpenNebula was installed in /)
> >> >> > #
> >> >> > # arguments : for the driver executable, usually a commands
> >> >> > configuration
> >> >> > file
> >> >> > # , can be an absolute path or relative to
> >> >> > $ONE_LOCATION/etc
> >> >> > (or
> >> >> > # /etc/one/ if OpenNebula was installed in /)
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> >
> >> >> > #TM_MAD = [
> >> >> > # name = "tm_ssh",
> >> >> > # executable = "one_tm",
> >> >> > # arguments = "tm_ssh/tm_ssh.conf" ]
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # NFS Transfer Manager Driver sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > TM_MAD = [
> >> >> > # name = "tm_nfs",
> >> >> > # executable = "one_tm",
> >> >> > # arguments = "tm_nfs/tm_nfs.conf" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # VMWare Transfer Driver Manager sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > TM_MAD = [
> >> >> > name = "tm_vmware",
> >> >> > executable = "one_tm",
> >> >> > arguments = "tm_vmware/tm_vmware.conf" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # Dummy Transfer Manager Driver sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #TM_MAD = [
> >> >> > # name = "tm_dummy",
> >> >> > # executable = "one_tm",
> >> >> > # arguments = "tm_dummy/tm_dummy.conf" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > # LVM Transfer Manager Driver sample configuration
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #TM_MAD = [
> >> >> > # name = "tm_lvm",
> >> >> > # executable = "one_tm",
> >> >> > # arguments = "tm_lvm/tm_lvm.conf" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # Hook Manager Configuration
> >> >> >
> >> >> >
> >> >> > #*******************************************************************************
> >> >> > # The Driver (HM_MAD), used to execute the Hooks
> >> >> > # executable: path of the hook driver executable, can be an
> >> >> > # absolute path or relative to $ONE_LOCATION/lib/mads
> >> >> > (or
> >> >> > # /usr/lib/one/mads/ if OpenNebula was installed in /)
> >> >> > #
> >> >> > # arguments : for the driver executable, can be an absolute path or
> >> >> > relative
> >> >> > # to $ONE_LOCATION/etc (or /etc/one/ if OpenNebula was
> >> >> > installed
> >> >> > # in /)
> >> >> > #
> >> >> > # Virtual Machine Hooks (VM_HOOK) defined by:
> >> >> > # name : for the hook, useful to track the hook (OPTIONAL)
> >> >> > # on : when the hook should be executed,
> >> >> > # - CREATE, when the VM is created (onevm create)
> >> >> > # - RUNNING, after the VM is successfully booted
> >> >> > # - SHUTDOWN, after the VM is shutdown
> >> >> > # - STOP, after the VM is stopped (including VM image
> >> >> > transfers)
> >> >> > # - DONE, after the VM is deleted or shutdown
> >> >> > # command : use absolute path here
> >> >> > # arguments : for the hook. You can access to VM template variables
> >> >> > with $
> >> >> > # - $ATTR, the value of an attribute e.g. $NAME or
> >> >> > $VMID
> >> >> > # - $ATTR[VAR], the value of a vector e.g. $NIC[MAC]
> >> >> > # - $ATTR[VAR, COND], same of previous but COND select
> >> >> > between
> >> >> > # multiple ATTRs e.g. $NIC[MAC, NETWORK="Public"]
> >> >> > # remote : values,
> >> >> > # - YES, The hook is executed in the host where the VM
> >> >> > was
> >> >> > # allocated
> >> >> > # - NO, The hook is executed in the OpenNebula server
> >> >> > (default)
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> >
> >> >> > HM_MAD = [
> >> >> > executable = "one_hm" ]
> >> >> >
> >> >> > #-------------------------------- Hook Examples
> >> >> > --------------------------------
> >> >> > #VM_HOOK = [
> >> >> > # name = "dhcp",
> >> >> > # on = "create",
> >> >> > # command = "/bin/echo",
> >> >> > # arguments = "$NAME > /tmp/test.$VMID" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #VM_HOOK = [
> >> >> > # name = "ebtables",
> >> >> > # on = "running",
> >> >> > # command = "/usr/local/one/bin/set_net",
> >> >> > # arguments = '$NIC[MAC, Network = "Private"]',
> >> >> > # remote = "yes" ]
> >> >> >
> >> >> >
> >> >> > #-------------------------------------------------------------------------------
> >> >> > #VM_HOOK = [
> >> >> > # name = "mail",
> >> >> > # on = "running",
> >> >> > # command = "/usr/local/one/bin/send_mail",
> >> >> > # arguments = "$VMID $NAME",
> >> >> > # remote = "no" ]
> >> >> >
> >> >> >
> >> >> > #------------------------------------------------------------------------------
> >> >> >
> >> >> > I can´t find the problem.
> >> >> >
> >> >> > Thanks.
> >> >> >
> >> >> >
> >> >> >> Hi Javier,
> >> >> >>
> >> >> >> It seems that OpenNebula is failing to load the im_vmware driver.
> >> >> >>
> >> >> >> Try executing it by hand ($ONE_LOCATION/lib/mads/one_im_vmware),
> >> >> >> does
> >> >> >> it
> >> >> >> fail?
> >> >> >>
> >> >> >> If that doesn't give hints on what is going wrong, could you send
> >> >> >> through the $ONE_LOCATION/etc/oned.conf file, and the
> >> >> >> $ONE_LOCATION/var/oned.log?
> >> >> >>
> >> >> >> Regards,
> >> >> >>
> >> >> >> -Tino
> >> >> >>
> >> >> >> --
> >> >> >> Constantino Vázquez, Grid & Virtualization Technology
> >> >> >> Engineer/Researcher: http://www.dsa-research.org/tinova
> >> >> >> DSA Research Group: http://dsa-research.org
> >> >> >> Globus GridWay Metascheduler: http://www.GridWay.org
> >> >> >> OpenNebula Virtual Infrastructure Engine: http://www.OpenNebula.org
> >> >> >>
> >> >> >>
> >> >> >>
> >> >> >> On Tue, Feb 9, 2010 at 2:40 PM, Javi Gironda Diaz
> >> >> >> <javigironda at hotmail.com> wrote:
> >> >> >> > Hello everyone.
> >> >> >> >
> >> >> >> > I installed OpenNebula in a CentOS 5.2, which is a virtual machine
> >> >> >> > created
> >> >> >> > with VMware Wrokstation.
> >> >> >> > I also have a properly installed and running ESX 3.5, which also
> >> >> >> > is a
> >> >> >> > VMware
> >> >> >> > Workstation virtual machine.
> >> >> >> >
> >> >> >> > My problem occurs when I try to add that host to be managed by
> >> >> >> > OpenNebula on
> >> >> >> > CentOS virtual machine.
> >> >> >> >
> >> >> >> > I have obtained the certificate vmware.keystore "from arhcivo"
> >> >> >> > rui.crt
> >> >> >> > "ESX
> >> >> >> > host.
> >> >> >> >
> >> >> >> > I have followed all the steps in the guide:
> >> >> >> > http://www.opennebula.org/doku.php?id=documentation:rel1.4:vmwareg
> >> >> >> >
> >> >> >> > To create the host I used the command:
> >> >> >> >
> >> >> >> > ESX-nebula onehost add im_vmware vmm_vmware tm_ssh
> >> >> >> >
> >> >> >> > But I must be doing something wrong, because the show host
> >> >> >> > information I
> >> >> >> > get
> >> >> >> > the following:
> >> >> >> >
> >> >> >> > HOST 7 Information
> >> >> >> > ID: 7
> >> >> >> > NAME: ESX-nebula
> >> >> >> > STATE: ERROR
> >> >> >> > IM_MAD: im_vmware
> >> >> >> > VM_MAD: vmm_vmware
> >> >> >> > TM_MAD: tm_ssh
> >> >> >> >
> >> >> >> > HOST SHARES
> >> >> >> > MAX MEM: 0
> >> >> >> > USED MEM (REAL): 0
> >> >> >> > USED MEM (ALLOCATED): 0
> >> >> >> > MAX CPU: 0
> >> >> >> > USED CPU (REAL): 0
> >> >> >> > USED CPU (ALLOCATED): 0
> >> >> >> > RUNNING VMS: 0
> >> >> >> >
> >> >> >> > MONITORING INFORMATION
> >> >> >> >
> >> >> >> > ----------------------------------------------
> >> >> >> >
> >> >> >> > The output of the log "oned.log" is payable are:
> >> >> >> >
> >> >> >> >
> >> >> >> > Tue Feb 9 15:09:57 2010 [REM] [D]: hostInfo method invoked
> >> >> >> > Tue Feb 9 15:10:08 2010 [INM] [I]: Monitoring ESX host-nebula (7)
> >> >> >> > Tue Feb 9 15:10:08 2010 [INM] [E]: Could not find driver
> >> >> >> > information
> >> >> >> > im_vmware
> >> >> >> > Tue Feb 9 15:11:03 2010 [INM] [I]: Monitoring ESX host-nebula (7)
> >> >> >> > Tue Feb 9 15:11:03 2010 [INM] [E]: Could not find driver
> >> >> >> > information
> >> >> >> > im_vmware
> >> >> >> > Tue Feb 9 15:11:57 2010 [INM] [I]: Monitoring ESX host-nebula (7)
> >> >> >> > Tue Feb 9 15:11:57 2010 [INM] [E]: Could not find driver
> >> >> >> > information
> >> >> >> > im_vmware
> >> >> >> >
> >> >> >> > -----------------------------------------------
> >> >> >> >
> >> >> >> > I can´t advanced as they do not know which is the problem.
> >> >> >> >
> >> >> >> > Thanks in advance.
> >> >> >> >
> >> >> >> > A greeting.
> >> >> >> > ________________________________
> >> >> >> > ¿Quieres tener a tus amigos de Facebook en Messenger? ¡Clic AQUÍ!
> >> >> >> > _______________________________________________
> >> >> >> > Users mailing list
> >> >> >> > Users at lists.opennebula.org
> >> >> >> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >> >> >> >
> >> >> >> >
> >> >> >
> >> >> > ________________________________
> >> >> > Disfruta de un resumen diario de tu Hotmail en tu móvil Movistar.
> >> >> > ¡Accede
> >> >> > ya!
> >> >> > _______________________________________________
> >> >> > Users mailing list
> >> >> > Users at lists.opennebula.org
> >> >> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >> >> >
> >> >> >
> >> >
> >> > ________________________________
> >> > Navega con el navegador más seguro de todos. ¡Descárgatelo ya!
> >> > _______________________________________________
> >> > Users mailing list
> >> > Users at lists.opennebula.org
> >> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >> >
> >> >
> >
> > ________________________________
> > Navega con el navegador más seguro de todos. ¡Descárgatelo ya!
> > _______________________________________________
> > Users mailing list
> > Users at lists.opennebula.org
> > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
> >
> >
_________________________________________________________________
¿Aún no sabes qué móvil eres? ¡Descúbrelo aquí!
http://www.quemovileres.com/
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.opennebula.org/pipermail/users-opennebula.org/attachments/20100209/2a60e45a/attachment-0001.htm>
More information about the Users
mailing list