[one-users] im_vmware error

[Shi Jin]

Dear Tino,

Thank you.
I've re-tried everything for ESXi 3.5 from building open nebula
subversion code to building the VI-SDK 2.5. However when I tested it
I still got the same error:
oneadmin at esx-one mads $ ./one_im_vmware --username root --password <password>
INIT
INIT SUCCESS
MONITOR 0 node2
java.lang.NullPointerException
    at GetProperty.getProperties(GetProperty.java:74)
    at GetProperty.getObjectProperty(GetProperty.java:59)
    at OneImVmware.loop(OneImVmware.java:159)
    at OneImVmware.main(OneImVmware.java:60)
MONITOR FAILURE 0 Failed monitoring host node2.

This is exactly the same issue for ESXi 4.0 I had before, where the
moRef is null.
Do you have any suggestions?
Thank you very much.

Shi

On Tue, Sep 15, 2009 at 4:33 AM, Tino Vazquez <tinova at fdi.ucm.es> wrote:
> Dear Shi Jin,
>
> Thanks a lot for your feedback. I still haven't got the time to test
> the drivers against the ESX and ESXi 4.0 hypervisors, but I am afraid
> that the API changed, and althought I also think that they made it
> backward compatible, some thigs may not work as expected.
>
> I suggest switching to the old ESXi version for now to see if the
> error goes away. I would appreciate it if you can confirm the error
> doesn't happen with the 3.5 version.
>
> Best regards,
>
> -Tino
>
> --
> Constantino Vázquez, Grid 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 Mon, Sep 14, 2009 at 11:06 PM, Shi Jin <jinzishuai at gmail.com> wrote:
>> Hi there,
>>
>> I am trying to get open nebula 1.3.8 work with ESXi 4.0 hosts.
>> I followed the documentation and all seemed to work fine.
>> After adding the ESXi host, I got error status code on the host.
>> The oned.log returns
>> Error monitoring host 0 : MONITOR FAILURE 0 Failed monitoring host node3.
>>
>> So I digged into the Java code of OneImVmware.java and figured out
>> exactly where the problem is.
>> In the GetProperty::connect() function, the moRef object is still null
>> after the connection.
>>
>> Has anyone seen  this kind of problem before?
>> I am not sure whether ESX4.0 makes a difference to ESXi 3.5 which was
>> used in the documentation.
>> Should I switch to the older version of ESXi?
>> Thank you very much.
>>
>> --
>> Shi Jin, Ph.D.
>> _______________________________________________
>> Users mailing list
>> Users at lists.opennebula.org
>> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>>
>



-- 
Shi Jin, Ph.D.