From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Fehlig Subject: Re: [PATCH] Error in Xend-API method VM_set_actions_after_crash Date: Tue, 27 Jul 2010 09:02:16 -0600 Message-ID: <4C4EF4F8.5050106@novell.com> References: <3958B14F314B884890EEE2F4CCDAB6A601122BDC5527@ABGEX73E.FSC.NET> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: <3958B14F314B884890EEE2F4CCDAB6A601122BDC5527@ABGEX73E.FSC.NET> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: "Dube, Lutz" Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Dube, Lutz wrote: > Xend-API defines the method VM_set_actions_after_crash with valid actio= n > names coredump_and_destroy, coredump_and_restart,... . These values > have to > be converted into internal representation =E2=80=9Ccoredump-destroy=E2=80= =9D, > =E2=80=9Ccoredump-restart=E2=80=9D, =E2=80=A6 > otherwise start of the domain is rejected. > Same error occurs, if I try to create a VM using the Xend-API with > actions_after_crash set to coredump_and_destroy. I've had similar reports when using legacy python config files and xend's xmlrpc interface. I'll post a patch for that soon. Your patch looks good, although I've not tested it. > =20 > Could you please apply my patch to xen-4-0-testing, too. It sounds like this will be the primary target for xend fixes going forward. How long will, if at all, will xend bug fixes be applied to -unstable? Regards, Jim