Bug 702246

Summary: For kvm hypervisor the default disk driver should be 'qemu'
Product: Red Hat Enterprise Linux 5 Reporter: weizhang <weizhan>
Component: libvirtAssignee: Jiri Denemark <jdenemar>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: high Docs Contact:
Priority: high    
Version: 5.7CC: dallan, dyuan, gren, hjiang, llim, mzhan, yoyzhang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-15 19:45:14 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description weizhang 2011-05-05 06:46:21 UTC
Description of problem:
When hot plug a disk to guest on kvm hypervisor, the default disk driver is 'phy', which is only supported on xen, but not 'qemu'

Version-Release number of selected component (if applicable):
kvm-83-231.el5
kernel-2.6.18-256.el5
libvirt-0.8.2-18.el5
kvm-qemu-img-83-231.el5

How reproducible:
100%

Steps to Reproduce:
1. prepare a kvm running guest and foo.img 
2. run # virsh attach-disk guest /var/lib/libvirt/images/foo.img vdb
3. virsh dumpxml guest
..
    <disk type='block' device='disk'>
      <driver name='phy' type='raw'/>
      <source dev='/var/lib/libvirt/images/foo.img'/>
      <target dev='vdb' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x2b79'/>
    </disk>
..
  
Actual results:
the default disk driver for kvm hypervisor is 'phy', which is only supported on xen

Expected results:
the default disk driver for kvm hypervisor should be 'qemu'

Additional info:

Comment 1 Huming Jiang 2011-05-26 09:16:04 UTC
Could not reproduce this bug on the following components:
kernel-2.6.18-238.el5
virt-manager-0.6.1-13.el5
libvirt-0.8.2-15.el5

Comment 3 Jiri Denemark 2011-05-26 10:13:02 UTC
It does reproduce on libvirt-0.8.2-15.el5; removing regression keyword.

These are the steps I did:

# rpm -q libvirt
libvirt-0.8.2-15.el5

# service libvirtd restart

# virsh attach-disk console /var/lib/libvirt/images/dummy/dummy001.img vda
Disk attached successfully

# virsh dumpxml console
...
    <disk type='block' device='disk'>
      <driver name='phy' type='raw'/>
      <source dev='/var/lib/libvirt/images/dummy/dummy001.img'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x06' function='0x37'/>
    </disk>
...

Comment 4 Huming Jiang 2011-05-31 02:17:42 UTC
There is a error in my last test about this bug in rh5.6.
It reproduces on libvirt-0.8.2-15.el5.

Steps:
# rpm -q libvirt
libvirt-0.8.2-15.el5

# service libvirtd restart
# virsh attach-disk rh5.6 /var/lib/libvirt/images/foo.img vda
# virsh dumpxml rh5.6
...
    <disk type='block' device='disk'>
      <driver name='phy' type='raw'/>
      <source dev='/var/lib/libvirt/images/foo.img'/>
      <target dev='vda' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x05' function='0x3b'/>
    </disk>
...

Comment 5 RHEL Program Management 2011-06-20 22:45:56 UTC
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.

Comment 7 RHEL Program Management 2011-08-15 19:45:14 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.