<html>
<head>
<style><!--
.hmmessage P
{
margin:0px;
padding:0px
}
body.hmmessage
{
font-size: 10pt;
font-family:Verdana
}
--></style>
</head>
<body class='hmmessage'>
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 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 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 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 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 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 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 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 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 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 any<br>> > problem, it's executed succesfull.<br>> ><br>> > The content of $ONE_LOCATION/etc/oned.conf is:<br>> ><br>> ><br>> ><br>> > #*******************************************************************************<br>> > # OpenNebula Configuration file<br>> > #*******************************************************************************<br>> ><br>> > #*******************************************************************************<br>> > # Daemon configuration attributes<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 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>> > 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>> > # Physical Networks configuration<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 auto-generated<br>> > MAC<br>> > # addresses is defined here (this can be overrided by the Virtual Network<br>> > # template)<br>> > #*******************************************************************************<br>> ><br>> > NETWORK_SIZE = 254<br>> ><br>> > MAC_PREFIX = "00:03"<br>> ><br>> > #*******************************************************************************<br>> > # Information Driver Configuration<br>> > #*******************************************************************************<br>> > # You can add more information managers with different configurations 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 (or<br>> > # /etc/one/ if OpenNebula was installed in /)<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>> > # VMWare Information Driver Manager sample configuration<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>> > # KVM Information Driver Manager sample configuration<br>> > #-------------------------------------------------------------------------------<br>> > #IM_MAD = [<br>> > # name = "im_kvm",<br>> > # executable = "one_im_ssh",<br>> > # arguments = "im_kvm/im_kvm.conf" ]<br>> > #-------------------------------------------------------------------------------<br>> ><br>> > #-------------------------------------------------------------------------------<br>> > # EC2 Information Driver Manager sample configuration<br>> > #-------------------------------------------------------------------------------<br>> > #IM_MAD = [<br>> > # name = "im_ec2",<br>> > # executable = "one_im_ec2",<br>> > # arguments = "im_ec2/im_ec2.conf" ]<br>> > #-------------------------------------------------------------------------------<br>> ><br>> > #*******************************************************************************<br>> > # Virtualization Driver Configuration<br>> > #*******************************************************************************<br>> > # You can add more virtualization managers with different configurations 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 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>> > #VM_MAD = [<br>> > # name = "vmm_xen",<br>> > # executable = "one_vmm_xen",<br>> > # default = "vmm_xen/vmm_xen.conf",<br>> > # type = "xen" ]<br>> ><br>> > #-------------------------------------------------------------------------------<br>> > # KVM Virtualization Driver Manager sample configuration<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>> > # VMWare Virtualization Driver Manager sample configuration<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>> > # EC2 Virtualization Driver Manager sample configuration<br>> > # arguments: default values for the EC2 driver, can be an absolute path<br>> > or<br>> > # relative to $ONE_LOCATION/etc (or /etc/one/ if OpenNebula<br>> > was<br>> > # installed in /).<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>> > # Transfer Manager Driver Configuration<br>> > #*******************************************************************************<br>> > # You can add more transfer managers with different configurations but 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 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>> > #TM_MAD = [<br>> > # name = "tm_ssh",<br>> > # executable = "one_tm",<br>> > # arguments = "tm_ssh/tm_ssh.conf" ]<br>> ><br>> > #-------------------------------------------------------------------------------<br>> > # NFS Transfer Manager Driver sample configuration<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>> > # VMWare Transfer Driver Manager sample configuration<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>> > # Dummy Transfer Manager Driver sample configuration<br>> > #-------------------------------------------------------------------------------<br>> > #TM_MAD = [<br>> > # name = "tm_dummy",<br>> > # executable = "one_tm",<br>> > # arguments = "tm_dummy/tm_dummy.conf" ]<br>> > #-------------------------------------------------------------------------------<br>> ><br>> > #-------------------------------------------------------------------------------<br>> > # LVM Transfer Manager Driver sample configuration<br>> > #-------------------------------------------------------------------------------<br>> > #TM_MAD = [<br>> > # name = "tm_lvm",<br>> > # executable = "one_tm",<br>> > # arguments = "tm_lvm/tm_lvm.conf" ]<br>> > #-------------------------------------------------------------------------------<br>> ><br>> > #*******************************************************************************<br>> > # Hook Manager Configuration<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 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 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>> > 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>> > #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>> > #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>> > 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 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" 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 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. ¡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 /><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>