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/
Home Products Support Community News


RE: [Xen-devel] can't boot upstream kernel in PV guest with recent xen t

To: Keir Fraser <keir.fraser@xxxxxxxxxxxxx>, "Xen-Devel (xen-devel@xxxxxxxxxxxxxxxxxxx)" <xen-devel@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-devel] can't boot upstream kernel in PV guest with recent xen trees
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Thu, 13 May 2010 07:46:33 -0700 (PDT)
Delivery-date: Thu, 13 May 2010 07:49:34 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <C81167AF.14212%keir.fraser@xxxxxxxxxxxxx>
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>
References: <8d329343-5276-4de6-99d0-29a6ad3e2b7f@default C81167AF.14212%keir.fraser@xxxxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
> > Is it possible some bug fix was recently applied into
> > all three xen trees that creates or exposes a problem
> > in upstream kernels built with certain CONFIG_ options
> > booting in PV guests? (I've also attached the config
> > file used to build the 2.6.32 kernel that panic'ed.)
> >
> > Or hopefully someone will find this familiar or
> > reproducible and can suggest an answer? I'm dead
> > in the water on one of my activities until I can
> > get an upstream kernel booting in a PV guest
> Try 4.0.0 release. I'm sure people have been booting pv_ops kernels
> with
> that okay. I think this problem is somehow specific to your test
> machine.

Thanks for the reply!

After much teeth-gnashing and hair-pulling, I think I figured
out the problem -- though not yet a full solution.  When I
follow the exact build process and use the same config file
to boot an upstream kernel in a *64-bit* VM, it panics
every time (including on 4.0.0).  On a *32-bit* VM,
it boots fine every time.

I suspect that I have never (before last week) attempted
to build/boot an upstream kernel in a 64-bit VM.  I further
suspect that there is something in the config file
that I am using (possibly something annoyingly stupid)
that doesn't cause a 64-bit *build* to fail but
does cause the 64-bit boot to fail.

Xen-devel mailing list

<Prev in Thread] Current Thread [Next in Thread>