+++ This bug was initially created as a clone of Bug #1109880 +++

Description of problem:
when i'm trying to run VM, it fails with this error:
VM testvm is down with error. Exit message: internal error process exited while connecting to monitor: qemu-kvm: -drive if=none,media=cdrom,id=drive-ide0-1-0,readonly=on,format=raw,serial=: Duplicate ID 'drive-ide0-1-0' for drive .

vdsm-4.14.7-3.el6ev in 3.4 compatibility mode
ovirt-engine-3.5.0-0.0.master.20140605145557.git3ddd2de.el6.noarch

Version-Release number of selected component (if applicable):

How reproducible:
always

Actual results:
VM fails to run

Expected results:
VM should run

Additional info:

--- Additional comment from  on 2014-06-16 17:36:27 IDT ---



--- Additional comment from Dan Kenigsberg on 2014-06-16 19:38:02 IDT ---

Engine specifies cdrom twice, with two different device ids.

{'index': '2', 'iface': 'ide', 'specParams': {'path': ''}, 'readonly': 'true', 'deviceId': '713938ee-bdd0-4a84-80d2-387e3b9e13f4', 'path': '', 'device': 'cdrom', 'shared': 'false', 'type': 'disk'},
{'index': '2', 'iface': 'ide', 'specParams': {'path': ''}, 'readonly': 'true', 'deviceId': 'cab66d14-1e9d-498c-82c3-0ab6545ac2c7', 'path': '', 'device': 'cdrom', 'shared': 'false', 'type': 'disk'}

--- Additional comment from  on 2014-06-17 13:39:24 IDT ---

any workaround for this?

--- Additional comment from Michal Skrivanek on 2014-06-19 12:13:03 IDT ---

(In reply to movciari from comment #0)
How reproducible:
always

always == always for this particular VM or for all VMs or…?

--- Additional comment from  on 2014-06-19 15:07:02 IDT ---

(In reply to Michal Skrivanek from comment #4)
> (In reply to movciari from comment #0)
> How reproducible:
> always
> 
> always == always for this particular VM or for all VMs or…?

for all VMs (at least on my setup)

--- Additional comment from Michal Skrivanek on 2014-06-19 15:09:07 IDT ---

even a new VM you create?
would you please include engine.log for that attempt?

--- Additional comment from  on 2014-06-19 17:17:12 IDT ---

in engine.log i already posted, i created VM called "minivm" on line 3824, and it failed to run around line 3935

--- Additional comment from Omer Frenkel on 2014-06-22 18:35:01 IDT ---

i have few questions to help me understand the root cause of the issue:
1. when creating the vm, do you select any iso?

2. is this a clean installation or upgrade?
i suspect you have something wrong with your blank template configuration
could you please attach the result of the following db query?

select type,device,is_managed,alias,spec_params from vm_device where vm_id = '00000000-0000-0000-0000-000000000000' order by device;

3. i'm interested to know if the duplicate device created on add vm or run,
can you please attach the result of this query as well? (replace <VM_NAME> with the new vm name):

select device,is_managed,alias,spec_params from vm_device where vm_id = (select vm_guid from vm_static where vm_name='<VM_NAME>') order by device;


thanks!

--- Additional comment from  on 2014-06-23 13:14:17 IDT ---

(In reply to Omer Frenkel from comment #8)
1. - i don't select any iso, i don't even have iso domain

2. clean install on a new VM

engine=# select type,device,is_managed,alias,spec_params from vm_device where vm_id = '00000000-0000-0000-0000-000000000000' order by device;
 type  | device | is_managed | alias |     spec_params      
-------+--------+------------+-------+----------------------
 video | cirrus | t          |       | { "vram" : "65536" }
(1 row)

3. 
on old vm:
engine=# select device,is_managed,alias,spec_params from vm_device where vm_id = (select vm_guid from vm_static where vm_name='minivm') order by device;
 device | is_managed | alias |     spec_params     
--------+------------+-------+---------------------
 bridge | t          |       | {
                             : }
 cdrom  | t          |       | {
                             :   "path" : ""
                             : }
 cdrom  | t          |       | {
                             :   "path" : ""
                             : }
 disk   | t          |       | 
 qxl    | t          |       | {
                             :   "vram" : "32768",
                             :   "heads" : "1"
                             : }
 qxl    | t          |       | {
                             :   "vram" : "32768",
                             :   "heads" : "1"
                             : }
(6 rows)
new vm i just created:
engine=# select device,is_managed,alias,spec_params from vm_device where vm_id = (select vm_guid from vm_static where vm_name='newvm') order by device;
 device | is_managed | alias |     spec_params     
--------+------------+-------+---------------------
 bridge | t          |       | {
                             : }
 cdrom  | t          |       | {
                             :   "path" : ""
                             : }
 cdrom  | t          |       | {
                             :   "path" : ""
                             : }
 disk   | t          |       | 
 qxl    | t          |       | {
                             :   "vram" : "32768",
                             :   "heads" : "1"
                             : }
 qxl    | t          |       | {
                             :   "vram" : "32768",
                             :   "heads" : "1"
                             : }
(6 rows)

--- Additional comment from Michal Skrivanek on 2014-06-26 15:24:12 IDT ---

seems not to be happening when *not* using instance types

--- Additional comment from Ilanit Stein on 2014-08-12 12:41:22 IDT ---

Verified on ovirt-engine 3.5-rc1

Created a VM both from template (with attached cd), and instance type (Large).
VM started successfully.

--- Additional comment from  on 2014-09-10 18:52:54 IDT ---

Hi,

This bug is also present on 3.4 and the patch needs to be backported.
This happens when using the blank template for creating a new VMs and modifying the advanced options like attaching a CDROM before booting the first time.

Thank you