Subject: Re: Image-based Linux-DomUs fail to boot ("VFS: Cannot open root device "hda1" or unknown-block(0,0)")
To: Mark Weinem <email@example.com>
From: Manuel Bouyer <firstname.lastname@example.org>
Date: 08/05/2006 19:56:56
On Thu, Aug 03, 2006 at 05:39:32PM +0200, Mark Weinem wrote:
> Thanks to community efforts there are now many ready-to-use VM-Images
> available, to "kickstart" Linux-DomUs. Just for examples:
> But unfortunately I don't get them run with Xen3/NetBSD-3.99.21
> I tried the following three methods without luck.
> 1) Copying a Linux system over to a ext2 filesystem (created by NetBSD):
> - I started "disklabel -i" and changed "fstype" of /dev/wd0g
> from "4.2BSD" to "Linux Ext2"
> - "mke2fs /dev/wd0g"
> - "mount_ext2fs /dev/wd0g /mnt" , "cp -R /linux_files/ /mnt/"
> and my config file for the Linux domU:
> kernel = "/vmlinuz-188.8.131.52-xen"
> memory = 300
> name = "suse"
> vif = [ 'bridge=bridge0' ]
> disk = [ 'phy:/dev/wd0g,0x301,w' ]
> root = "/dev/hda1 rw"
> The corresponding error message after "xm create ..."
> VFS: Cannot open root device "hda1" or unknown-block(0,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on
Looks like something didn't get to the domU properly. I've always used this
method and it worked for me, I don't know what has gone wrong here (exept
I use 'ro' for root instead or 'rw').
> 2) Booting a file-based Linux image directly:
I didn't find ready-to-use disk image, so I guess it's a file that you
formatted as ext2 and populated by yourself ?
Manuel Bouyer <email@example.com>
NetBSD: 26 ans d'experience feront toujours la difference