WARNING - OLD ARCHIVES

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/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-users

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

To: <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: RE: [Xen-users] Xen3.1 x86_64: no volume groups found
From: "Schober Walter" <Walter.Schober@xxxxxxxxx>
Date: Wed, 3 Oct 2007 19:11:05 +0200
Delivery-date: Wed, 03 Oct 2007 10:11:56 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
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>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
Thread-index: Acfq59SuABMRRRfURJKN8hwPOTt8rQa+Fd4Q
Thread-topic: [Xen-users] Xen3.1 x86_64: no volume groups found
In my case I have a /dev/hda in CentOS which is then a /dev/sda after
Xen 3.1.0 boot.
I tried in VMWare to reproduce, but if it's a /dev/sda before, too, it
works great.

Any Idea to either have /dev/sda always or to teach the initrd /
xenkernel to leave /dev/hda as it is?

br
Walter 

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

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