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