From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Magenheimer Subject: RE: need known working 64-bit upstream kernel config file for PV guest Date: Fri, 14 May 2010 09:58:47 -0700 (PDT) Message-ID: References: <20100513203053.GJ17817@reaktio.net> <324eaac0-9a5e-427b-9529-907742f7c23d@default 20100514054659.GN17817@reaktio.net abca62c2-7d9e-475d-bb18-0f60e4b5ecd3@default> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Return-path: In-Reply-To: List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: =?UTF-8?B?IlBhc2kgS8Okcmtrw6RpbmVuIg==?= Cc: xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org > But I hadn't noticed the problem in the earlier part of > the boot before you pointed it out. > I'm beginning to suspect that there is a bug in 64-bit > upstream kernels that is exposed in nash (the lightweight > shell that gets bundled in a RedHat initrd). If so, > it will be very difficult to track down, though clearly > it is fixed in one of the many Fedora kernel patches. > So I am going to give up on 64-bit upstream kernels > for now so I can get some other things done and > come back to this later. To add one more very interesting piece of data, booting a 2.6.32 32-bit kernel.org kernel in a PV guest works, while booting a 2.6.32.13 32-bit kernel.org kernel doesn't... same config file! And the failure looks very similar to the one I've been seeing on several x86_64 kernel.org kernels. I'll confirm that I can reproduce this, and then post as a separate thread.