Bug 789075

Summary:	adding a second cdrom to machine change boot order
Product:	[Community] Virtualization Tools	Reporter:	dhiaeddine <dhiaeddine>
Component:	virt-manager	Assignee:	Cole Robinson <crobinso>
Status:	CLOSED INSUFFICIENT_DATA	QA Contact:
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	unspecified	CC:	berrange, crobinso, xen-maint
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2012-04-02 20:39:51 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:

Description dhiaeddine 2012-02-09 17:30:55 UTC

Description of problem:

when adding a second cdrom drive to a virtual machine (example:with virtio drivers) the boot order is altered and first install cdrom iso is ignored stating no boot device is found

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

How reproducible:
add a second cdrom to vm and boot

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
workaround : 
1- add the "drivers" cdrom iso first 
2- add the "installer" cdrom iso
3- boot

if it doesn't work do:
1bis- boot then shutdown

NB: only one cdrom shows in Boot Options-->Boot device order

Comment 1 Cole Robinson 2012-03-01 23:43:24 UTC

We probably need to support individual device boot order to make this work.

Can you provide the XML or a working guest, and a non working guest? sudo virsh dumpxml <vm-name>   gives the XML

Comment 2 Cole Robinson 2012-04-02 20:39:51 UTC

No response for a month, closing. If you are still hitting this issue, please reopen with the info requested in comment #1