|
|
|
|
|
|
|
|
|
|
xen-users
Fwd: [Xen-users] Using lvm for domUs
Just added the full paths to the lvms. No difference made. should i also change
root = "/dev/sda1 ro" to something like
root = "xvda ro" ?
On 30/04/07, Jason Dillon <jason@xxxxxxxxxxxx> wrote:
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 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']
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
--
John Maclean - 07739 171 531
MSc (DIC)
--
John Maclean - 07739 171 531
MSc (DIC)
_______________________________________________
Xen-users mailing list
Xen-users@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/xen-users
|
|
|
|
|