From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matt Ayres Subject: Re: xm save - not working on 32-bit PAE host (-testing) Date: Tue, 14 Mar 2006 12:16:23 -0500 Message-ID: <4416FA67.70602@tektonic.net> References: <4416B800.2020307@tektonic.net> <20060314170450.GC19635@leeni.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20060314170450.GC19635@leeni.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: Ewan Mellor Cc: "xen-devel@lists.xensource.com" List-Id: xen-devel@lists.xenproject.org Ewan Mellor wrote: > On Tue, Mar 14, 2006 at 07:33:04AM -0500, Matt Ayres wrote: > >> Hi, >> >> "xm save domID savefile" will create a file around 715 bytes long and >> then just sit there forever. This is with the latest 3.0-testing. >> >> 1) Is this a known issue? If it is, is it fixed in -unstable yet? >> 2) If it is not a known issue, what is required on my end to help the >> progress of getting the save feature fixed? > > Having just poked around your system, Matt, it turns out that you've turned > off CONFIG_HOTPLUG_CPU when compiling your guest. CONFIG_HOTPLUG_CPU is > required for save/restore; you actually get a message to that effect on the > guest's console when you try to suspend the guest. > > It would be nice if the tools recognised the failure, and didn't just hang. > Feel free to file a bug to that effect. As it is, this is "expected > behaviour" at the moment. > Thanks Ewan!