[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [Xen-users] Xen3.1 x86_64: no volume groups found


  • To: xen-users@xxxxxxxxxxxxxxxxxxx
  • From: David Koscinski <dmkoscinski@xxxxxxxxx>
  • Date: Wed, 31 Oct 2007 16:46:31 -0500
  • Delivery-date: Wed, 31 Oct 2007 14:47:56 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:subject:content-type; b=s0SnlXhFbq6Aa4YBFWflMeveVs/mMvdn2Ec1deUyYz4D/agwIctkGgqXxdvYaiCMrD0AMm0HlQxAO7txJ9dgbg2O0uWA2X+g6WlCNV4PHFDJme4Rfr7I8XOZDfBRavUQRE30mK/YenoTU6rPGxsWenivEswXjGa0WE8so++v71o=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

I too am getting a "no volume groups found" error at boot time, but I am my reasons appear to be different.

My

I did a clean install of CentOS 5 i386 on a test PC, then did a binary install of Xen 3.1 from the tarballs per this howto: http://bderzhavets.blogspot.com/2007/08/xen-3_10.html

I can boot fine from the original CentOS 5 kernel, but when I boot to the Xen kernel, it fails with the following error:

Reading all physical volumes.  This may take a while...
    No volume groups found
    Volume group "VolGroup00" not found

eventually the boot fails with a kernel panic.

This is a one drive system.  Here's the /etc/fstab

/dev/VolGroup00/LogVol00 /                       ext3    defaults        1 1
LABEL=/boot             /boot                   ext3    defaults        1 2
devpts                  /dev/pts                devpts  gid=5,mode=620  0 0
tmpfs                   /dev/shm                tmpfs   defaults        0 0
proc                    /proc                   proc    defaults        0 0
sysfs                   /sys                    sysfs   defaults        0 0
/dev/VolGroup00/LogVol01 swap                    swap    defaults        0 0


and here's the /boot/grub/menu.lst
default=0
timeout=5
splashimage=(hd0,0)/grub/splash.xpm.gz
hiddenmenu
title Xen 3.1 (2.6.18-xen)
        root (hd0,0)
        kernel /xen-3.1.gz dom0_mem=752M lowmem_emergency_pool=16M crashkernel=64M@32M
        module /vmlinuz-2.6.18-xen ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        module /initrd-2.6.18-xen.img
title CentOS (2.6.18-8.1.15.el5)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-8.1.15.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.18-8.1.15.el5.img
title CentOS (2.6.18-8.el5)
        root (hd0,0)
        kernel /vmlinuz-2.6.18-8.el5 ro root=/dev/VolGroup00/LogVol00 rhgb quiet
        initrd /initrd-2.6.18-8.el5.img

Since it says that it is looking for volume groups, I take that to mean that the kernel is LVM-enabled.  Just the same, I did look at the modules.dep in /lib/modules/2.6.18-xen and compare them to modules.dep in /lib/modules/2.6.18-8.1.15.el5 to see if there was a lvm module that is not getting loaded.  I couldn't find a reference to lvm anywhere.  But LVM is part of the kernel now, right?

I'm pretty new to LVM, Xen and to the idea of having multiple kernels that you can boot to.

Any thoughts on what I should check next?

> -----Original Message-----
> From: xen-users-bounces@xxxxxxxxxxxxxxxxxxx 
> [mailto:xen-users-bounces@xxxxxxxxxxxxxxxxxxx] On Behalf Of 
> Alien999999999
> Sent: Wednesday, August 22, 2007 6:52 PM
> To: xen-users@xxxxxxxxxxxxxxxxxxx
> Subject: [Xen-users] Xen3.1 x86_64: no volume groups found
> 
> I was using xen3.0 on rhel5, but had issues with installing 2k3, so i
> tried upgrading to 3.1 .
> 
> found only the tarball on xensource, used the spec file and 
> modified it
> for x86_64 .
> 
> 
> after booting the initrd said: no volume groups found (they 
> clearly should
> be there).
> 
> This is the menu.lst part:
> 
> title Red Hat Enterprise Linux Xen Server (2.6.18-3.1.0)
>         root (hd0,0)
>         kernel /xen-3.1.0.gz dom0_mem=393216
>         module /vmlinuz-2.6.18-xen_3.1.0 ro 
> root=/dev/VolGroup00/LogVol00
> rhgb quiet
>         module /initrd-2.6.18-xen_3.1.0.img
> 
> 
> this was the old one:
> 
> title Red Hat Enterprise Linux Server (2.6.18-8.1.8.el5xen)
>         root (hd0,0)
>         kernel /xen.gz-2.6.18-8.1.8.el5 dom0_mem=393216
>         module /vmlinuz-2.6.18-8.1.8.el5xen ro
> root=/dev/VolGroup00/LogVol00 rhgb quiet
>         module /initrd-2.6.18-8.1.8.el5xen.img
> 
> 
> 
> any idea what it is? clearly the initrd isn't the problem or 
> the kernel...
> 
> the only thing i can think of, is that xen-3.1.0.gz would 
> have virtualised
> the device into /dev/hdc or something ...
> 
> 
> 
> 
> 
> _______________________________________________
> Xen-users mailing list
> Xen-users@xxxxxxxxxxxxxxxxxxx
> http://lists.xensource.com/xen-users
> 

_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users

 


Rackspace

Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.