|
|
|
|
|
|
|
|
|
|
xen-users
Re: [Xen-users] Using lvm for domUs
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']
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
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
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|