Xen project Mailing List

Re: [Xen-devel] xl save -c issues with Windows 7 Ultimate

Date: Thu, 5 May 2011 14:01:47 -0700

Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>, Ian Campbell <Ian.Campbell@xxxxxxxxxx>

Delivery-date: Thu, 05 May 2011 14:02:51 -0700

Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type:content-transfer-encoding; b=Un/FfVFaO+4P/XC7xJP2FfE8oLU4tgtSGmcUkh5Q4Qb4UU/6MxDlzaQGIL30hyB4Hf hvTaoWy2ZDvz+lVfWCgUYOBi2KAZYtbYS0DXdMgWq3JdVZ0i8swTFO3FFXQ7fr0gvQM7 8FXHghR6J6Zlrt4bpRAQNn529XF1OEtVZXDAQ=

List-id: Xen developer discussion <xen-devel.lists.xensource.com>

On Thu, May 5, 2011 at 7:42 AM, Shriram Rajagopalan <rshriram@xxxxxxxxx> wrote: > On Tue, May 3, 2011 at 2:17 PM, AP Xen <apxeng@xxxxxxxxx> wrote: >> >> On Tue, May 3, 2011 at 7:09 AM, Shriram Rajagopalan <rshriram@xxxxxxxxx> >> wrote: >> > On Tue, May 3, 2011 at 6:01 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> >> > wrote: >> >> >> >> On Fri, 2011-04-29 at 20:28 +0100, AP Xen wrote: >> >> > I am trying to do an "xl save -c" on a Windows 7 Ultimate domain that >> >> > will leave the domain running at the end of the save operation. >> >> >> >> Do you have pv drivers installed which support checkpoint suspends? I'm >> >> not sure if such a thing even exists for Windows. >> >> >> >> I'm also not entirely sure that checkpointing was ever supported for >> >> HVM >> >> domains without PV drivers (e.g. via emulated hibernation). Perhaps the >> >> Remus guys know? >> >> >> > Remus works with HVM domains via normal xenstore based suspend/resume. >> > Only PV-HVM support is "disabled" for the moment. >> >> >> >> [...] >> >> > At the end of this the domain is frozen. Is this a known issue? Any >> >> > pointers as to how to debug this? Where does xl pipe its debug >> >> > messages to? >> >> >> >> /var/log/xen/xl-<domname>.log. You can also do "xl -vvv <command>" to >> >> get some additional debug output. >> >> >> > Yes. the logs would be great. Also, by frozen, do you mean the domain >> > remains >> > in "suspended" state? or is Windows hung? >> >> Not sure what the difference between Windows being suspended and hung >> is. Here is the xl list output: >> Name ID Mem VCPUs State >> Time(s) >> Domain-0 0 2914 4 r----- >> 1259.0 >> win7 15 1019 2 ---ss- >> 0.3 >> >> Here is the log: >> Saving to win7chk new xl format (info 0x0/0x0/255) >> libxl: debug: libxl_dom.c:378:libxl__domain_suspend_common_callback >> Calling xc_domain_shutdown on HVM domain >> libxl: debug: libxl_dom.c:438:libxl__domain_suspend_common_callback >> wait for the guest to suspend >> libxl: debug: libxl_dom.c:450:libxl__domain_suspend_common_callback >> guest has suspended >> xc: debug: outbuf_write: 4194304 > 90092@16687124 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: debug: outbuf_write: 4194304 > 4169716@12607500 >> xc: detail: delta 9991ms, dom0 27%, target 0%, sent 863Mb/s, dirtied >> 0Mb/s 0 pages >> xc: detail: Total pages sent= 263168 (0.25x) >> xc: detail: (of which 0 were fixups) >> xc: detail: All memory is saved >> xc: detail: Save exit rc=0 >> libxl: debug: libxl_dom.c:534:libxl__domain_save_device_model Saving >> device model state to /var/lib/xen/qemu-save.15 >> libxl: debug: libxl_dom.c:546:libxl__domain_save_device_model Qemu >> state is 7204 bytes >> >> > Ok. I see a "HVM shutdown". But where is the resume? > Going through the libxl code, one obvious difference I see between xl's > implementation of save > and the old xm implementation is, xl calls "xc_domain_unpause" while the xm > implementation > calls xc_domain_resume. > > Just in case, have you tried the same with xm save -c ? > shriram xm save -c doesn't seem to work at all. root@tubuntu:/etc/xen# xm save -c win7 win7chk Error: Timeout waiting for domain 2 to suspend [2011-05-05 13:55:43 1615] DEBUG (XendCheckpoint:124) [xc_save]: /usr/lib/xen/bin/xc_save 22 2 0 0 0 [2011-05-05 13:55:43 1615] INFO (XendCheckpoint:423) xc_save: failed to get the suspend evtchn port [2011-05-05 13:55:43 1615] INFO (XendCheckpoint:423) [2011-05-05 13:55:43 1615] DEBUG (XendCheckpoint:394) suspend [2011-05-05 13:55:43 1615] DEBUG (XendCheckpoint:127) In saveInputHandler suspend [2011-05-05 13:55:43 1615] DEBUG (XendCheckpoint:129) Suspending 2 ... [2011-05-05 13:55:43 1615] DEBUG (XendDomainInfo:524) XendDomainInfo.shutdown(suspend) [2011-05-05 13:55:43 1615] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch [2011-05-05 13:56:44 1615] DEBUG (XendDomainInfo:1881) XendDomainInfo.handleShutdownWatch [2011-05-05 13:56:44 1615] INFO (XendCheckpoint:423) xc: error: Suspend request failed: Internal error [2011-05-05 13:56:44 1615] INFO (XendCheckpoint:423) xc: error: Domain appears not to have suspended: Internal error [2011-05-05 13:56:44 1615] ERROR (XendCheckpoint:185) Save failed on domain win7 (2) - resuming. Traceback (most recent call last): File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 146, in save forkHelper(cmd, fd, saveInputHandler, False) File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 395, in forkHelper inputHandler(line, child.tochild) File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendCheckpoint.py", line 131, in saveInputHandler dominfo.waitForSuspend() File "/usr/local/lib/python2.6/dist-packages/xen/xend/XendDomainInfo.py", line 2998, in waitForSuspend raise XendError(msg) XendError: Timeout waiting for domain 2 to suspend [2011-05-05 13:56:44 1615] DEBUG (XendDomainInfo:3135) XendDomainInfo.resumeDomain(2) _______________________________________________ Xen-devel mailing list Xen-devel@xxxxxxxxxxxxxxxxxxx http://lists.xensource.com/xen-devel

©2013 Xen Project, A Linux Foundation Collaborative Project. All Rights Reserved.
Linux Foundation is a registered trademark of The Linux Foundation.
Xen Project is a trademark of The Linux Foundation.