From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: [PATCH] [xend] fix coredump-{restart, destroy} on_crash actions Date: Tue, 27 Jul 2010 11:59:38 -0600 Message-ID: <4C4F1E8A.8040202@novell.com> References: <4C4EF697.8060506@novell.com> <19535.3133.638714.871445@mariner.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <19535.3133.638714.871445@mariner.uk.xensource.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: Ian Jackson Cc: xen-devel List-Id: xen-devel@lists.xenproject.org Ian Jackson wrote: > Jim Fehlig writes ("[Xen-devel] [PATCH] [xend] fix coredump-{restart, destroy} on_crash actions"): > >> After all of these years, more fallout from xen-api and legacy xmlrpc >> integration. Can't say I'll miss xend :-). >> >> Please apply to xen-4.0-testing. >> > > We'll apply this to xen-unstable first, as Keir says. Don't. > However, I'm > not sure I fully understand how this patch works. > Well, I'm not surprised that you are confused. As it turns out, we have an internal patch that fixes a bug wrt 'xm create -x ...' not working - and that patch is causing the bug described here. Unfortunately it was never upstreamed, allowing such regressions to be spotted by others:-(. Sorry for the noise. Regards, Jim