[one-users] problems with ESX(i) 5.0 and opennebula 2.2.1

[Tino Vazquez]

FYI


On Thu, Mar 1, 2012 at 11:25 AM, Tino Vazquez <tinova at opennebula.org> wrote:
> Hi,
>
> You need to install a newer version of libvirt, the one you are using
> doesn't support vSphere 5. Snatching the last from libvirt's git repo
> would do [1].
>
> Regards,
>
> -Tino
>
> [1] http://libvirt.org/downloads.html
>
> --
> Constantino Vázquez Blanco, MSc
> Project Engineer
> OpenNebula - The Open-Source Solution for Data Center Virtualization
> www.OpenNebula.org | @tinova79 | @OpenNebula
>
>
>
> On Wed, Feb 29, 2012 at 8:13 PM, PJ PJ <igranjo at hotmail.com> wrote:
>> I have opennebula-2.2.1 with driver vmware-2.2.0
>> After to up date the versión of ESX(i) to 5.0 and run to deploy of a virtual
>> machine, show the next error:
>>
>>  Mon Feb 27 13:04:35 2012 [ReM][D]: VirtualMachinePoolInfo method invoked
>>  Mon Feb 27 13:04:37 2012 [InM][I]: Monitoring host esx (1)
>>  Mon Feb 27 13:04:40 2012 [InM][I]: Command execution fail:
>> /srv/cloud/one/var/remotes//im/run_probes vmware esx
>>  Mon Feb 27 13:04:40 2012 [InM][I]: STDERR follows.
>>  Mon Feb 27 13:04:40 2012 [InM][I]: /srv/cloud/one/lib/ruby/vmwarelib.rb:26:
>> warning: already initialized constant ONE_LOCATION
>>  Mon Feb 27 13:04:40 2012 [InM][I]: /srv/cloud/one/lib/ruby/vmwarelib.rb:32:
>> warning: already initialized constant RUBY_LIB_LOCATION
>>  Mon Feb 27 13:04:40 2012 [InM][I]: [VMWARE] cmd failed
>> [/srv/cloud/one/bin/tty_expect -u oneadmin -p cloud2011 virsh -c
>> esx://esx/?no_verify=1 --readonly nodeinfo]. S
>>  tderr:
>>  Mon Feb 27 13:04:40 2012 [InM][I]: error: internal error Expecting VI API
>> major/minor version '2.5' or '4.x' but found '5.0'
>>  Mon Feb 27 13:04:40 2012 [InM][I]: error: failed to connect to the
>> hypervisor
>>  Mon Feb 27 13:04:40 2012 [InM][I]: . Stdout: ExitCode: 1
>>  Mon Feb 27 13:04:40 2012 [InM][I]: ./vmware.rb:65: private method `split'
>> called for 1:Fixnum (NoMethodError)
>>  Mon Feb 27 13:04:40 2012 [InM][I]: Error executing vmware.rb
>>  Mon Feb 27 13:04:40 2012 [InM][I]: ExitCode: 1
>>  Mon Feb 27 13:04:40 2012 [InM][E]: Error monitoring host 1 : MONITOR
>> FAILURE 1 Could not monitor host esx.
>>
>> Afterward I check the conectivity and I recived this error:
>>
>>  oneadmin at opennebula:~$ virsh -c esx://esx/?no_verify=1
>>  Ingrese un nombre de usuario para esx [root]: oneadmin
>>  Ingrese la contraseña de oneadmin para esx:
>>  error:error interno Se esperaba una version VI API mayor/menor '2.5' or
>> '4.x', pero se ha encontrado '5.0'
>>  error:Fallo al conectar con el hipervisor
>>
>> More later I checked the driver VMWare on node ESX(i) 5.0, it showed the
>> next message:
>>
>>  oneadmin at opennebula:~$ lib/remotes/im/run_probes vmware esx
>>  /srv/cloud/one/lib/ruby/vmwarelib.rb:26: warning: already initialized
>> constant ONE_LOCATION
>>  /srv/cloud/one/lib/ruby/vmwarelib.rb:32: warning: already initialized
>> constant RUBY_LIB_LOCATION
>>  [VMWARE] cmd failed [/srv/cloud/one/bin/tty_expect -u oneadmin -p cloud2011
>> virsh -c esx://esx/?no_verify=1 --readonly nodeinfo]. Stderr:
>>  error: internal error Expecting VI API major/minor version '2.5' or '4.x'
>> but found '5.0'
>>  error: failed to connect to the hypervisor
>>  . Stdout: ExitCode: 1
>>  ./vmware.rb:65: private method `split' called for 1:Fixnum (NoMethodError)
>>  Error executing vmware.rb
>>
>> when all is ok, it showed:
>>
>>     oneadmin at opennebula:~$ onehost list
>>    ID NAME              CLUSTER  RVM   TCPU   FCPU   ACPU    TMEM    FMEM
>> STAT
>>     1 esx               default    0    800    800    800      8G    4.7G
>> on
>>
>> I checked the status node, it showed:
>>
>>  oneadmin at opennebula:~$ onehost list
>>    ID NAME              CLUSTER  RVM   TCPU   FCPU   ACPU    TMEM    FMEM
>> STAT
>>     1 esx               default    0    800    800    800      8G    4.7G
>> err
>> I have deleted the node, and I have created the node again, it showed:
>>
>>  oneadmin at opennebula:~$ onehost list
>>   ID NAME              CLUSTER  RVM   TCPU   FCPU   ACPU    TMEM    FMEM
>> STAT
>>     2 esx               default    0      0      0    100      0K      0K
>> err
>>
>> I came back to develop the above steps and I have obteined the same result.
>>
>> Could someone tell me if this versión of OpenNebula 2.2.1 with the driver
>> VMware 2.2.0 is compatible with ESX(i) version 5.0?
>> If this is true, what I need to change?
>>
>> Thanks in advance
>>
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>