Re: [Xen-users] Migration Failure (unable to destroy guest)

[Roger Pau Monnà <roger.pau@xxxxxxxxxx>]

El 16/12/15 a les 22.56, Charlie Mei ha escrit:
> Hello,
> 
> We are running into some issues with our migration - we are using a
> simple "xl migrate <id> <host ip>" command which gives us the
> following error:
> 
> migration target: Ready to receive domain.
> Saving to migration stream new xl format (info 0x3/0x0/2373)
> Loading new save file <incoming migration stream> (new xl fmt info 
> 0x3/0x0/2373)
> Savefile contains xl domain config in JSON format
> Parsing config from <saved>
> xc: info: Saving domain 1, type x86 HVM
> xc: error: Failed to enable logdirty: 22,0,22 (22 = Invalid argument):
> Internal error
> xc: error: Save failed (22 = Invalid argument): Internal error
> xc: info: Found x86 HVM domain from Xen 4.7
> xc: info: Restoring domain
> libxl: error: libxl_stream_write.c:329:libxl__xc_domain_save_done:
> saving domain: domain did not respond to suspend request: Invalid
> argument
> migration sender: libxl_domain_suspend failed (rc=-8)
> xc: error: Failed to read Record Header from stream (0 = Success):
> Internal error
> xc: error: Restore failed (0 = Success): Internal error
> libxl: error: libxl_stream_read.c:749:libxl__xc_domain_restore_done:
> restoring domain: Success
> libxl: error: libxl_create.c:1147:domcreate_rebuild_done: cannot
> (re-)build domain: -3
> libxl: error: libxl_dm.c:1994:kill_device_model: unable to find device
> model pid in /local/domain/2/image/device-model-pid
> libxl: error: libxl.c:1630:libxl__destroy_domid:
> libxl__destroy_device_model failed for 2
> libxl: error: libxl.c:1593:libxl__destroy_domid: non-existant domain 2
> libxl: error: libxl.c:1551:domain_destroy_callback: unable to destroy
> guest with domid 2
> libxl: error: libxl.c:1476:domain_destroy_cb: destruction of domain 2 failed
> migration target: Domain creation failed (code -3).
> libxl: info: libxl_exec.c:118:libxl_report_child_exitstatus: migration
> transport process [2902] exited with error status 3
> Migration failed, failed to suspend at sender.
> 
> Some context:
> We tried to run xl save, which was successful. We are also utilizing
> passthrough of some USB devices.

AFAIK you cannot migrate guests with passed through devices, the enable
log dirty hypercall will fail and return 22 (EINVAL). I have no idea how
you managed to successfully run xl save on it.

Roger.


_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxx
http://lists.xen.org/xen-users