From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: AP Xen <apxeng@gmail.com>
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: xl save -c issues with Windows 7 Ultimate
Date: Thu, 5 May 2011 19:31:21 -0700 [thread overview]
Message-ID: <BANLkTikY9UChqO2Lx9mvqbeUkaL3=LvqyA@mail.gmail.com> (raw)
In-Reply-To: <BANLkTin6Rz=GpKZbO2ug7kMt2BERxixbUw@mail.gmail.com>
[-- Attachment #1.1: Type: text/plain, Size: 10061 bytes --]
On Thu, May 5, 2011 at 2:01 PM, AP Xen <apxeng@gmail.com> wrote:
> On Thu, May 5, 2011 at 7:42 AM, Shriram Rajagopalan <rshriram@cs.ubc.ca>
> wrote:
> > On Tue, May 3, 2011 at 2:17 PM, AP Xen <apxeng@gmail.com> wrote:
> >>
> >> On Tue, May 3, 2011 at 7:09 AM, Shriram Rajagopalan <rshriram@cs.ubc.ca
> >
> >> wrote:
> >> > On Tue, May 3, 2011 at 6:01 AM, Ian Campbell <Ian.Campbell@citrix.com
> >
> >> > 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)
>
> Any debug output from xen? "xm dmesg"
shriram
[-- Attachment #1.2: Type: text/html, Size: 12679 bytes --]
[-- Attachment #2: Type: text/plain, Size: 138 bytes --]
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel
next prev parent reply other threads:[~2011-05-06 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-29 19:28 xl save -c issues with Windows 7 Ultimate AP Xen
2011-05-03 11:07 ` George Dunlap
2011-05-03 19:04 ` AP Xen
2011-05-06 22:01 ` AP Xen
2011-05-03 13:01 ` Ian Campbell
2011-05-03 14:09 ` Shriram Rajagopalan
2011-05-03 14:31 ` Ian Campbell
2011-05-03 14:42 ` Tim Deegan
2011-05-03 16:32 ` Shriram Rajagopalan
2011-05-03 16:35 ` Brendan Cully
2011-05-03 19:17 ` AP Xen
2011-05-05 14:42 ` Shriram Rajagopalan
2011-05-05 21:01 ` AP Xen
2011-05-06 2:31 ` Shriram Rajagopalan [this message]
2011-05-03 19:15 ` AP Xen
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='BANLkTikY9UChqO2Lx9mvqbeUkaL3=LvqyA@mail.gmail.com' \
--to=rshriram@cs.ubc.ca \
--cc=Ian.Campbell@citrix.com \
--cc=apxeng@gmail.com \
--cc=xen-devel@lists.xensource.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).