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: stevegt@xxxxxxxxxxxxx
Subject: Re: [Xen-devel] Cannot open root device for dom0
From: Ian Pratt <Ian.Pratt@xxxxxxxxxxxx>
Date: Sat, 17 Jan 2004 09:23:11 +0000
Cc: xen-devel@xxxxxxxxxxxxxxxxxxxxx, Ian.Pratt@xxxxxxxxxxxx
Delivery-date: Sat, 17 Jan 2004 09:24:44 +0000
Envelope-to: steven.hand@xxxxxxxxxxxx
In-reply-to: Your message of "Fri, 16 Jan 2004 17:06:59 PST." <20040117010659.GA2801@pathfinder>
List-archive: <http://sourceforge.net/mailarchive/forum.php?forum=xen-devel>
List-help: <mailto:xen-devel-request@lists.sourceforge.net?subject=help>
List-id: List for Xen developers <xen-devel.lists.sourceforge.net>
List-post: <mailto:xen-devel@lists.sourceforge.net>
List-subscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=subscribe>
List-unsubscribe: <https://lists.sourceforge.net/lists/listinfo/xen-devel>, <mailto:xen-devel-request@lists.sourceforge.net?subject=unsubscribe>
Sender: xen-devel-admin@xxxxxxxxxxxxxxxxxxxxx
> Getting "Cannot open root device" on a pretty vanilla setup.  Xen seems
> to see the device but xenolinux does not.  I'm stumped.

Hmm very odd. The messages coming out of Xen look fine, but you
should be getting 'partition check' messages something like these
earlier in the DOM0 boot:

DOM0: Starting Xeno Balloon driver
DOM0: Detected PS/2 Mouse Port.
DOM0: pty: 256 Unix98 ptys configured

DOM0: Partition check:
DOM0:  hda: hda1 hda3 hda4 < hda5 hda6 hda7 hda8 hda9 hda10 hda11 hda12 hda13 
hda14 hda15 hda16 >
DOM0:  hdc: hdc1 hdc3 hdc4 < hdc5 hdc6 hdc7 hdc8 hdc9 hdc10 hdc11 hdc12 hdc13 
hdc14 hdc15 hdc16 hdc17 hdc18 hdc19 hdc20 hdc21 hdc22 >
DOM0: Skipping partition check on cdrom /dev/hdd

DOM0: RAMDISK driver initialized: 16 RAM disks of 4096K size 1024 blocksize
DOM0: loop: loaded (max 8 devices)
DOM0: NET4: Linux TCP/IP 1.0 for NET4.0

> 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.

I'm grasping at straws here, but please can you try the pre-built
binaries in the install/boot directory in the following tar ball:



The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
Xen-devel mailing list