Bug 656489

Summary: libvirt hotplug changes are semi-persistent, upsets virt-manager
Product: [Fedora] Fedora Reporter: J. Bruce Fields <bfields>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: berrange, clalance, crobinso, djuran, hbrock, itamar, jforbes, veillard, virt-maint
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-01-24 21:46:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description J. Bruce Fields 2010-11-23 20:57:42 UTC
If I add a new drive to a running domain using the "add new hardware" button, on restarting the domain I get an error like

error: Failed to start domain rhel6
error: internal error Process exited while reading console log output: qemu-kvm: -drive file=/var/lib/libvirt/images/rhel6-1.img,if=none,id=drive-virtio-disk1,format=raw: Duplicate ID 'drive-virtio-disk1' for drive
qemu-kvm: -device virtio-blk-pci,bus=pci.0,addr=0x8,drive=drive-virtio-disk1,id=virtio-disk1: Duplicate ID 'virtio-disk1' for device

Investigation shows that the xml file does indeed contain duplicate entries:

$ cat /etc/libvirt/qemu/rhel6.xml
...
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/rhel6-1.img'/>
      <target dev='vdb' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x07' function='0x0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/rhel6-1.img'/>
      <target dev='vdb' bus='virtio'/>
      <address type='pci' domain='0x0000' bus='0x00' slot='0x08' function='0x0'/>
...

Removing one of them manually with a text editor and then restarting libvirtd resolves the problem.

This is 100% reproduceable.

Possibly relevant software versions:

# rpm -qa|grep virt
libvirt-client-0.8.3-2.fc14.x86_64
virt-viewer-0.2.1-1.fc13.x86_64
libvirt-python-0.8.3-2.fc14.x86_64
python-virtinst-0.500.4-1.fc14.noarch
virt-manager-0.8.5-1.fc14.noarch
libvirt-0.8.3-2.fc14.x86_64
python-virtkey-0.50-8.fc14.x86_64

Comment 2 Fedora Admin XMLRPC Client 2011-09-22 18:00:04 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 3 Fedora Admin XMLRPC Client 2011-09-22 18:04:13 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 4 Fedora Admin XMLRPC Client 2011-11-30 20:00:40 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 5 Fedora Admin XMLRPC Client 2011-11-30 20:00:57 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 6 Fedora Admin XMLRPC Client 2011-11-30 20:06:01 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 7 Fedora Admin XMLRPC Client 2011-11-30 20:06:16 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 8 Cole Robinson 2012-01-24 21:46:53 UTC
F14 is EOL, please reopen if this is still relevant in a more recent fedora.