[one-users] im_vmware fails [SOLVED]

Tino Vazquez tinova at fdi.ucm.es
Fri Feb 5 02:20:58 PST 2010


Hi Stefan,

I've added the default for the NET attributes [1], and thus closed issue 175.

Thanks a lot for your feedback,

-Tino

[1] http://dev.opennebula.org/projects/opennebula/repository/revisions/964
--
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, Feb 4, 2010 at 11:02 PM, Stefan Reichel
<Stefan.Reichel at student.hpi.uni-potsdam.de> wrote:
> Hi Tino,
> as i already mentioned i set a default value for the transmitted and
> received bytes. My code looks as follows:
>                              // NET
>                               int net=0;
>                               rf =
> gP.getPerformanceCounter("net.transmitted.average", 60);
>                               if (!rf) net = 0;
>                               else net = (int)gP.getMeasure();
>                               response = response + ",NETTX=" + net;
>
>                               rf =
> gP.getPerformanceCounter("net.received.average", 60);
>                               if (!rf) net = 0;
>      else net = (int)gP.getMeasure();
>                               response = response + ",NETRX=" + net;
> For us this workaround is better then just raising an exception. Setting a
> default value wont cause any problems in this special case. But you are
> right, setting default values for RAM, CPU, DIsk etc. can cause serious
> trouble.
> Best regards,
> Stefan
>
> Am 01.02.2010 um 12:20 schrieb Tino Vazquez:
>
> Hi Stefan,
>
> I'm glad it finally worked. The default values for server properties
> is a tricky task because setting a, say, 1Gb of RAM as a default value
> can cause machines with 512Mb problems.
>
> The real deal is to find the match between the no found values and
> their equivalents in VMware server 2. Can you tell me which values you
> had to set by default?
>
> Regards,
>
> -Tino
>
> --
> 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 Wed, Jan 27, 2010 at 4:44 PM, Stefan Reichel
> <Stefan.Reichel at student.hpi.uni-potsdam.de> wrote:
>
> Hi Tino,
>
> thanks for your reply.  I debugged the code and came across to major
>
> problems. First of all the error, which i reported with the bug trace. It
>
> turned out, that this error was connected to a configuration problem. In
>
> effect the supplied entityname in connect()/GetProperties could not be
>
> found.
>
> The second problem was a problem with the net.average etc. After i disabled
>
> the exceptions and set instead default values, it worked. Indeed this is the
>
> mentioned issue 175. Perhaps you should also set default values.
>
> So there are no further problems at the moment , so this problem is solved.
>
> Best Regards
>
> Stefan
>
> Am 27.01.2010 um 12:28 schrieb Tino Vazquez:
>
> Hi Stefan,
>
> The VMware drivers has been tested thoroughly against the ESX
>
> hypervisor, but not that extensively in VMware server. I know there
>
> are some incompatibilities (see [1]).
>
> For what I see in the stack traces you've sent through, the IM driver
>
> is failing performing a
>
> gP.getObjectProperty("hardware.memorySize")
>
> so it is possible that this property is not available in the VMware
>
> server 2 hypervisor. It is wird though that in the second stack trace
>
> you sent the IM got to
>
> gP.getObjectProperty("hardware.cpuInfo.numCpuCores")
>
> Could it be that the file got a few more comment lines?
>
> In any case, I appreciate it if you could tell me the exact version of
>
> VMware server 2 are you running, and, if possible, which SDK is using,
>
> so we can find the equivalent(s) of the properties requested.
>
> Best regards,
>
> -Tino
>
> [1] http://dev.opennebula.org/issues/175
>
> --
>
> 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 Sat, Jan 23, 2010 at 12:31 PM, Stefan Reichel
>
> <Stefan.Reichel at student.hpi.uni-potsdam.de> wrote:
>
> Hi,
>
> i just installed the current stable version and followed your vmware driver
>
> manual and the opennebula in five steps howto.
>
> https://help.ubuntu.com/community/OpenNebula
>
> http://www.opennebula.org/doku.php?id=documentation:rel1.4:vmwareg
>
> I added a host/cluster seclab-server.hpi.uni-potsdam.de but i get several
>
> errors.
>
> [23.01.2010 12:19:37] INIT SUCCESS
>
> [23.01.2010 12:21:39] MONITOR FAILURE 0 Failed monitoring host
>
> seclab-server.hpi.uni-potsdam.de.
>
> [23.01.2010 12:21:39] Failed monitoring host
>
> seclab-server.hpi.uni-potsdam.de.Reason: null
>
> ---- Debug stack trace ----
>
> java.lang.NullPointerException
>
>       at GetProperty.getProperties(GetProperty.java:74)
>
>       at GetProperty.getObjectProperty(GetProperty.java:59)
>
>       at OneImVmware.loop(OneImVmware.java:166)
>
>       at OneImVmware.main(OneImVmware.java:59)
>
> [23.01.2010 12:21:39] ---------------------------
>
>
> I think the login to my VmWare Server 2 is successful, because i see no
>
> errors  in the tomcat log of the VMware server.  I also tried to use the SVN
>
> version of your software, with no success either. Afterwards i tried to
>
> debug the error and i extended the debug output. Do you have any hints what
>
> is going wrong here.
>
>
> Kind regards
>
> Stefan.
>
>
>
>
>
> [23.01.2010 11:59:12] MONITOR FAILURE 2 Failed monitoring host
>
> seclab-server.hpi.uni-potsdam.de.
>
> [23.01.2010 11:59:12] Failed monitoring host
>
> seclab-server.hpi.uni-potsdam.de.Reason: ; nested exception is:
>
>       java.io.IOException: java.io.IOException: java.io.IOException: Non
>
> nillable element 'type' is null.
>
> ---- Debug stack trace ----
>
> AxisFault
>
> faultCode: {http://schemas.xmlsoap.org/soap/envelope/}Server.userException
>
> faultSubcode:
>
> faultString: java.io.IOException: java.io.IOException: java.io.IOException:
>
> Non nillable element 'type' is null.
>
> faultActor:
>
> faultNode:
>
> faultDetail:
>
>       {http://xml.apache.org/axis/}stackTrace:java.io.IOException:
>
> java.io.IOException: java.io.IOException: Non nillable element 'type' is
>
> null.
>
>       at
>
> org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
>
>       at
>
> org.apache.axis.encoding.ser.ArraySerializer.serialize(ArraySerializer.java:414)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
>
>       at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
>
>       at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
>
>       at
>
> org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
>
>       at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
>
>       at
>
> org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
>
>       at
>
> org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
>
>       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
>
>       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
>
>       at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
>
>       at org.apache.axis.SOAPPart.getContentLength(SOAPPart.java:229)
>
>       at org.apache.axis.Message.getContentLength(Message.java:510)
>
>       at
>
> org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:371)
>
>       at
>
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
>
>       at
>
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
>
>       at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>
>       at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>
>       at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>
>       at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>
>       at org.apache.axis.client.Call.invoke(Call.java:2767)
>
>       at org.apache.axis.client.Call.invoke(Call.java:2443)
>
>       at org.apache.axis.client.Call.invoke(Call.java:2366)
>
>       at org.apache.axis.client.Call.invoke(Call.java:1812)
>
>       at
>
> com.vmware.vim.VimBindingStub.retrieveProperties(VimBindingStub.java:19279)
>
>       at GetProperty.getProperties(GetProperty.java:99)
>
>       at GetProperty.getObjectProperty(GetProperty.java:59)
>
>       at OneImVmware.loop(OneImVmware.java:172)
>
>       at OneImVmware.main(OneImVmware.java:59)
>
>       {http://xml.apache.org/axis/}hostname:seclab-server
>
> java.io.IOException: java.io.IOException: java.io.IOException: Non nillable
>
> element 'type' is null.
>
>       at org.apache.axis.AxisFault.makeFault(AxisFault.java:101)
>
>       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:317)
>
>       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:269)
>
>       at org.apache.axis.SOAPPart.saveChanges(SOAPPart.java:530)
>
>       at org.apache.axis.SOAPPart.getContentLength(SOAPPart.java:229)
>
>       at org.apache.axis.Message.getContentLength(Message.java:510)
>
>       at
>
> org.apache.axis.transport.http.HTTPSender.writeToSocket(HTTPSender.java:371)
>
>       at
>
> org.apache.axis.transport.http.HTTPSender.invoke(HTTPSender.java:138)
>
>       at
>
> org.apache.axis.strategies.InvocationStrategy.visit(InvocationStrategy.java:32)
>
>       at org.apache.axis.SimpleChain.doVisiting(SimpleChain.java:118)
>
>       at org.apache.axis.SimpleChain.invoke(SimpleChain.java:83)
>
>       at org.apache.axis.client.AxisClient.invoke(AxisClient.java:165)
>
>       at org.apache.axis.client.Call.invokeEngine(Call.java:2784)
>
>       at org.apache.axis.client.Call.invoke(Call.java:2767)
>
>       at org.apache.axis.client.Call.invoke(Call.java:2443)
>
>       at org.apache.axis.client.Call.invoke(Call.java:2366)
>
>       at org.apache.axis.client.Call.invoke(Call.java:1812)
>
>       at
>
> com.vmware.vim.VimBindingStub.retrieveProperties(VimBindingStub.java:19279)
>
>       at GetProperty.getProperties(GetProperty.java:99)
>
>       at GetProperty.getObjectProperty(GetProperty.java:59)
>
>       at OneImVmware.loop(OneImVmware.java:172)
>
>       at OneImVmware.main(OneImVmware.java:59)
>
> Caused by: java.io.IOException: java.io.IOException: java.io.IOException:
>
> Non nillable element 'type' is null.
>
>       at
>
> org.apache.axis.encoding.ser.BeanSerializer.serialize(BeanSerializer.java:275)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:734)
>
>       at
>
> org.apache.axis.encoding.ser.ArraySerializer.serialize(ArraySerializer.java:414)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serializeActual(SerializationContext.java:1504)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:980)
>
>       at
>
> org.apache.axis.encoding.SerializationContext.serialize(SerializationContext.java:801)
>
>       at org.apache.axis.message.RPCParam.serialize(RPCParam.java:208)
>
>       at org.apache.axis.message.RPCElement.outputImpl(RPCElement.java:433)
>
>       at
>
> org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
>
>       at org.apache.axis.message.SOAPBody.outputImpl(SOAPBody.java:139)
>
>       at
>
> org.apache.axis.message.SOAPEnvelope.outputImpl(SOAPEnvelope.java:478)
>
>       at
>
> org.apache.axis.message.MessageElement.output(MessageElement.java:1208)
>
>       at org.apache.axis.SOAPPart.writeTo(SOAPPart.java:315)
>
>       ... 20 more
>
> [23.01.2010 11:59:12] ---------------------------
>
> [23.01.2010 12:00:01] FINALIZE SUCCESS
>
> _______________________________________________
>
> Users mailing list
>
> Users at lists.opennebula.org
>
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
> _____________________________________
>
> Stefan Reichel,  M.Sc. Candidate
>
> Hasso-Plattner-Institut für Softwaresystemtechnik GmbH
>
> Postfach 900460, D-14440 Potsdam, Germany
>
> http://www.hpi.uni-potsdam.de
>
> Telefon: 03322/206306  Mobile: 0178/5495023
>
> Email: stefan.reichel at student.hpi.uni-potsdam.de
>
> _____________________________________
>
> _______________________________________________
>
> Users mailing list
>
> Users at lists.opennebula.org
>
> http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
>
>
>
> _____________________________________
>
> Stefan Reichel,  M.Sc. Candidate
>
> Hasso-Plattner-Institut für Softwaresystemtechnik GmbH
> Postfach 900460, D-14440 Potsdam, Germany
> http://www.hpi.uni-potsdam.de
> Telefon: 03322/206306  Mobile: 0178/5495023
> Email: stefan.reichel at student.hpi.uni-potsdam.de
> _____________________________________
>



More information about the Users mailing list