From mboxrd@z Thu Jan  1 00:00:00 1970
From: "Greg Brackley" <greg.brackley-gmane@lucidsolutions.co.nz>
Subject: Re: Problem getting x86_64 dom0 to boot on a FC4 machine
Date: Mon, 3 Oct 2005 19:58:51 +1300
Message-ID: <dhqkri$3ht$1@sea.gmane.org>
References: <dhlv7q$sna$1@sea.gmane.org> <433E998D.5090004@us.ibm.com>
Return-path: <xen-devel-bounces@lists.xensource.com>
List-Unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=unsubscribe>
List-Post: <mailto:xen-devel@lists.xensource.com>
List-Help: <mailto:xen-devel-request@lists.xensource.com?subject=help>
List-Subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-devel>,
	<mailto:xen-devel-request@lists.xensource.com?subject=subscribe>
Sender: xen-devel-bounces@lists.xensource.com
Errors-To: xen-devel-bounces@lists.xensource.com
To: xen-devel@lists.xensource.com
List-Id: xen-devel@lists.xenproject.org

"Andrew Theurer" <habanero@us.ibm.com> wrote in message 
news:433E998D.5090004@us.ibm.com...
> with 'yum update" and I have not had this happen again.  Also, I have

Thanks for that idea. I had already done a yum update, so this didn't help.

Out of band Larry Hovind recommended compiling the RAID support into the 
kernel (c.f. as modules). I did this for all multiple device support 
(RAID/LVM), and then rebuilt the initrd (specifying that the modules were 
now built-in). I can now get the privileged domain 0 booting. I don't 
understand what limitation it has overcome, but it does get it up and going.

Still need to get a Marvell SATA driver going, and overcome a 
dma/bonding/vlan/ethernet kernel oops.

Thanks,

Greg :-)