Tino I wanted to confirm one thing. You have referred to documentation of SDK 4.0, however I am using sdk 2.5 as mentioned in the opennebula vmware page.
Do you think things should work fine if I use SDK 4? Thanks and Regards, Manish Office Phone : 46711053 Extension : #1053 On 6/24/2010 6:37 PM, Tino Vazquez wrote:
Hi Manish, You are getting this errors because the VMware server doesn't have the "hardware.memorySize" property, or, rather, it exists under other name. My experience is that, for some reason, differente VMware server versions have different property names (the OpenNebula drivers were developed against ESXi). We are quite busy at the moment preparing the v1.6 release so I don't really have the time to dig into this, but we would appreciate any feedback. I think the VI SDK documentation is the right place to look, take a look at the programming guide [1], and the API reference [2] (I believe all the properties are listed here). Best regards, -Tino [1] http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/sdk40programmingguide.pdf [2] http://www.vmware.com/support/developer/vc-sdk/visdk400pubs/ReferenceGuide/index.html -- 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 Thu, Jun 24, 2010 at 8:54 AM, Manish Sapariya<man...@gslab.com> wrote:Hi, I have working setup of opennebula using VMWare Server on Linux FC 8. I want to run VMWare Server on Windows to use some of my windows servers. As I add the Windows host to list it fails to monitor the Widnows VMWare server with following exception. ---- Debug stack trace ---- java.lang.NullPointerException at GetProperty.getProperties(GetProperty.java:74) at GetProperty.getObjectProperty(GetProperty.java:59) at OneImVmware.loop(OneImVmware.java:180) at OneImVmware.main(OneImVmware.java:59) [24.06.2010 12:12:47] --------------------------- As I see in the code it fails to check the "hardware.memorySize". Any clues? How can I figure if these perf counters are supported or not on windows? -- Thanks and Regards, Manish _______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
