[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [Xen-devel] Xen 3.1 - Can't run Fedora Core 1 PV
- To: Nick Craig-Wood <nick@xxxxxxxxxxxxxx>, <xen-devel@xxxxxxxxxxxxxxxxxxx>
- From: Keir Fraser <keir@xxxxxxxxxxxxx>
- Date: Thu, 12 Jul 2007 14:11:19 +0100
- Delivery-date: Thu, 12 Jul 2007 06:09:14 -0700
- List-id: Xen developer discussion <xen-devel.lists.xensource.com>
- Thread-index: AcfEcsQtApiKDDBmEdyvtwAX8io7RQAE16Bn
- Thread-topic: [Xen-devel] Xen 3.1 - Can't run Fedora Core 1 PV
My current guess is that this is a kernel version issue. Have you tried
using your old (pre-3.1) domU kernel with the FC1 image on Xen 3.1?
On 12/7/07 11:52, "Keir Fraser" <keir@xxxxxxxxxxxxx> wrote:
> Is this using an up-to-date kernel image? I.e., we think the problem occurs
> when we hit the init task?
> -- Keir
> On 12/7/07 11:46, "Nick Craig-Wood" <nick@xxxxxxxxxxxxxx> wrote:
>> I can't run a Fedora Core 1 image PV - it SEGVs on start. This is a
>> show stopper for me upgrading to xen 3.1 as we have quite a few FC1
>> I've written a bug report here, but I'm not sure anyone ever looks at
>> Here are the details...
>> Xen 3.1 runs most of my domUs just fine, windows etc, but it doesn't
>> run a Fedora Core 1 image. It hangs at 100% cpu usage just after
>> "Freeing kernel memory".
>> If I mount the FC1 image on dom0 and chroot into it I get
>> # chroot . /bin/bash
>> Segmentation fault
>> I've put a small ext2 filing system here (built from a virgin FC1
>> image) which demonstrates the problem
>> Mounting it and chrooting from dom0 under Xen 3.1 gives the SEGV.
>> Doing the same from Xen 3.0.3 , Xen 3.0.4 and Debian testing works
>> I've verified that the same thing happens on the binary download from
>> the xen web site (xen-3.1.0-install-x86_32p.tgz) dated June 1st so it
>> isn't just my dodgy compiling skills!
> Xen-devel mailing list
Xen-devel mailing list