Bug 1006384

Summary:	Hot-unplugging a device does not remove it from the "devices boot order" list
Product:	Red Hat Enterprise Linux 7	Reporter:	Marcel Apfelbaum <marcel>
Component:	qemu-kvm	Assignee:	Marcel Apfelbaum <marcel>
Status:	CLOSED DUPLICATE	QA Contact:	Virtualization Bugs <virt-bugs>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	7.0	CC:	acathrow, juzhang, qiguo, rhod, sluo, virt-maint
Target Milestone:	rc
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-13 13:17:07 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Marcel Apfelbaum 2013-09-10 14:21:01 UTC

Description of problem:
Hot-Unplugging of a device with bootindex > 0 does not remove it from
the fw_boot_order. The outcome is that when trying to hot-plug another
device with the same boot index, it will fail. 

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

How reproducible:
100%

Steps to Reproduce:
1. device_add e1000,id=my_net_dev,bootindex=3
2. device_del my_ned_dev
3. device_add e1000,id=other_device,bootindex=3

Actual results:
qemu quits with the message:
Two devices with same boot index 3

Expected results:
Hot-Plugging should finish successfully.

Additional info:

Comment 2 Marcel Apfelbaum 2013-09-16 10:22:55 UTC

The boot order is passed in fw cfg and updated only once at
"machine done". There is no update of this list after this point.
Modifying the boot order from monitor does not work at all.
 
 So in order to solve this issue we can:
 1. Don't allow use of bootindex at hot-plug
 2. Change the architecture so boot order changing during hot-plug will be possible

Currently discussed upstream

Comment 5 Ronen Hod 2014-07-13 13:17:07 UTC


*** This bug has been marked as a duplicate of bug 1086603 ***