2 messages in com.xensource.lists.xen-bugs[Xen-bugs] [Bug 993] New: Xen 3.1: ca...
FromSent OnAttachments
bugz...@lists.xensource.com11 Jun 2007 01:48 
bugz...@lists.xensource.com10 Jul 2007 09:47 
Subject:[Xen-bugs] [Bug 993] New: Xen 3.1: can't run PV Fedora Core 1 Images any more
From:bugz...@lists.xensource.com (bugz@lists.xensource.com)
Date:06/11/2007 01:48:12 AM
List:com.xensource.lists.xen-bugs

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

Summary: Xen 3.1: can't run PV Fedora Core 1 Images any more Product: Xen Version: unspecified Platform: x86 OS/Version: Linux Status: NEW Severity: major Priority: P2 Component: Hypervisor AssignedTo: xen-@lists.xensource.com ReportedBy: ni@craig-wood.com

I've just built Xen 3.1 x86 32 bit with PAE from source.

Both the dom0 and PV domU are running 2.6.18.8 which I made by using "make mkpatches" and applying the patch produced to a vanilla 2.6.18.8 as donwloaded from kernel.org. There was one reject which I ascertained was a patch that had already been applied to the Xen kernel.

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.