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: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Subject: Re: [Xen-devel] Cannot open root device for dom0
From: Steven Hand <Steven.Hand@xxxxxxxxxxxx>
Date: Sat, 17 Jan 2004 11:32:30 +0000
Cc: stevegt@xxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxxxx, Steven.Hand@xxxxxxxxxxxx
Delivery-date: Sat, 17 Jan 2004 11:32:32 +0000
Envelope-to: Steven.Hand@xxxxxxxxxxxx
In-reply-to: Message from Ian Pratt <Ian.Pratt@xxxxxxxxxxxx> of "Sat, 17 Jan 2004 09:23:11 GMT." <E1Ahmfg-0004Bp-00@xxxxxxxxxxxxxxxxxxxx>
>> 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. 

Anyway, that's just for info -- I believe it's fixed now, right?