Bug 1028387

Summary:	virtio-serial and balloon should be managed devices
Product:	Red Hat Enterprise Virtualization Manager	Reporter:	Michal Skrivanek <michal.skrivanek>
Component:	ovirt-engine-webadmin-portal	Assignee:	Arik <ahadas>
Status:	CLOSED ERRATA	QA Contact:	Lukas Svaty <lsvaty>
Severity:	unspecified	Docs Contact:
Priority:	high
Version:	3.3.0	CC:	ahadas, asegundo, ecohen, iheim, juwu, mkalinin, rbalakri, Rhev-m-bugs, tdosek, yeylon
Target Milestone:	---
Target Release:	3.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:	virt
Fixed In Version:	vt2.2	Doc Type:	Bug Fix
Doc Text:	Previously, virtio-serial and balloon devices were treated as unmanaged devices on Windows virtual machines. As a result, the addresses of the virtio-serial and balloon devices changed every time a virtual machine was started and users were asked to install drivers again. With this update, virtio-serial and balloon devices are now managed devices. Users are no longer asked to install drivers for the virtio-serial and balloon devices every time a Windows virtual machine is started.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-02-11 17:55:55 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:
Bug Depends On:
Bug Blocks:	1133612, 1142923, 1156165

Description Michal Skrivanek 2013-11-08 10:46:02 UTC

those devices should be managed in order to keep their PCI addresses fixed between VM runs. Otherwise that can trigger driver updates (and eventualy windows reboot) or other issues with the installed sw

ATM the problem shows up only when a new device is added or removed

Comment 1 Arik 2014-07-07 13:05:01 UTC

this bug was discovered while checking https://bugzilla.redhat.com/1024833, see comment #7 there for more details.

Comment 3 Lukas Svaty 2014-09-16 10:19:55 UTC

verified in vt3

Comment 4 Michal Skrivanek 2014-10-10 17:18:53 UTC

*** Bug 1146180 has been marked as a duplicate of this bug. ***

Comment 7 Julie 2015-02-03 06:07:52 UTC

Hi Arik, 
   Can you check again if the doc text is correct?

Many thanks,
Julie

Comment 8 Arik 2015-02-03 07:48:58 UTC

(In reply to Julie from comment #7)
> Hi Arik, 
>    Can you check again if the doc text is correct?
> 
> Many thanks,
> Julie

correct

Comment 10 errata-xmlrpc 2015-02-11 17:55:55 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHSA-2015-0158.html