WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-devel

RE: [Xen-devel] pv 2.6.31 (kernel.org) and save/migrate, domU BUG()

To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Subject: RE: [Xen-devel] pv 2.6.31 (kernel.org) and save/migrate, domU BUG()
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Sun, 8 Nov 2009 08:54:23 -0800 (PST)
Cc: "Xen-Devel \(E-mail\)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Sun, 08 Nov 2009 08:57:18 -0800
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20091108154153.GM1434@xxxxxxxxxxx>
List-help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-id: Xen developer discussion <xen-devel.lists.xensource.com>
List-post: <mailto:xen-devel@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > Ok, so it appears there is something problematic with
> > saving an upstream kernel.  It might be (partially) fixed
> > in Fedora 12 or maybe there is some other environmental
> > difference which makes save fail entirely on my system.
> > 
> 
> Yeah, fedora kernel has some patches, but it should be pretty 
> close to upstream kernel..
> 
> btw was your guest UP or SMP? Mine was UP..

Mine was SMP... switching to UP I can now save.  BUT...
restore doesn't seem to quite work.  The restore completes
but I get no response from the VNC console.  When I
use a tty console, after restore, I am getting
an infinite dump of

WARNING: at arch/x86/time.c:180 xen_sched_clock+0x2b

(see attached).

Did you try restore on Fedora 12?
 
> > > > The results explain why I can get it to run on
> > > > one machine (an older laptop) and not run on another
> > > > machine (a Nehalem system)... looks like this is maybe
> > > > related to the cpuid-extended-topology-leaf bug that Jeremy
> > > > sent a fix for upstream recently.
> > > 
> > > Did you try with that patch applied? 
> > 
> > No, the patch wasn't posted, just a pull request to Linus,
> > so I don't have the patch (and am not a git expert so
> > am not sure how to get it).
> > 
> > http://lists.xensource.com/archives/html/xen-devel/2009-11/msg00182.html
> >
> > So I'll try it again when .6 or .7 is available.
> 
> See here for changelog:
> http://git.kernel.org/?p=linux/kernel/git/jeremy/xen.git;a=shortlog;h=bugfix
> 
> You can get the diffs/patches from there using the links..

Thanks.  Yes, Jeremy's patch allows 2.6.31.5 (in a PV domain)
to completely boot on my Nehalem box.

Attachment: restore.out
Description: Binary data

_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-devel
<Prev in Thread] Current Thread [Next in Thread>