[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] 答复: [Xen-devel] Xen Live Migration Fail
Did you modify the xend-config.sxp correctly? Those comments in the discussion thread below, could be helpful for your question. http://lists.xensource.com/archives/html/xen-users/2009-03/msg00079.html thanks, -James ( Song Wei) << : xen-devel-bounces@xxxxxxxxxxxxxxxxxxx [mailto:xen-devel-bounces@xxxxxxxxxxxxxxxxxxx] << xen-devel@xxxxxxxxxxxxxxxxxxx <<[Xen-devel] Xen Live Migration Fail Dear all: I am trying to migrate a WinXP HVM (64M memory) from a machine (sender) to another machine (receiver) through AoE disk, however, there are some errors when do the following command: (My xen version is xen-4.0.1-rc5.hg, kernel 2.6.31.13, xen xen-4.0.1-rc6-pre, Both sender and receiver are the same xen version) xm migrate --live domain_id receiver_ip =============================================== The error message at sender side is: Error: timed out Usage: xm migrate <Domain> <Host> ... =============================================== Then, I read the xend.log (sender) and find this error message: =============================================== [2010-11-20 18:12:45 4667] INFO (XendDomain:1206) Domain WinXP_HVM_Migrate (1) unpaused. [2010-11-20 18:14:06 4667] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 35 1 0 0 5 [2010-11-20 18:14:06 4667] INFO (XendCheckpoint:423) xc_save: failed to get the suspend evtchn port ... [2010-11-20 18:14:33 4667] WARNING (image:552) domain migrating-WinXP_HVM_Migrate: device model failure: pid 4871: died due to signal 6; see /var/log/xen/qemu-dm-WinXP_HVM_Migrate.log [2010-11-20 18:14:33 4667] INFO (XendDomainInfo:2088) Domain has shutdown: name=migrating-WinXP_HVM_Migrate id=1 reason=suspend. [2010-11-20 18:14:43 4667] INFO (XendCheckpoint:423) ERROR Internal error: Suspend request failed [2010-11-20 18:14:43 4667] INFO (XendCheckpoint:423) ERROR Internal error: Domain appears not to have suspended [2010-11-20 18:14:48 4667] INFO (XendCheckpoint:423) xc_save: timed out waiting for qemu logdirty response. ... =============================================== And the qemu-dm.log gives a "buffer overflow" message as following: =============================================== ... device model saving state *** buffer overflow detected ***: /usr/lib64/xen/bin/qemu-dm terminated ======= Backtrace: ========= /lib/libc.so.6(__fortify_fail+0x37)[0x7fecab467217] /lib/libc.so.6(+0xfe0d0)[0x7fecab4660d0] /lib/libc.so.6(+0xfd539)[0x7fecab465539] /lib/libc.so.6(_IO_default_xsputn+0xcc)[0x7fecab3ddd1c] /lib/libc.so.6(_IO_vfprintf+0x14c)[0x7fecab3ad4ec] =============================================== The logs are also attached. Any ideas or patches to fix this problem ? Thanks! Best Regards, Tang-Hsun Tu _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel
|
![]() |
Lists.xenproject.org is hosted with RackSpace, monitoring our |