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

[Xen-devel] Xen 3.1 - Can't run Fedora Core 1 PV

To: xen-devel@xxxxxxxxxxxxxxxxxxx
Subject: [Xen-devel] Xen 3.1 - Can't run Fedora Core 1 PV
From: Nick Craig-Wood <nick@xxxxxxxxxxxxxx>
Date: Thu, 12 Jul 2007 11:46:02 +0100
Delivery-date: Thu, 12 Jul 2007 03:43:54 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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
User-agent: Mutt/1.5.13 (2006-08-11)
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
images.

I've written a bug report here, but I'm not sure anyone ever looks at
bugzilla!

  http://bugzilla.xensource.com/bugzilla/show_bug.cgi?id=993

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

  http://www.craig-wood.com/nick/pub/fedora_demo.gz

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
fine.

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!

-- 
Nick Craig-Wood <nick@xxxxxxxxxxxxxx> -- http://www.craig-wood.com/nick

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