On Fri, Nov 29, 2013 at 01:16:17PM +0100, Nicolas Ecarnot wrote:
Le 29/11/2013 11:44, Dan Kenigsberg a écrit :
On Fri, Nov 29, 2013 at 11:13:03AM +0100, Nicolas Ecarnot wrote:
Hi,
Strarting from a VM with two IDE disks, I'm trying to add a third IDE disk.
I get this Duplicate ID error :
VM serv-bd-dev1 is down. Exit message: internal error process exited while connecting to monitor: qemu-kvm: -drive file=/rhev/data-center/5849b030-626e-47cb-ad90-3ce782d831b3/1429ffe2-4137-416c-bb38-63fd73f4bcc1/images/f9ca88d8-e29f-4b11-9aae-b9330b5f8cdf/ed91505a-a219-42af-9915-e5ffc79918f9,if=none,id=drive-ide0-1-1,format=qcow2,serial=f9ca88d8-e29f-4b11-9aae-b9330b5f8cdf,cache=none,werror=stop,rerror=stop,aio=native: Duplicate ID 'drive-ide0-1-1' for drive .
When disabling the second one and starting only with disk 0 et the new one (so start with 2 disks), it is booting well.
Is it by design?
No. It sounds like a collision between the address of your third ide disk and the ide cdrom. Would you post vdsm.log from vmCreate command until the reported error message? It would let us understand if the bug is in Vdsm or Engine.
Dan.
Do you mean the xml that one can see in the vdsm.log?
Actually, I've meant everything: from Engine's parameters to the vmCreate command, down to the error from libvirt. The domxml blow suggests that the error might be even further below, since I do not see an address collision here.
<disk device="cdrom" snapshot="no" type="file"> <address bus="1" controller="0" target="0" type="drive" unit="0"/> <target bus="ide" dev="hdc"/> </disk> <disk device="disk" snapshot="no" type="block"> <address bus="0" controller="0" target="0" type="drive" unit="0"/> <target bus="ide" dev="hda"/> </disk> <disk device="disk" snapshot="no" type="block"> <address bus="1" controller="0" target="0" type="drive" unit="1"/> <target bus="ide" dev="hdb"/> </disk> <disk device="disk" snapshot="no" type="block"> <address bus="0" controller="0" target="0" type="drive" unit="1"/> <target bus="ide" dev="hdd"/> </disk>
Could you provide the vmCreate line from vdsm.log, and also the part of libvirtd.log since that domxml gets in until the error is spewed out?