Red Hat Bugzilla – Bug 609422
VM can't be started after being attached disk with virsh
Last modified: 2011-01-13 18:13:36 EST
I can't find how does the diver name 'qemu' impact the process of building command line for qemu. So is it possible to remove the checking for driver name?
Otherwise, we should make 'qemu' become a valid driver name for virsh.
This is fixed upstream by 12a41822e14b558f7ffb4812978b957f3d228f23
A follow-up upstream patch dfec22cc6035a95ff1c7609ea060029cb99182cc is needed to deal with the issue more completely
Fix built into libvirt-0.8.2-4.el5
*** Bug 638071 has been marked as a duplicate of this bug. ***
Verify this bug with libvirt-0.8.2-7.el5 on RHEL5u6 Server x86_64 kvm, and PASSED.
Now libvirt allow user to specify driver name.
1. Start a guest.
2. Add a disk using virsh command:
# virsh attach-disk rhel5u5 /dev/VolGroup00/lvolhome vda --sourcetype block --driver qemu --subdriver raw
Disk attached successfully
3. Check the new disk xml
<disk type='block' device='disk'>
<driver name='qemu' type='raw'/>
<target dev='vda' bus='virtio'/>
<address type='pci' domain='0x0000' bus='0x00' slot='0x04' function='0x0'/>
The new disk works fine in guest.
4. Shut down the guest, and start it successfully.
# virsh start rhel5u5
Domain rhel5u5 started
Verified with passed on below environments according to comment 11:
An advisory has been issued which should help the problem
described in this bug report. This report is therefore being
closed with a resolution of ERRATA. For more information
on therefore solution and/or where to find the updated files,
please follow the link below. You may reopen this bug report
if the solution does not work for you.