[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-API] empty vdi-map will cause VM.migrate_send operation to fail

Hi Mike,

Thanks for your email.

We made the changes for migrate_send, but I guess, we need to do the
same gymnastics for the assert_can_migrate call. We found the following log

Sep  7 10:20:42 localhost xapi: [error|epun|5997 INET|dispatch:VM.assert_can_migrate D:fc2677e3fc64|xmlrpc] Error:
name='unbox: Element=struct should contain 'string''; xml=

What do you think, could me not passing vid_ref causing this log entry?
Seems to be some sort of syntax error.


On Fri, Sep 07, 2012 at 02:17:04PM +0100, Mike McClurg wrote:
> On 07/09/12 10:13, Mate Lakat wrote:
> > Hi,
> > 
> > I am about to fix this bug for OpenStack:
> > https://bugs.launchpad.net/nova/+bug/1040332
> > 
> > I would like to know a bit more about what is the expected content for
> > vdi-map in this case, to create proper test doubles. So I am interested
> > in the specification of the VM.migrate_send command.
> The vdi-map should contain a dictionary of (vdi_ref, sr_ref) pairs. The
> vdi_ref should be an Opaque_ref to the VDI on the source pool, and the
> sr_ref should be an Opaque_ref to the destination SR on the destination
> pool. You should specify all the VDIs for which the VM has a VBD.
> In case you didn't know, you can look at the Xapi source code to see a
> list of all the XenAPI commands and the name and type of each of their
> parameters [1]. Here [2] is a direct link to the migrate_send function.
> Mike
> [1] https://github.com/xen-org/xen-api/blob/master/ocaml/idl/datamodel.ml
> [2]
> https://github.com/xen-org/xen-api/blob/master/ocaml/idl/datamodel.ml#L2049

Xen-api mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.