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/
Home Products Support Community News


Re: [Xen-devel] Cannot open root device for dom0

To: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Cannot open root device for dom0
From: stevegt@xxxxxxxxxxxxx
Date: Sat, 17 Jan 2004 09:33:09 -0800
Cc: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>, xen-devel@xxxxxxxxxxxxxxxxxxxxx
Delivery-date: Sat, 17 Jan 2004 17:33:33 +0000
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: <E1Ahogq-0006D9-00@xxxxxxxxxxxxxxxxxxxx>
References: <Ian.Pratt@xxxxxxxxxxxx> <E1Ahmfg-0004Bp-00@xxxxxxxxxxxxxxxxxxxx> <E1Ahogq-0006D9-00@xxxxxxxxxxxxxxxxxxxx>
User-agent: Mutt/1.3.28i
Okay, I've done another pull and rebuilt xenolinux 1.2 with both gcc
2.95.4 and gcc 3.0.  Both of these boot dom0 and find hda just fine.
The only thing that's changed is the code changed by the pull.

(Note that I'm talking about xenolinux only here -- I'm still using the
gcc 3.0 Xen -- haven't tried Xen with gcc 2.95 since I hit those parsing
errors on Thursday.)

On Sat, Jan 17, 2004 at 11:32:30AM +0000, Steven Hand wrote:
> >> Does anyone know why the (failed) modprobe attempt is happening at all,
> >> since the ext3 driver is built in?
> >
> >It's actually the xenolinux block device driver that it's trying
> >to modprobe.
> Indeed; in more detail, the modprobe happened because major device 3 (ide0) 
> was not registered with the blkdev layer; and this happened because 
> something was screwed in the xenolinux 'probe' (where at start of day it
> asks Xen about what devices exist, etc). Given that this code has all just
> been rewritten (in Xen) to use red-black trees in place of a hash table so
> that order is deterministic, I reckon that's the culprit. 

I suspect this was in fact the culprit -- possibly I grabbed the code
when it was in an intermediate state (Thursday evening Pacific time).
> Anyway, that's just for info -- I believe it's fixed now, right?

We can call this fixed.  Thanks everyone for your help.  

Stephen G. Traugott  (KG6HDQ)
UNIX/Linux Infrastructure Architect, TerraLuna LLC
http://www.stevegt.com -- http://Infrastructures.Org