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] Xen 3.1 - Can't run Fedora Core 1 PV

To: Ian Campbell <Ian.Campbell@xxxxxxxxxxxxx>, Nick Craig-Wood <nick@xxxxxxxxxxxxxx>
Subject: Re: [Xen-devel] Xen 3.1 - Can't run Fedora Core 1 PV
From: Keir Fraser <keir@xxxxxxxxxxxxx>
Date: Fri, 13 Jul 2007 07:31:32 +0100
Cc: xen-devel@xxxxxxxxxxxxxxxxxxx
Delivery-date: Thu, 12 Jul 2007 23:26:05 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <1184262714.1152.81.camel@xxxxxxxxxxxxxxxxxxxxx>
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/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>, <mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
Sender: xen-devel-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AcfFF3O8sjumpDEKEdyTSAAWy6hiGQ==
Thread-topic: [Xen-devel] Xen 3.1 - Can't run Fedora Core 1 PV
User-agent: Microsoft-Entourage/11.3.3.061214
On 12/7/07 18:51, "Ian Campbell" <Ian.Campbell@xxxxxxxxxxxxx> wrote:

>> The above fails for xen 3.1 but succeeds (you get a shell) for xen 3.0.4 and
>> 3.0.3
> 
> FC1 had some odd stuff going on with the vdso -- it comes up any time
> upstream tries to touch the compat vdso code.
> 
> You could try enabling/disabling COMPAT_VDSO in your kernel
> configuration, see what happens.
> 
> It'd also be interesting to know which libc is getting linked in within
> the chroot.

Yes, it's definitely VDSO related as it crashes in linux-gate.so. 3.0.4
kernels work just fine with 3.1, so that is the correct fix for this
situation.

 -- Keir


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