Re: [Xen-users] Using lvm for domUs

To:	john maclean <jayeola@xxxxxxxxx>
Subject:	Re: [Xen-users] Using lvm for domUs
From:	Jason Dillon <jason@xxxxxxxxxxxx>
Date:	Mon, 30 Apr 2007 13:58:02 -0700
Cc:	Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
Delivery-date:	Mon, 30 Apr 2007 13:56:38 -0700
Dkim-signature:	a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=ANcTfwPWA6IVmyh7NbCYAIQR9lfOHtwFSwpXBznuvejBA2xgH7ZWjRWQA4gTTDVicWfgNEPpqgRbb/sFzxI5emK8CkbFmzoXDACjBqKcLZVwN9e6/yEnxFGYcylebTSeGaRqhXHrfpy85PYqQxjjuBPslfVSYH0KRift8uOEdKM=
Domainkey-signature:	a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:in-reply-to:references:mime-version:content-type:message-id:cc:content-transfer-encoding:from:subject:date:to:x-mailer:sender; b=lbN1QWAyGnxpCQqZSQm98lxtsWxybx3Hko6rFcP6Un/jEQS+F0kq71vF+L4q3ahuCrDhLvQTVXVbrdgi+Fi0kTchStwpHVnfefh1bUhUa7gy1czuoRrGirGw6BcgsZbFk5m8OGav2zOc5Lglb17ORzdM6z0OjkGj8pUBSdsnVoE=
Envelope-to:	www-data@xxxxxxxxxxxxxxxxxx
In-reply-to:	<4170c1720704301129k4cc8eac3m32395ce16c7c20ec@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/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>
References:	<4170c1720704301129k4cc8eac3m32395ce16c7c20ec@xxxxxxxxxxxxxx>
Sender:	xen-users-bounces@xxxxxxxxxxxxxxxxxxx

On Apr 30, 2007, at 11:29 AM, john maclean wrote:

Hey chaps. What's the best way to populate an lvm to get it readyfor xen?


Steps I've taken so far;
* create file based images using another machine.
* create physical group and volume
* create logical volume

All checks out so far...
acid:~# lvscan
 ACTIVE            '/dev/xenLabs/etch_lvm' [4.00 GB] inherit
 ACTIVE            '/dev/xenLabs/etch_swap' [128.00 MB] inherit
 ACTIVE            '/dev/xenLabs/blag_lvm0' [2.00 GB] inherit
 ACTIVE            '/dev/xenLabs/blag_swap0' [128.00 MB] inherit

So far so good.
* mount /dev/xenLabs/etch_lvm /mnt/testing
* mkfs.ext3 /dev/xenLabs/etch_lvm
* mkswap /dev/xenLabs/etch_swap
* debootstrap /dev/xenLabs/etch_lvm

OK, still with me? Config file;
cat /etc/xen/etch_lvm
#  -*- mode: python; -*-
kernel = "/boot/vmlinuz-2.6.16-xen"
memory = 128
name = "etch_lvm"
vif = [ '' ]

disk = [ 'phy:xenLabs/etch_lvm,sda1,w', 'phy:xenLabs/etch_swap,sda2,w']


You might have better luck using the full path to the /dev files here...

disk = [ 'phy:/dev/xenLabs/etch_lmv,xvda1,w', 'phy:/dev/xenLabs/etch_swap,xvda2,w' ]


I switched sdaN to xvdaN, though it shouldn't matter which you use.

I am using LVM on dom0 to manage domU's disks with no problems.

--jason


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