I can confirm this behaviour if domU is a paravirtualized etch x686 too; I think the severity of this bug should be raised to "important".
Dom0: debian lenny amd64 (2.6.26-2-xen-amd64) DomU: debian etch i686 (2.6.18-6-xen-686) From the xen logs: [2009-07-03 17:12:34 4686] INFO (XendCheckpoint:373) All memory is saved [2009-07-03 17:12:34 4686] INFO (XendDomainInfo:1283) Domain has shutdown: name=migrating-sg id=27 reason=suspend. [2009-07-03 17:12:34 4686] ERROR (XendCheckpoint:144) Save failed on domain sg (27). Traceback (most recent call last): File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py", line 112, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/lib/xen-3.2-1/lib/python/xen/xend/XendCheckpoint.py", line 361, in forkHelper raise XendError("%s failed" % string.join(cmd)) XendError: /usr/lib/xen-3.2-1/bin/xc_save 22 27 0 0 1 failed [2009-07-03 17:12:59 4686] DEBUG (XendDomainInfo:1897) XendDomainInfo.destroy: domid=27 [2009-07-03 17:12:59 4686] DEBUG (XendDomainInfo:1914) XendDomainInfo.destroyDomain(27) -- To UNSUBSCRIBE, email to debian-kernel-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org