Re: [Xen-devel] xm save - not working on 32-bit PAE host (-testing)

[Matt Ayres <matta@xxxxxxxxxxxx>]

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!

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel