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-users] Re: Kernel panic, unable to mount rootfs

To: "Matthew J. Harmon" <mjh@xxxxxxxx>, xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] Re: Kernel panic, unable to mount rootfs
From: Yvette Chanco <yentlsoup@xxxxxxxxx>
Date: Mon, 20 Jun 2005 19:28:02 -0500
Delivery-date: Tue, 21 Jun 2005 00:27:04 +0000
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=cMODw4vBb/zDSUPGHuo1tGepsQvt5zlk6a65kDAWEiv8EAFP4i9AUxnvZ26+C+syBokReerCUsOffzNAcWfkyWkXknyCg7hphpZx44c0hnhG5XxfM/O3FNu9jtx/vHOllJKRJzM8fWsHQUBI9YqDFrsS4VjbO0UC/vLlEx9E7KI=
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <Pine.LNX.4.62.0506201811200.32722@xxxxxxxxxxxxx>
List-help: <mailto:xen-users-request@lists.xensource.com?subject=help>
List-id: Xen user discussion <xen-users.lists.xensource.com>
List-post: <mailto:xen-users@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/cgi-bin/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <Pine.LNX.4.62.0506201748260.32722@xxxxxxxxxxxxx> <Pine.LNX.4.62.0506201811200.32722@xxxxxxxxxxxxx>
Reply-to: Yvette Chanco <yentlsoup@xxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
If you're getting that far (to starting the dom0) then grub might not
directly be the issue. I got that error message when I was using a
kernel (for dom0) that hadn't been compiled with support for my scsi
adapter. From the looks of your menu.lst, though, it seems you
probably did a custom build, so you would know what you included. My
only other guess is if there is an initrd image you haven't put in the
grub configuration?

On 6/20/05, Matthew J. Harmon <mjh@xxxxxxxx> wrote:
> Additionally, the menu.lst for grub is as follows:
> title Debian GNU/Linux, Xen 2.6.11xen0, testing 2005.06.18
> kernel=/xen.gz dom0_mem=32768 noreboot
> root (hd0,0)
> module=(hd0,0)/xen-linux-2.6.11charliexen0 root=/dev/sda2 ro console=tty0
> console=ttyS0 showopts selinux=0
> ###[snip - all default]
> -M
> On Mon, 20 Jun 2005, Matthew J. Harmon wrote:
> Alright, thank you for the "noreboot" kernel option!
> Here is the full err:
> Root-NFS: No NFS server available, giving up.
> VFS: Unable to mount root fs via NFS, trying floppy.
> VFS: Cannot open root device "sda2" or unknown-block(2,0)
> Please append a correct "root=" boot option
> Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(2,0)
> Doing a bit of research on the error message, found the following threads on
> xen-devel:
> http://lists.xensource.com/archives/html/xen-devel/2004-10/msg00382.html
> http://lists.xensource.com/archives/html/xen-devel/2004-12/msg00470.html
> I'm thinking this might not be a xen problem, but a grub problem?
> Still working on the issue, any tips would be appreciated.
> Thanks.
> -Matthew
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users

-Yvette Chanco

Xen-users mailing list

<Prev in Thread] Current Thread [Next in Thread>