Roberto Scudeller
2010-Oct-14 13:50 UTC
[Xen-devel] Problem with stubdom-dm and live migration in xen 4.0.1
Hi all, I try using a VM with stubdom-dm instead qemu-dm, and "live migration" don''t work. This command "xm migrate --live w2k3-ent.15 IP_Dom0_Destiny" works, in the Dom0 destiny, created a paused VM (with memory but not a vcpus), but in the end of process, not started appropriate and destroyed VM in both Dom0 Xen. Look "xl list" below: This description in "xl list", Dom0: Name ID Mem VCPUs State Time(s) w2k3-ent.15 29 4099 4 r-- 545.1 w2k3-ent.15-dm 30 32 1 r-- 482.4 In Dom0_Destiny, during "xm migrate...": Name ID Mem VCPUs State Time(s) w2k3-ent.15 8 4099 1 -p- 0.0 I using xen 4.0.1 and a kernel 2.6.31.21. Anybody help? Sorry for my English terrible. -- Roberto Scudeller _______________________________________________ Xen-devel mailing list Xen-devel@lists.xensource.com http://lists.xensource.com/xen-devel
Roberto Scudeller
2010-Oct-15 14:00 UTC
[Xen-devel] Re: Problem with stubdom-dm and live migration in xen 4.0.1
Hi all,
This problem continues.
Now I try with xen 4.0.2-rc1-pre, and I catch the log in
/var/log/xen/xend.log in Dom0 receiving the VM:
[2010-10-15 10:51:51 4484] INFO (XendCheckpoint:423) ERROR Internal error:
Error reading QEMU signature
[2010-10-15 10:51:51 4484] INFO (XendCheckpoint:423) ERROR Internal error:
error buffering image tail
[2010-10-15 10:51:51 4484] INFO (XendCheckpoint:423) Restore exit with rc=1
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:3053)
XendDomainInfo.destroy: domid=2
[2010-10-15 10:51:51 4484] ERROR (XendDomainInfo:3067)
XendDomainInfo.destroy: domain destruction failed.
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/XendDomainInfo.py", line
3060, in destroy
xc.domain_pause(self.domid)
Error: (3, ''No such process'')
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2416) No device model
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2418) Releasing devices
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2424) Removing vif/0
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2424) Removing vfb/0
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = vfb, device = vfb/0
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2424) Removing console/0
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2424) Removing tap2/768
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = tap2, device = tap2/768
[2010-10-15 10:51:51 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/768/hotplug-status.
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2424) Removing tap2/51712
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = tap2, device = tap2/51712
[2010-10-15 10:51:51 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/51712/hotplug-status.
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:2424) Removing tap2/51744
[2010-10-15 10:51:51 4484] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = tap2, device = tap2/51744
[2010-10-15 10:51:51 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/51744/hotplug-status.
[2010-10-15 10:51:52 4484] DEBUG (XendDomainInfo:2424) Removing tap2/51760
[2010-10-15 10:51:52 4484] DEBUG (XendDomainInfo:1286)
XendDomainInfo.destroyDevice: deviceClass = tap2, device = tap2/51760
[2010-10-15 10:51:52 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/51760/hotplug-status.
[2010-10-15 10:51:52 4484] INFO (XendDomain:1106) Domain centos1
(cd73e043-72e1-5b84-3a10-c9f4d06e9858) deleted.
[2010-10-15 10:51:52 4484] ERROR (XendCheckpoint:357)
/usr/lib64/xen/bin/xc_restore 26 2 3 4 1 1 1 0 failed
Traceback (most recent call last):
File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
309, in restore
forkHelper(cmd, fd, handler.handler, True)
File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
411, in forkHelper
raise XendError("%s failed" % string.join(cmd))
XendError: /usr/lib64/xen/bin/xc_restore 26 2 3 4 1 1 1 0 failed
[2010-10-15 10:51:52 4484] ERROR (XendDomain:1175) Restore failed
Traceback (most recent call last):
File "/usr/lib64/python2.4/site-packages/xen/xend/XendDomain.py",
line
1159, in domain_restore_fd
dominfo = XendCheckpoint.restore(self, fd, paused=paused,
relocating=relocating)
File
"/usr/lib64/python2.4/site-packages/xen/xend/XendCheckpoint.py", line
358, in restore
raise exn
XendError: /usr/lib64/xen/bin/xc_restore 26 2 3 4 1 1 1 0 failed
[2010-10-15 10:51:52 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/768/hotplug-status.
[2010-10-15 10:51:52 4484] DEBUG (DevController:658) deviceDestroyCallback
6.
[2010-10-15 10:51:52 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/51712/hotplug-status.
[2010-10-15 10:51:52 4484] DEBUG (DevController:658) deviceDestroyCallback
6.
[2010-10-15 10:51:52 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/51744/hotplug-status.
[2010-10-15 10:51:52 4484] DEBUG (DevController:658) deviceDestroyCallback
6.
[2010-10-15 10:51:52 4484] DEBUG (DevController:649) deviceDestroyCallback
/local/domain/0/backend/vbd/2/51760/hotplug-status.
[2010-10-15 10:51:52 4484] DEBUG (DevController:658) deviceDestroyCallback
6.
Any help? Ideas?
--
Roberto Scudeller
Especialista Linux/Unix
+55 11 8763-6300
+55 11 8022-6956
beto.rvs@gmail.com
beto_rvs@yahoo.com.br
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel