Error adding second ide disk in virt-manager

Gianluca Cecchi gianluca.cecchi at gmail.com
Wed Oct 19 15:38:15 UTC 2011


Hello,
I have F15 + virt-preview environment.
I configured a vm with "kernel 2.6 with virtio" (in virt-manager.log I
get "OS: linux:virtio26").
Then I changed config and deleted disk0 and created it as an ide disk.
Booting from CD I installed the OS without problems.
I then added a second ide disk.
Now I get an error on start after adding this second ide disk

Error starting domain: internal error Process exited while reading
console log output: qemu-kvm: -drive
file=/var/lib/libvirt/images/ovm1-2.img,if=none,id=drive-ide0-0-0,format=raw:
Duplicate ID 'drive-ide0-0-0' for drive


Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 44, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 65, in tmpcb
    callback(*args, **kwargs)
  File "/usr/share/virt-manager/virtManager/domain.py", line 1050, in startup
    self._backend.create()
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 510, in create
    if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirtError: internal error Process exited while reading console log
output: qemu-kvm: -drive
file=/var/lib/libvirt/images/ovm1-2.img,if=none,id=drive-ide0-0-0,format=raw:
Duplicate ID 'drive-ide0-0-0' for drive

the relevant part written in xml file is indeed:

    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/ovm1.img'/>
      <target dev='vda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>
    <disk type='file' device='disk'>
      <driver name='qemu' type='raw'/>
      <source file='/var/lib/libvirt/images/ovm1-2.img'/>
      <target dev='hda' bus='ide'/>
      <address type='drive' controller='0' bus='0' unit='0'/>
    </disk>

With virsh edit I change the second to
      <address type='drive' controller='0' bus='0' unit='1'/>

and I'm able to boot with the new second disk in place...
Do I have to file a bug or is this an "unsupported" way of operation
(create as 2.6+virtio and then remove virtio disk and use ide)?

Gianuca


More information about the test mailing list