RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:
guest can have the same target device with different bus

Version-Release number of selected component (if applicable):
libvirt-0.10.2-55.el6.x86_64

How reproducible:
100%

Steps to Reproduce:
1.prepare a guest with the following xml
<disk type='file' device='disk'>
      <driver name='qemu' type='qcow2' cache='none'/>
      <source file='/var/lib/libvirt/images/rhel6.img'/>
      <target dev='vda' bus='virtio'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw' cache='none'/>
      <source file='/var/lib/libvirt/images/test.img'/>
      <target dev='vda' bus='scsi'/>
    </disk>
2.start the guest
[root@lmen ~]# virsh start rhel6
Domain rhel6 started
3.look at the domblklist
[root@lmen ~]# virsh domblklist rhel6
Target     Source
------------------------------------------------
vda        /var/lib/libvirt/images/rhel6.img
vda        /var/lib/libvirt/images/test.img



Actual results:
there are 2 disks whose target is vda. User can't operate the second vda disk,such as using command 'virsh domblkinfo' 'virsh domblkstat' 'virsh detach'.


Expected results:


Additional info:

This has been fixed upstream by:
commit e0e290552bbbbd449399c9144b6b5b442b973de7
Author:     John Ferlan <jferlan>
CommitDate: 2015-03-02 22:38:36 -0500

    disk: Disallow duplicated target 'dev' values

git describe: v1.2.13-27-ge0e2905 contains: v1.2.14-rc1~301

The fix is already in RHEL 7.2 (see bug 1142631).
Since it only involves adding an error message for the incorrect configuration, I do not think it is worth backporting to RHEL 6 this late in the cycle.