[Xen-devel] Re: Test results for save/restore with upstream pv_ops domU kernels, 2.6.33 problems

[Pasi Kärkkäinen <pasik@xxxxxx>]

On Fri, Jan 29, 2010 at 10:35:32AM +0000, Ian Campbell wrote:
> On Thu, 2010-01-28 at 21:25 +0000, Pasi Kärkkäinen wrote:
> > Hello,
> > 
> > I just tried some save/restore tests with Fedora 12 Linux 2.6.31.12 kernels.
> > The exact Fedora kernel versions are: 2.6.31.12-174.2.3.fc12.i686.PAE and 
> > 2.6.31.12-174.2.3.fc12.x86_64.
> > 
> > Dom0 for these tests was CentOS 5.4 (Xen 3.1.2).
> > 
> > - F12 32bit 1vcpu PV guest: 
> >     save+restore OK, BUG() in guest dmesg after restore [1]
> > 
> > - F12 64bit 1vcpu PV guest:
> >     save+restore OK, BUG() in guest dmesg after restore [2]
> 
> I think those are the same underlying bug and are fixed by 
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=commit;h=777df2b017ef34b2d1a172bf769582158839a860
> 
> > 
> > - F12 32bit 2vcpu PV guest:
> >     save doesn't work, guest stays as "migrating-f12test32" in "xm list" 
> > forever and has to be "xm destroy"ed.
> > 
> > - F12 64bit 2vcpu PV guest:
> >     save doesn't work, guest stays as "migrating-f12test64" in "xm list" 
> > forever and has to be "xm destroy"ed.
> > 
> > 
> > What's the best way to debug failing "xm save" ? There was no errors in "xm 
> > log", or in "xm dmesg".
> 
> I think you might see some stuff in /var/log/xen/something but I don't
> have any particular tips apart from "add printf/printk".
> 
> > Also the guest "xm console" doesn't show anything before it dies.
> > 
> > Is it possible some of the save/restore related patches didn't make it to 
> > 2.6.31.x stable kernels? 
> 
> AFAIK they only went into the 2.6.32 stable branch. Unfortunately I
> think the 2.6.31 stable series has come to an end now.
> 

Hello,

An user on ##xen just reported that 2.6.32.9 save/restore works OK,
but 2.6.33 fails/crashes.

Some of the patches that went to 2.6.32.x are not in 2.6.33?

-- Pasi


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