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

[Xen-users] Using lvm for domUs

To: "Xen Users" <xen-users@xxxxxxxxxxxxxxxxxxx>
Subject: [Xen-users] Using lvm for domUs
From: "john maclean" <jayeola@xxxxxxxxx>
Date: Mon, 30 Apr 2007 19:29:31 +0100
Delivery-date: Mon, 30 Apr 2007 11:28:09 -0700
Dkim-signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=t8YY3TXtkr+Wj8pEuuy46QhRkt5Ft8eHG+Vzx6HIz5NSjTz1dclXrrK6RW+d2KGvDVAEwGod5HFB22I3NEw2djpAQx2WuQJrpZf2Ww5lfUFttFO6/X35gqWKml7q99/0GXJpcafihh7+IKESNDKABI9S3+uJvQE7BaAYfLOc6ag=
Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:mime-version:content-type:content-transfer-encoding:content-disposition; b=CIkokBA4vow4401ko9dWV/I4k1sD+Re79xzGDwHpJ7KwQG26FDSzz2SDBpukTd3ePiURpJAsnA1SLYOACTNIwLIa9OT7lI5UuClSd47fo4GOUC/AiHffRi2VwB2X4lhrSJRWQ9qqkTLlewg7WwEv1wthjhldueMMLS4kQPmS1io=
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
Hey chaps. What's the best way to populate an lvm to get it ready for 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']
dhcp="dhcp"
hostname= "etch_lvm"
root = "/dev/sda1 ro"
extra = "4"
vnc= 'yes'

xm start etch_lvm => backend device not found. Am I missing something?
Perhaps I'm not using dd correctly to fill up the lvm. wrong switches
used for cp perhaps?

tried dd /path/to/image /path/to/lvm
cp -dpR /path/to/image /path/to/lvm

xen-3.0.4-1

--
John Maclean  - 07739 171 531
MSc (DIC)

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

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