4:13 a.m.
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?
(oVirt 3.3, no shared disk, thin-provisioned)
--
Nicolas Ecarnot
4:44 a.m.
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.
6:16 a.m.
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?
<domain type="kvm">
<name>serv-bd-dev1</name>
<uuid>0e3ffc7c-4e54-405c-9af1-55bc4f25fe13</uuid>
<memory>4194304</memory>
<currentMemory>4194304</currentMemory>
<vcpu>4</vcpu>
<memtune>
<min_guarantee>349184</min_guarantee>
</memtune>
<devices>
<channel type="unix">
<target name="com.redhat.rhevm.vdsm"
type="virtio"/>
<source mode="bind"
path="/var/lib/libvirt/qemu/channels/0e3ffc7c-4e54-405c-9af1-55bc4f25fe13.com.redhat.rhevm.vdsm"/>
</channel>
<channel type="unix">
<target name="org.qemu.guest_agent.0"
type="virtio"/>
<source mode="bind"
path="/var/lib/libvirt/qemu/channels/0e3ffc7c-4e54-405c-9af1-55bc4f25fe13.org.qemu.guest_agent.0"/>
</channel>
<input bus="usb" type="tablet"/>
<graphics autoport="yes" keymap="fr"
passwd="*****"
passwdValidTo="1970-01-01T00:00:01" port="-1"
type="vnc">
<listen network="vdsm-ovirtmgmt"
type="network"/>
</graphics>
<controller model="virtio-scsi" type="scsi"/>
<video>
<address bus="0x00" domain="0x0000"
function="0x0" slot="0x02" type="pci"/>
<model heads="1" type="qxl"
vram="65536"/>
</video>
<interface type="bridge">
<address bus="0x00" domain="0x0000"
function="0x0" slot="0x03" type="pci"/>
<mac address="00:1a:4a:a8:27:0c"/>
<model type="e1000"/>
<source bridge="ovirtmgmt"/>
<filterref filter="vdsm-no-mac-spoofing"/>
<link state="up"/>
</interface>
<disk device="cdrom" snapshot="no"
type="file">
<address bus="1" controller="0"
target="0"
type="drive" unit="0"/>
<source file=""
startupPolicy="optional"/>
<target bus="ide" dev="hdc"/>
<readonly/>
<serial/>
</disk>
<disk device="disk" snapshot="no"
type="block">
<address bus="0" controller="0"
target="0"
type="drive" unit="0"/>
<source
dev="/rhev/data-center/5849b030-626e-47cb-ad90-3ce782d831b3/1429ffe2-4137-416c-bb38-63fd73f4bcc1/images/c38a73f0-da9e-4e52-ad63-78e64fce957c/7a74ba80-9207-4f21-90a0-f28fc9925fee"/>
<target bus="ide" dev="hda"/>
<serial>c38a73f0-da9e-4e52-ad63-78e64fce957c</serial>
<boot order="1"/>
<driver cache="none" error_policy="stop"
io="native" name="qemu" type="qcow2"/>
</disk>
<disk device="disk" snapshot="no"
type="block">
<address bus="1" controller="0"
target="0"
type="drive" unit="1"/>
<source
dev="/rhev/data-center/5849b030-626e-47cb-ad90-3ce782d831b3/11a077c7-658b-49bb-8596-a785109c24c9/images/36553e2f-64f2-4d4e-b8a1-d9cd7d1cdf49/e610a133-1f96-4c6a-8be5-efd1fdc413b6"/>
<target bus="ide" dev="hdb"/>
<serial>36553e2f-64f2-4d4e-b8a1-d9cd7d1cdf49</serial>
<driver cache="none" error_policy="stop"
io="native" name="qemu" type="qcow2"/>
</disk>
<disk device="disk" snapshot="no"
type="block">
<address bus="0" controller="0"
target="0"
type="drive" unit="1"/>
<source
dev="/rhev/data-center/5849b030-626e-47cb-ad90-3ce782d831b3/1429ffe2-4137-416c-bb38-63fd73f4bcc1/images/f9ca88d8-e29f-4b11-9aae-b9330b5f8cdf/ed91505a-a219-42af-9915-e5ffc79918f9"/>
<target bus="ide" dev="hdd"/>
<serial>f9ca88d8-e29f-4b11-9aae-b9330b5f8cdf</serial>
<driver cache="none" error_policy="stop"
io="native" name="qemu" type="qcow2"/>
</disk>
<memballoon model="virtio"/>
</devices>
<os>
<type arch="x86_64"
machine="rhel6.4.0">hvm</type>
<smbios mode="sysinfo"/>
</os>
<sysinfo type="smbios">
<system>
<entry name="manufacturer">oVirt</entry>
<entry name="product">oVirt Node</entry>
<entry
name="version">6-4.el6.centos.10</entry>
<entry
name="serial">4C4C4544-0036-3310-805A-B1C04F585831</entry>
<entry
name="uuid">0e3ffc7c-4e54-405c-9af1-55bc4f25fe13</entry>
</system>
</sysinfo>
<clock adjustment="-2" offset="variable">
<timer name="rtc" tickpolicy="catchup"/>
</clock>
<features>
<acpi/>
</features>
<cpu match="exact">
<model>SandyBridge</model>
<topology cores="4" sockets="1"
threads="1"/>
</cpu>
</domain>
--
Nicolas Ecarnot
6:36 a.m.
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?
3:32 a.m.
Le 29/11/2013 13:36, Dan Kenigsberg a écrit :
> 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?
Wow, this is weird!
After some shutdown/reboot (I have other things to do with this VM), I
CAN NOT reproduce the issue.
I swear I have not changed the disk setup, neither added a component or
what else.
What I get now is the VM up and running with 3 IDE disks, a state I
couldn't reach so far. I don't know what to conclude?
--
Nicolas Ecarnot
4:27 a.m.
On Mon, Dec 02, 2013 at 10:32:15AM +0100, Nicolas Ecarnot wrote:
Le 29/11/2013 13:36, Dan Kenigsberg a écrit :
>>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?
>
Wow, this is weird!
After some shutdown/reboot (I have other things to do with this VM),
I CAN NOT reproduce the issue.
I swear I have not changed the disk setup, neither added a component
or what else.
What I get now is the VM up and running with 3 IDE disks, a state I
couldn't reach so far. I don't know what to conclude?
shutdown/reboot of what? Vm? Host? Engine?
Maybe you have still access to the old vdsm.logs? Otherwise the
conclusion is that someone else would bump into this bug..
I have a suspicion that Engine is somehow confused by the device
addresses reported by Vdsm. But I'd need to see the logs to stop
guessing.
4209
days inactive
4212
days old
5 comments
2 participants
participants (2)
-
Dan Kenigsberg -
Nicolas Ecarnot