From mboxrd@z Thu Jan 1 00:00:00 1970 From: Andreas Olsowski Subject: Re: pv guests die after failed migration Date: Sat, 15 Oct 2011 12:35:50 +0200 Message-ID: <4E996206.4050500@leuphana.de> References: <4E786015.80603@leuphana.de> <1316546879.5182.26.camel@dagon.hellion.org.uk> <4E7C37BD.2000706@leuphana.de> <1316764045.23371.100.camel@zakaz.uk.xensource.com> <4E7C4E44.70508@leuphana.de> <1317225159.26672.87.camel@zakaz.uk.xensource.com> <4E98DF51.9070907@leuphana.de> <1318657499.11016.12.camel@dagon.hellion.org.uk> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <1318657499.11016.12.camel@dagon.hellion.org.uk> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Ian Campbell Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org On 10/15/2011 07:44 AM, Ian Campbell wrote: > On Sat, 2011-10-15 at 02:18 +0100, Andreas Olsowski wrote: >> It seems this still has not made it into 4.1-testing. > > I'm afraid I've not had time to "figure out how to automatically select > which guests are capable of a cooperative resume and which are not." so > it hasn't been fixed in xen-unstable either AFAIK. > Wouldnt just assuming all of them do fix a bigger percentage of systems than leaving it the way it is? > I'm also still interested in confirmation to the question I asked in the > mail you just replied to. > Oh, i thought i allready did. > Are you saying that you don't see the "failed for domain %u" message > immediately after the xc_domain_resume call? > > + if (xc_domain_resume(ctx->xch, domid, 1)) { > LIBXL__LOG_ERRNO(ctx, LIBXL__LOG_ERROR, > "xc_domain_resume failed for domain %u", > domid); > > That would be pretty odd... Yes that is what i am saying: root@memoryana:/var/log/xen# cat xl-testmig.log Waiting for domain testmig (domid 2) to die [pid 13349] Domain 2 is dead Done. Exiting now -- Andreas