Greetings,

I'm creating xen guests with file-backed VBDs and installing RHEL5
(paravirt) on them with kickstart. When the guest is first created my
xmdomain.cfg looks something like this:

name = "kauai"
memory = "1024"
disk = [ 'tap:aio:/local/mnt/xen/kauai,xvda,w' ]
vif = [ '' ]
kernel = "/local/mnt/xen/bootimages/vmlinuz"
ramdisk = "/local/mnt/xen/bootimages/initrd.img"
vcpus=1
on_reboot   = 'destroy'
extra = "ks=http://ks-dev/rhel-5-i386/GV/ks/rhel-5-xen-guest-i386.cfg noipv6 
name=kauai"

Here's my question: during the RHEL5 beta I was able to just touch the
file for the VBD (/local/mnt/xen/kauai) and during the kickstart it
would be grown as needed up to a limit of 8Gb. After reloading my xen
server with the released RHEL5 the same thing fails with
"Input/output error during read on /dev/xvda". If I do something like:

dd if=/dev/zero of=kauai bs=1k seek=8192k count=1

(which I found in the Xen users manual) then everything proceeds as
before.

Anybody else notice this? Did something change between the beta and
release? 

-Deke

_______________________________________________
rhelv5-list mailing list
[EMAIL PROTECTED]
https://www.redhat.com/mailman/listinfo/rhelv5-list

Reply via email to