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] How to create a domU on RedHat Enterprise AS 4.4?

To: xen-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Xen-users] How to create a domU on RedHat Enterprise AS 4.4?
From: "Tom Z. Napierala" <tom@xxxxxx>
Date: Sun, 10 Sep 2006 16:34:32 +0100
Delivery-date: Sun, 10 Sep 2006 08:35:17 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxx
In-reply-to: <BAY108-DAV996CFEF6667BC05E84D6693340@xxxxxxx>
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>
Organization: DB Alliance Ltd.
References: <BAY108-DAV141AC7FD006ADE7C2079393440@xxxxxxx> <9c92ada10609071220v440f7323m8ac3df69e3865cc2@xxxxxxxxxxxxxx> <BAY108-DAV996CFEF6667BC05E84D6693340@xxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: KMail/1.9.1
Dnia Saturday 09 September 2006 04:14, Liang Yang napisał:
> Hi,
> I installed Xen 3.0.2 on RedHat Enterprise AS 4.4. Now I try to create domU
> from dom0. I copied the whole filesystem of a RedHat to the logic volume
> group (/dev/VG_Dom6_Linux/LogVol00) I created for domU.  I then start the
> domU kernel, however I got the following errors:


> Checking root filesystem
> [/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a /dev/VG_Dom6_Linux/LogVol00
> fsck.ext3: /dev/VG_Dom6_Linux/LogVol00:
> The superblock could not be read or does not describe a correct ext2
> filesystem.  If the device is valid and it really contains an ext2
> filesystem (and not swap or ufs or something else), then the superblock
> is corrupt, and you might try running e2fsck with an alternate superblock:
>     e2fsck -b 8193 <device>
> No such file or directory while trying to open /dev/VG_Dom6_Linux/LogVol00


Your DomU is trying to access logocal volume as root instrad of sda1.

> Here is the content of my domU config file:
> kernel = "/boot/vmlinuz-2.6-xenU"
> ramdisk = "/boot/initrd-2.6-xen.img"
> memory = 512
> name = "domain1"
> extra = "3"
> vif = [ 'bridge=xenbr0' ]
> dhcp = "dhcp"
> disk = ['phy:/dev/VG_Dom6_Linux/LogVol00,sda1,w' ]
> root = "/dev/sda1 ro"
Check your DomU fstab.

Tom Napierala
DB Alliance Limited
North Point House, New Mallow Road, Cork, Ireland
The National Software Centre, Mahon, Cork, Ireland

Xen-users mailing list