From mboxrd@z Thu Jan 1 00:00:00 1970 From: Keir Fraser Subject: Re: Xen 3.1 - Can't run Fedora Core 1 PV Date: Thu, 12 Jul 2007 11:52:40 +0100 Message-ID: References: <20070712104602.GA4213@craig-wood.com> Mime-Version: 1.0 Content-Type: text/plain; charset="US-ASCII" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070712104602.GA4213@craig-wood.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xensource.com Errors-To: xen-devel-bounces@lists.xensource.com To: Nick Craig-Wood , xen-devel@lists.xensource.com List-Id: xen-devel@lists.xenproject.org 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" 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 > 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!