Bug 1159729

Summary:	[RFE] Warn/Block user trying to hotunplug if guest agent is not running
Product:	[oVirt] ovirt-engine	Reporter:	Michael Burman <mburman>
Component:	BLL.Network	Assignee:	Dan Kenigsberg <danken>
Status:	CLOSED WONTFIX	QA Contact:	Meni Yakove <myakove>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.5.0	CC:	bugs, danken, lpeer, lsurette, nyechiel, rbalakri, Rhev-m-bugs, srevivo, ykaul, ylavi
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	---	Flags:	ylavi: ovirt-future? rule-engine: planning_ack? mburman: devel_ack? rule-engine: testing_ack?
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2018-06-06 07:34:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Network	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Michael Burman 2014-11-03 08:03:02 UTC

Description of problem:
If UN-expirienset customer or new QE will run vm with nic without any OS, and then will hotunplug and remove the nic, migrate the vm, from that stage there will be no option to add any new nic's to this vm, even if the vm is not running.

Hotplug/unplug is not supported without guest OS support. It make sense to block it if guest OS is not running or at least warn the user. 

Version-Release number of selected component (if applicable):
3.5.0-0.18.beta.el6ev

How reproducible:
alaways

Steps to Reproduce:
1. run vm, with plugged nic, and make sure network is part of the boot order 
2. hot-unplug and remove the nic 
3. migrate the vm, from this point, its impossible to add nic as long network is part of the boot order

Actual results:
Impossible to add nic to the vm. user will have to create new vm.

Expected results:
User should be warned or blocked if trying to hotunplug vm that has no OS.

Comment 2 Nir Yechiel 2014-11-26 15:25:41 UTC

The only reliable way for us to detect a running guest OS in the VM is if guest agent is being used. We can limit the feature for VMs with guest agents only, or add a warning in the UI, but I really want to see similar requests from customers before doing any of the above.

I would start by properly documenting this. Interestingly enough, although this is seems to be a common thing users encounter when plugging/unplugging a NIC. our Admin Guide does not state that guest OS is required for the feature to work.

Comment 3 Yaniv Lavi 2018-06-06 07:34:25 UTC

Closing old RFEs, please reopen if still needed.
Patches are always welcomed.