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] need known working 64-bit upstream kernel config file fo

To: "Pasi Kärkkäinen" <pasik@xxxxxx>
Subject: RE: [Xen-devel] need known working 64-bit upstream kernel config file for PV guest
From: Dan Magenheimer <dan.magenheimer@xxxxxxxxxx>
Date: Thu, 13 May 2010 13:49:01 -0700 (PDT)
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 13 May 2010 13:52:11 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <20100513203053.GJ17817@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>
References: <8feac03c-52fc-4f0b-bf8d-7b9bdd3c2ee0@default 20100513203053.GJ17817@xxxxxxxxxxx>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Hi Pasi --

Thanks for the reply.  Hope your trip home went well!

> What exact upstream kernel.org kernels you are trying to make work?

Any working x86_64 config file for any upstream kernel >=2.6.32
would be fine.  I have a 32-bit config file that works fine for 2.6.27
up to 2.6.32 (and I think for 2.6.33... trying again now).

I've just found out that my config file does NOT work for x86
2.6.34-rc5 though.  Not sure why...

> I assume you're familiar with debugging crashing guest kernels?
> If not, see here:
> http://wiki.xensource.com/xenwiki/XenCommonProblems
> The chapter "My Xen PV guest kernel crashes, how can I debug it?".

I've done that before but these panics are all very early and
I have a tombstone for each panic.  I thought enough people are
using upstream kernels that I must just have some CONFIG_
incorrect.  Perhaps I am wrong and I am the first one to
try these upstream kernels (at least in a PV domain)?

It seems that all the failures I am seeing have some kind
of syscall in the stacktrace and they happen early enough
in init that I suppose it is possible that this is the very
first syscall that is failing.


Xen-devel mailing list