From: Keir Fraser <keir@xen.org>
To: Jan Beulich <JBeulich@novell.com>, rshriram@cs.ubc.ca
Cc: "xen-devel@lists.xensource.com" <xen-devel@lists.xensource.com>,
Ian Campbell <Ian.Campbell@citrix.com>
Subject: Re: xl/xm save -c fails - set_vcpucontext EOPNOTSUPP (was Re: xl save -c issues with Windows 7 Ultimate)
Date: Thu, 12 May 2011 09:10:17 +0100 [thread overview]
Message-ID: <C9F15479.2D2C3%keir@xen.org> (raw)
In-Reply-To: <4DCA5B3A0200007800040EC4@vpn.id2.novell.com>
On 11/05/2011 08:47, "Jan Beulich" <JBeulich@novell.com> wrote:
> The question is whether there are other inconsistencies lurking, and
> hence whether it wouldn't be better to mark a vCPU on which setting
> the context failed, not allowing it to resume or have its context
> obtained anymore. That appears quite drastic though - Keir, what's
> your opinion here?
Hm, I think overall we just need to get the error-path handling in this
function correct. I think it'll be a bit ugly to kludge around that.
-- Keir
next prev parent reply other threads:[~2011-05-12 8:10 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-09 23:06 xl/xm save -c fails - set_vcpucontext EOPNOTSUPP (was Re: xl save -c issues with Windows 7 Ultimate) Shriram Rajagopalan
2011-05-10 8:41 ` 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 [this message]
-- 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=C9F15479.2D2C3%keir@xen.org \
--to=keir@xen.org \
--cc=Ian.Campbell@citrix.com \
--cc=JBeulich@novell.com \
--cc=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).