On Sep 28, 2007, at 12:48, Matthias Saou wrote:
I like installing all my RHEL5 Xen guests on unpartitionned block
devices provided by LVs on the host. That way I remove one layer of
"complexity", which does make things a little easier when growing
guest
filesystems (stop the guest, grow the LV and then the ext3 from the
host, start the guest, done).
Does anyone know of a way to force RHEL5 onto a non partitionned
block device using kickstart?
We have one VG (VG00) for the host environment and another VG (VG01)
for guests. On VG01 a LV is created for each guest with a specified
size, say, 100 GB and name it according to what the guest is going to
be named - idb2 would have a LV named xen-idb2LV. The partitioning
configuration is generated runtime in a kickstart %pre block based on
the disk size and LV partitions are used once again. I have not
noticed any issues during installation and/or operation with this
approach. I have not used cobbler/koan for provisioning either. :)
The underlying hardware is typically multiple disks in a RAID10
group. It seems to work, is convenient and was easy to transition to
when setting up the first Xen hosts.
For example:
% sudo pvdisplay /dev/sdb
--- Physical volume ---
PV Name /dev/sdb
VG Name VG01
PV Size 930.50 GB / not usable 32.00 MB
Allocatable yes
PE Size (KByte) 32768
Total PE 29775
Free PE 11727
Allocated PE 18048
PV UUID 9uWM9e-P9Xb-4nK0-SPEC-bUYE-aeli-uapcss
% sudo vgdisplay VG01
--- Volume group ---
VG Name VG01
System ID
Format lvm2
Metadata Areas 1
Metadata Sequence No 20
VG Access read/write
VG Status resizable
MAX LV 0
Cur LV 11
Open LV 11
Max PV 0
Cur PV 1
Act PV 1
VG Size 930.47 GB
PE Size 32.00 MB
Total PE 29775
Alloc PE / Size 18048 / 564.00 GB
Free PE / Size 11727 / 366.47 GB
VG UUID e7efKL-CztK-3OY2-akSn-CeFN-4LzS-MsZ6QG
% sudo lvdisplay VG01
[snip]
--- Logical volume ---
LV Name /dev/VG01/xen-idb2LV
VG Name VG01
LV UUID 8e1L28-XqQy-m4dg-bt58-IyVV-2Sb7-bdFmrx
LV Write Access read/write
LV Status available
# open 1
LV Size 100.00 GB
Current LE 3200
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:14
--- Logical volume ---
LV Name /dev/VG01/xen-crm1LV
VG Name VG01
LV UUID b7J45r-LQ16-bA2f-XIGK-2rcD-xFRS-3LcmC2
LV Write Access read/write
LV Status available
# open 1
LV Size 8.00 GB
Current LE 256
Segments 1
Allocation inherit
Read ahead sectors 0
Block device 253:15
[snip]
On a related note - is there a reason why txqueuelen for vifs is 32
by default? Setting it to 128 increases network performance for xen
guests (as measured by iperf) significantly. Also, configuring NIC
bonding and per-guest VLANs is also a pretty hairy exercise that
could be made much easier. :)
HTH
Kaj
--
Kaj J. Niemi
<[EMAIL PROTECTED]>
+358 45 63 12000
_______________________________________________
rhelv5-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/rhelv5-list
