From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser 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 Message-ID: References: <4DCA5B3A0200007800040EC4@vpn.id2.novell.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <4DCA5B3A0200007800040EC4@vpn.id2.novell.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Jan Beulich , rshriram@cs.ubc.ca Cc: "xen-devel@lists.xensource.com" , Ian Campbell List-Id: xen-devel@lists.xenproject.org On 11/05/2011 08:47, "Jan Beulich" 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