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] 3.4-testing : Kernel panic on bootup (mount: couldnotfin

To: "Fajar A. Nugraha" <fajar@xxxxxxxxx>
Subject: RE: [Xen-users] 3.4-testing : Kernel panic on bootup (mount: couldnotfind filesystem /dev/root/)
From: "Madhu Venugopal (vmadhu)" <vmadhu@xxxxxxxxx>
Date: Thu, 27 Aug 2009 21:44:03 -0700
Authentication-results: sj-dkim-1; header.From=vmadhu@xxxxxxxxx; dkim=pass ( sig from cisco.com/sjdkim1004 verified; );
Cc: Xen User-List <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date: Thu, 27 Aug 2009 21:44:45 -0700
Dkim-signature: v=1; a=rsa-sha256; q=dns/txt; l=2368; t=1251434645; x=1252298645; c=relaxed/simple; s=sjdkim1004; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=vmadhu@xxxxxxxxx; z=From:=20=22Madhu=20Venugopal=20(vmadhu)=22=20<vmadhu@cisco .com> |Subject:=20RE=3A=20[Xen-users]=203.4-testing=20=3A=20Kerne l=20panic=20on=20bootup=20(mount=3A=20couldnotfind=20filesys tem=20/dev/root/) |Sender:=20; bh=TVQ9GFV7Bu/yaJzuT7Dm9cbI0DuiikH21iepNwsewoY=; b=rL2nI7HAWpObamBzSSsqSnoXiIKvjV6URuqJtaem2P7rJCUlakU0YnGEgc 7U9yWCXojqMTj8hmeWrex3LQ9cowN8unhFx5Z5+bdDizC0Kij4t3HTK6SUhV rm8FL0qWlmZVerPYv8JOhIc0wVOWqu/y2or9sE+7KbLf59FQlhVQ4=;
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <7207d96f0908270552x6aa640c7r49662c9a5dfa06be@xxxxxxxxxxxxxx>
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/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-users>, <mailto:xen-users-request@lists.xensource.com?subject=unsubscribe>
References: <66EB4A5E3F739E40BFC2567243002B830787F065@xxxxxxxxxxxxxxxxxxxxxxxxxx> <66EB4A5E3F739E40BFC2567243002B83078F3463@xxxxxxxxxxxxxxxxxxxxxxxxxx> <00f001ca264e$a3e13370$fcdf0a0a@xxxxxxxxxxxxxxx> <66EB4A5E3F739E40BFC2567243002B83078F36EA@xxxxxxxxxxxxxxxxxxxxxxxxxx> <7207d96f0908270552x6aa640c7r49662c9a5dfa06be@xxxxxxxxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: AconFS0gHOcK5+FgTjqiJMUfEq0plgAhHVGQ
Thread-topic: [Xen-users] 3.4-testing : Kernel panic on bootup (mount: couldnotfind filesystem /dev/root/)
Hi Fajar

> (vmadhu)<vmadhu@xxxxxxxxx> wrote:
> > Hi,
> >
> > I started everything from scratch...
> >
> > 1. Installed CentOS 5.3
> > 2. Installed XEN 3.4-testing as per README
> >
> > The same problem during the reboot. I copied the Grub entry from the
> > Native CentOS5.3 installation.
> On your original setup, I noticed you're using "root=LABEL=/1" on the
> original grub stanza and "root=LABEL=/" on Xen stanza. Are they
> supposed to refer to the same root? This could be one of things
> causing you problems.

That is the earliest attempt and that setup is gone. I don't want to 
debug this now... Maybe later (once the issue at hand is resolved).

> >
> > This time am seeing an error additional error :
> >
> > "Volume group : "VolGroup00" not Found"
> >
> > Searching the forums, I understand that this is a Logical Volume and
> > There are a few problems with Logical Volumes. But none of the
> > workarounds
> > Seems to work.
> >
> > I get a feeling that the "mkinitrd" is not doing its job completely.
> > (or) what am I missing ?
> My guess is the kernel config you use is missing some essential
> modules needed to boot correctly. Here's some of the things you can
> try :

Okay. How would I find what modules are missing ?
I don't see any such error in the bootup logs. Any other suggestions ?

> - Install RHEL's Xen. This should be pretty straightforward, you'd end
> up with Xen 3.1+ and a working grub.conf stanza for Xen with RHEL's
> kernel-xen
> - Install Xen package from gitco (http://www.gitco.de/repo/). You can
> get Xen 3.4.1 (currently in testing) but still using RHEL's kernel-xen
> - If that works, you can simply compile another xen kernel as you
> like, using either 2.6.18 or later pv_ops kernel. If using 2.6.18, you
> can use RHEL's kernel-xen config as a base.

I didn't want to take this approach. We have standardized on the
to take with the existing XEN installations and kernel to use. It is
that am the only one seeing this issue while it works just fine on other
Machines. This makes it clear that it is machine specific and am missing
Some drivers for them. But am clueless on what is that am missing and
To include them in initrd. Any suggestions ?



> --
> Fajar

Xen-users mailing list

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