xen-devel.lists.xenproject.org archive mirror
 help / color / mirror / Atom feed
From: Shriram Rajagopalan <rshriram@cs.ubc.ca>
To: xen-devel@lists.xensource.com
Subject: xl/xm save -c fails - set_vcpucontext EOPNOTSUPP (was Re: xl save -c issues with Windows 7 Ultimate)
Date: Mon, 9 May 2011 18:06:03 -0500	[thread overview]
Message-ID: <BANLkTi=a4=uNLYSA+0FEX+oX=iBmStn3aA@mail.gmail.com> (raw)


[-- Attachment #1.1: Type: text/plain, Size: 7116 bytes --]

I was testing xl/xm checkpoint with the latest c/s in the repo, 23300.
neither xl nor xm seem to work. The error code is 95 (EOPNOTSUPP).

Migration works but not checkpointing. While doing a xc_domain_resume,
the "modify_returncode" phase (for suspend_cancel) fails. Tracing through
the control flow, I found that the hypercall for set_vcpucontext
(in do_xen_hypercall() from xc_private.c) fails with this error code.

I have tested this with a 64-bit 2.6.39 and 32-bit 2.6.18 pv domU.
Any help would be great.

shriram

On Fri, May 6, 2011 at 5:01 PM, AP Xen <apxeng@gmail.com> wrote:

> On Tue, May 3, 2011 at 4:07 AM, George Dunlap
> <George.Dunlap@eu.citrix.com> wrote:
> > Have you tried it with other operating systems and found it to work?
> > I.e., is it something specific to Windows 7, or is it a general HVM /
> > Windows problem?
>
> I tried this with CentOS 5.6 and saw the same behavior.
>
> root@ubuntu:~# xl -vvv save -c centos /etc/xen/centoschk
> Saving to /etc/xen/centoschk new xl format (info 0x0/0x0/255)
> libxl: debug: libxl_dom.c:384:libxl__domain_suspend_common_callback
> issuing PVHVM suspend request via XenBus control node
> libxl: debug: libxl_dom.c:389:libxl__domain_suspend_common_callback
> wait for the guest to acknowledge suspend request
> libxl: debug: libxl_dom.c:434:libxl__domain_suspend_common_callback
> guest acknowledged suspend request
> 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: type fail: page 0 mfn 000f2000
> xc: detail: type fail: page 1 mfn 000f2001
> xc: detail: type fail: page 2 mfn 000f2002
> xc: detail: delta 9371ms, dom0 25%, target 0%, sent 920Mb/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.7
> libxl: debug: libxl_dom.c:546:libxl__domain_save_device_model Qemu
> state is 7204 bytes
>
>
> root@ubuntu:~# xl list
> Name                                        ID   Mem VCPUs      State
> Time(s)
> Domain-0                                    0  2914     4     r-----
>  6576.4
> centos                                        7  1019     2     ---ss-
> 575.4
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xensource.com
> http://lists.xensource.com/xen-devel
>

[-- Attachment #1.2: Type: text/html, Size: 8408 bytes --]

[-- Attachment #2: Type: text/plain, Size: 138 bytes --]

_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xensource.com
http://lists.xensource.com/xen-devel

             reply	other threads:[~2011-05-09 23:06 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-09 23:06 Shriram Rajagopalan [this message]
2011-05-10  8:41 ` xl/xm save -c fails - set_vcpucontext EOPNOTSUPP (was Re: xl save -c issues with Windows 7 Ultimate) Ian Campbell
2011-05-10 14:52   ` Shriram Rajagopalan
2011-05-10 15:02     ` Jan Beulich
2011-05-10 15:50       ` Shriram Rajagopalan
2011-05-10 15:55         ` Ian Campbell
2011-05-10 16:03         ` Jan Beulich
2011-05-11  2:30           ` Shriram Rajagopalan
2011-05-11  7:47             ` Jan Beulich
2011-05-11 18:37               ` Shriram Rajagopalan
2011-05-11 19:50                 ` Shriram Rajagopalan
2011-05-13 10:00                   ` Jan Beulich
2011-05-14 22:15                     ` Shriram Rajagopalan
2011-05-16 12:02                       ` Jan Beulich
2011-05-17  1:48                         ` Shriram Rajagopalan
2011-05-24 19:24                           ` AP Xen
2011-05-24 20:09                             ` Keir Fraser
2011-05-25  7:15                               ` Jan Beulich
2011-05-25  7:53                                 ` AP Xen
2011-05-12  8:10               ` Keir Fraser
  -- strict thread matches above, loose matches on Subject: below --
2011-05-16  6:05 Jan Beulich

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='BANLkTi=a4=uNLYSA+0FEX+oX=iBmStn3aA@mail.gmail.com' \
    --to=rshriram@cs.ubc.ca \
    --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).