Red Hat Bugzilla – Bug 166674
xm vbd-refresh has no effect in xenU env when partition was lvm-extended in dom0
Last modified: 2008-02-26 17:55:07 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050720 Fedora/1.0.6-1.1.fc4 Firefox/1.0.6
Description of problem:
When xen is used together with LVM (in dom0) and its partition is resized (in dom0) and xm vbd-refresh is called, then the unprivileged domain should recognize the change without the need of beeing restartet. But i don't get this working.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. install fc4, update or not (does not matter)
2. set up test xen env like that: lvcreate -L2g -n xentest vg0; mount /dev/vg0/xentest /mnt/tmp; cp -xa / /mnt/tmp; cp -a /dev/* /mnt/tmp/dev
3. small modifications like in: /mnt/tmp/etc/fstab
4. create simple xen config file
5. start domain with xm
6. in domain launch: sfdisk -s /dev/hda1
7. in dom0: lvextend -L+200m /dev/vg0/xentest; xm vbd-refresh <x> <y>
8. in domain launch: sfdisk -s /dev/hda1
Actual Results: both results of sfdisk were the same.
ext2online tells me that the device has same size
after domain was restarted the new size is found by sfdisk and ext2online works
Expected Results: IMHO the new size of the partition should be seen by domain as soon as vbd-refresh is called (in step 6)
I don't know if this is a bug in fedora or just not yet implemented .. but at least i found one webpage with makes me belief this should work:
Created attachment 118072 [details]
my xen config on one test host
I can confirm the bug, we have exact the same behaviour with our xen
domU doesn't recognize the on-the-fly resize of the partition, although the
command "xm vbd-refresh domainname vbdid" was executed
I only found one additional reference of this command:
This report targets the FC3 or FC4 products, which have now been EOL'd.
Could you please check that it still applies to a current Fedora release, and
either update the target product or close it ?
This report targets FC4, which is now end-of-life.
Please re-test against Fedora 7 or later, and if the issue persists, open a new bug.