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.
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.
Closing old RFEs, please reopen if still needed. Patches are always welcomed.