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] Troubles converting a pv host from dom0-hosted kernel to

To: Guillaume Rousse <Guillaume.Rousse@xxxxxxxx>
Subject: Re: [Xen-users] Troubles converting a pv host from dom0-hosted kernel to self-contained kernel
From: Fabian Zimmermann <xen-users@xxxxxxxxxxxxxxxxx>
Date: Tue, 21 Jul 2009 17:28:58 +0200
Cc: xen-users@xxxxxxxxxxxxxxxxxxx
Delivery-date: Tue, 21 Jul 2009 08:29:46 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <4A65DBFD.9090304@xxxxxxxx>
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: <4A65DBFD.9090304@xxxxxxxx>
Sender: xen-users-bounces@xxxxxxxxxxxxxxxxxxx
User-agent: Mozilla-Thunderbird (X11/20090103)
Hi Guillaume Rousse,

First issue: I found than it was mandatory to use root=/dev/xvda1 in order to mount root device when booting, despite the partition being exported as sda1 according to domU configuration. Is this normal ?

As far as I know, this depends on your DomU-Kernel. Did you try the xen.org-

Second issue, the boot stop at root partition mount time, trying to force fsck:
[/sbin/fsck.ext3 (1) -- /] fsck.ext3 -a -a /dev/sda1
fsck.ext3: No such file or directory while trying to open /dev/sda1
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>

This happens whatever device I use for root partition in domU /etc/fstab (/dev/sda1 or /dev/xdva1). However, I can perfectly mount /dev/vg0/sexonthebeach as an ext3 partition in domU. Morevoer, the emergency shell has expected content monted under / in both case...

Try to boot your initramfs with init=/bin/bash and play around to find the right device-name (if any) f.e.:

mkdir /tmp/testme/
mount /dev/sda1 /tmp/testme/
mount /dev/xvda1 /tmp/testme/

Last question, loosely related to this problem: is there a way to easily convert a partition-based host to a disk-based host (phy:/dev/vg0/foo,sda1 -> phy:/dev/vg0/foo,sda) ?

Maybe you find this useful: http://wiki.z-technologies.de/doku.php?id=partitiontabelle_nachtraeglich_erstellen


Xen-users mailing list