[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-users] Using lvm for domUs

  • To: john maclean <jayeola@xxxxxxxxx>
  • From: Nico Kadel-Garcia <nkadel@xxxxxxxxx>
  • Date: Mon, 30 Apr 2007 20:10:35 +0100
  • Cc: Xen Users <xen-users@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Mon, 30 Apr 2007 12:09:15 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:user-agent:mime-version:to:cc:subject:references:in-reply-to:content-type:content-transfer-encoding; b=RwquI15F4bVy42xPYsvW6YtZ2h5q3RI1DDzItz+pJl5wHsyOa/BwXfYXu09cFI5ZbqjTx5bjdUj+MzyPd2i1vNuISWJrinvl069UqM8CGQm4bv8XiAxUPBsWkDfy1kn9SQ7Fy5JY0dTyTWu7lrKvn40tuK6tdfTU/7YxGfnjp4M=
  • List-id: Xen user discussion <xen-users.lists.xensource.com>

john maclean wrote:
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']
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


First: unless you have really compelling need, do *NOT* use lvm inside of Xen guests. Seriously, you're just adding another layer of management and configuration problems you don't need. Keep your LVM work in Dom0.

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.