On Tue, Mar 23, 2010 at 05:04:59PM +0900, ?????? wrote:
> when I command 'xm save [domainU] [filename]', save process does not
> complete with this error message
>
> Error: /usr/lib/xen/bin/xc_save 34 2 0 0 0 failed
> Usage: xm save [-c] <Domain> <CheckpointFile>
>
> Save a domain state to restore later.
> -c, --checkpoint Leave domain running after
> creating
> snapshot
>
> and /var/log/xen/xend.log produced below error message.
>
> [2010-03-23 16:58:07 1023] DEBUG (DevController:643) hotplugStatusCallback
> 1.
> [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting for devices
> irq.
> [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting for devices
> vfb.
> [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting for devices
> pci.
> [2010-03-23 16:58:07 1023] DEBUG (DevController:139) Waiting for devices
> vtpm.
> [2010-03-23 16:58:07 1023] INFO (XendDomain:1182) Domain ubuntu1 (3)
> unpaused.
> [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:110) [xc_save]:
> /usr/lib/xen/bin/xc_save 34 3 0 0 0
> [2010-03-23 16:58:42 1023] INFO (XendCheckpoint:417) xc_save: failed to
> get the suspend evtchn port
> [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:388) suspend
> [2010-03-23 16:58:42 1023] INFO (XendCheckpoint:417)
> [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:113) In saveInputHandler
> suspend
> [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:115) Suspending 3 ...
> [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:511)
> XendDomainInfo.shutdown(suspend)
> [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:1709)
> XendDomainInfo.handleShutdownWatch
> [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:1709)
> XendDomainInfo.handleShutdownWatch
> [2010-03-23 16:58:42 1023] INFO (XendDomainInfo:1903) Domain has shutdown:
> name=migrating-ubuntu1 id=3 reason=suspend.
> [2010-03-23 16:58:42 1023] INFO (XendCheckpoint:121) Domain 3 suspended.
> [2010-03-23 16:58:42 1023] DEBUG (XendCheckpoint:130) Written done
> [2010-03-23 16:58:42 1023] ERROR (XendCheckpoint:164) Save failed on
> domain ubuntu1 (3) - resuming.
> Traceback (most recent call last):
> File "/usr/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line
> 132, in save
> forkHelper(cmd, fd, saveInputHandler, False)
> File "/usr/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line
> 405, in forkHelper
> raise XendError("%s failed" % string.join(cmd))
> XendError: /usr/lib/xen/bin/xc_save 34 3 0 0 0 failed
> [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:2788)
> XendDomainInfo.resumeDomain(3)
> [2010-03-23 16:58:42 1023] DEBUG (XendDomainInfo:2829)
> XendDomainInfo.resumeDomain: completed
> [2010-03-23 17:01:10 1023] DEBUG (XendDomainInfo:2732)
> XendDomainInfo.destroy: domid=3
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2207) Destroying device
> model
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2214) Releasing devices
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removing vif/0
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vif, device = vif/0
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removing console/0
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = console, device = console/0
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removing vbd/51713
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51713
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2227) Removing vbd/51714
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:1134)
> XendDomainInfo.destroyDevice: deviceClass = vbd, device = vbd/51714
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2212) No device model
> [2010-03-23 17:01:11 1023] DEBUG (XendDomainInfo:2214) Releasing devices
>
> my system configuration ( 32bit machine )
> xen 3.4.2, dom0( jeremy's pvops kernel 2.6.31.6), domU( vanilla kernel
> 2.6.32 with paravirt enabled), distribution( ubuntu 9.10 )
> It does not work well
>
> what is the problem??
> I think current system is quite stable, newtork, disk, and so on.
> Is there anyone who know this or has experience??
>
You need to update your domU kernel to the latest stable update (2.6.32.10),
and that'll fix the problem. 2.6.32(.0) doesn't yet have the necessary
save/restore fixes.
-- Pasi
_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
|
Home