WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 		  
Home Products Support Community News
 
   
 

xen-devel

[Top] [All Lists]
<prev [Date] next>
[Advanced]
 <prev [Thread] next>

[Xen-devel] Re: Problem with stubdom-dm and live migration in xen 4.0.1

from [Roberto Scudeller] [Permanent Link][Original]
To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Re: Problem with stubdom-dm and live migration in xen 4.0.1
From: Roberto Scudeller <beto.rvs@xxxxxxxxx>
Date: Fri, 15 Oct 2010 11:00:41 -0300
Delivery-date: Fri, 15 Oct 2010 07:01:50 -0700
Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:received:date:message-id :subject:from:to:content-type; bh=fA5jJgs7ehuT4ugxXlirXmrs8TAXwya8X8cH/nGnVwc=; b=X14htVvOVpp+7SyF2SchAQaCRT3BUQloBvvJDpH0wEzxYDsYb369yQ8IZMK6e01Mkt GfCM8LfI/nDU33CbO7wvVdfGiHMb9a1HRSqkY6z/vfs8CsJi1yGMbqBy/OaJCw2YCzGp gIgA01iOGlx2LFuqj7QIRl2BElB2+ah3GHJGs=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=oFLgfCE+RhlSwCBcg4c+UN4PdSwcgXdOsa3XHaz04wAuMkL5Y8pPGFd0g3N5HGRxl6 3YcpVk3hzNqfohyiW1BuZy++NwW/6OjmcKrVxLvKK2O4Xy9Z5h3TShPh8aONYu4dLB4e zA5Y0Xh1ue78f5oMJZ00CoEOWz9GuQfXjCmbo=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
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@xxxxxxxxx
beto_rvs@xxxxxxxxxxxx
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
[More with this subject...]
<Prev in Thread] Current Thread [Next in Thread>
  • [Xen-devel] Re: Problem with stubdom-dm and live migration in xen 4.0.1, Roberto Scudeller <=
Previous by Date:  [Xen-devel] [PATCH 13/13] Nested Virtualiztion: hap-on-hap, Christoph Egger
Next by Date:  RE: [Xen-devel] [PATCH] time-xen : Reset monotonic time when sync up time from dom0 to domU, Dan Magenheimer
Previous by Thread:  [Xen-devel] [PATCH 13/13] Nested Virtualiztion: hap-on-hap, Christoph Egger
Next by Thread:  [Xen-devel] [PATCH 00/18] xenpaging changes for 4.0, Olaf Hering
Indexes:  [Date] [Thread] [Top] [All Lists]
 
   

Copyright , Citrix Systems Inc. All rights reserved. Legal and Privacy