[Xen-bugs] [Bug 1273] New: Message Parameter Count Mismatch using clone() method

[bugzilla-daemon@xxxxxxxxxxxxxxxxxxx]

http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=1273

           Summary: Message Parameter Count Mismatch using clone() method
           Product: Xen
           Version: unspecified
          Platform: x86
        OS/Version: Linux-2.6
            Status: NEW
          Severity: normal
          Priority: P1
         Component: Hypervisor
        AssignedTo: xen-bugs@xxxxxxxxxxxxxxxxxxx
        ReportedBy: mmauser70@xxxxxx


I am using the Java bindings of the Xen API to manage VMs remotely. But it
seems to me that these bindings do not work properly. The version of Xen I am
using is 3.1.2 I am trying to start, stop, pause, unpause and clone VMs.
Everything is working fine except the clone() method. When I call this method I
get the following error message:

[MESSAGE PARAMETER COUNT MISMATCH, clone, 2, 3]

The manual of the Xen API says that the clone() method needs three parameters,

  - session ID
  - VM reference
  - name of new VM

but the description of the error message says that this error occures because
the number of parameters equals not the expected number of parameters. The
format of the above mentioned error is ERROR MESSAGE, AFFECTED METHOD, EXPECTED
NUMBER OF PARAMETERS, RECEIVED NUMBER OF PARAMETERS.

I think this is a little bit confusing, because the method clone(), which
resides in the class VM, sends all neccessary parameters (see above) and sends
it in the expected order.

I have also captured the communication between the Xen host and the client with
Wireshark. Everything is marshalled correctly. So my question is could anybody
help me to get rid of this problem? Or has anybody another solution how I can
implement the management abilities in my application?

I would really appreciate that because it is very important for my thesis I am
currently working on.

Max


-- 
Configure bugmail: 
http://bugzilla.xensource.com/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

_______________________________________________
Xen-bugs mailing list
Xen-bugs@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-bugs