Created attachment 1120332 [details]
vdsm logs

Description of problem:
Engine should block run of VM with devices that are PFs with enabled VFs.

We shouldn't allow the run of VM with directly attached PFs as devices(via Host devices sub tab) if they have enabled VFs in order to prevent some undesired scenarios/behaviors.

1) A case in which 1 or more of the VFs of the PF are in use.
In such case we can found our self trying to shut down the VM that using one of the VFs and we fail, because the node device(the VF) can't be found no more. 

"VDSM puma22.scl.lab.tlv.redhat.com command failed: Node device not found: no node device with matching name 'pci_0000_05_10_4'"
"Failed to power off VM sr-vm1 (Host: puma22.scl.lab.tlv.redhat.com, User: admin@internal)."

2) A case in which running a VM with a PF as directly attached device and one of his VFs as a 'pci-passthorugh' vNIC. Such scenario will cause to an endless loop of Node device not found(the VF of the PF disappeared and can't be found).

"VDSM puma22.scl.lab.tlv.redhat.com command failed: Node device not found: no node device with matching name 'pci_0000_05_10_4'"

This will trigger device not found errors in the logs every few seconds, until the next reboot of the server(shutting down the VM won't help)

3) There is no real use case that admin/user would enable VFs on a PF and then will run a VM with the PF as a directly attached device. 

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


Additional info:
jsonrpc.Executor/5::ERROR::2016-02-02 08:27:33,238::__init__::526::jsonrpc.JsonRpcServer::(_serveRequest) Internal server error
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/yajsonrpc/__init__.py", line 521, in _serveRequest
    res = method(**params)
  File "/usr/share/vdsm/rpc/Bridge.py", line 277, in _dynamicMethod
    result = fn(*methodArgs)
  File "/usr/share/vdsm/API.py", line 346, in destroy
    res = v.destroy()
  File "/usr/share/vdsm/virt/vm.py", line 3887, in destroy
    result = self.doDestroy()
  File "/usr/share/vdsm/virt/vm.py", line 3905, in doDestroy
    return self.releaseVm()
  File "/usr/share/vdsm/virt/vm.py", line 3832, in releaseVm
    self._cleanup()
  File "/usr/share/vdsm/virt/vm.py", line 1694, in _cleanup
    self._reattachHostDevices()
  File "/usr/share/vdsm/virt/vm.py", line 1301, in _reattachHostDevices
    hostdev.reattach_detachable(dev_name)
  File "/usr/share/vdsm/hostdev.py", line 212, in reattach_detachable
    libvirt_device, device_params = _get_device_ref_and_params(device_name)
  File "/usr/share/vdsm/hostdev.py", line 151, in _get_device_ref_and_params
    nodeDeviceLookupByName(device_name)
  File "/usr/lib/python2.7/site-packages/vdsm/libvirtconnection.py", line 124, in wrapper
    ret = f(*args, **kwargs)
  File "/usr/lib/python2.7/site-packages/vdsm/utils.py", line 1313, in wrapper
    return func(inst, *args, **kwargs)
  File "/usr/lib64/python2.7/site-packages/libvirt.py", line 4182, in nodeDeviceLookupByName
    if ret is None:raise libvirtError('virNodeDeviceLookupByName() failed', conn=self)
libvirtError: Node device not found: no node device with matching name 'pci_0000_05_10_4'


2016-02-02 08:24:40,869 ERROR [org.ovirt.engine.core.vdsbroker.DestroyVmVDSCommand] (org.ovirt.thread.pool-6-thread-50) [7b6f76d2] VDS::destroy Failed destroying VM '75211a37-8ee4-45c8-a8e0-049f13ed29e4' in vds = 
'75694d24-1833-4864-8736-fd80bffb30f7' , error = 'org.ovirt.engine.core.vdsbroker.vdsbroker.VDSErrorException: VDSGenericException: VDSErrorException: Failed to DestroyVDS, error = Node device not found: no node d
evice with matching name 'pci_0000_05_10_4', code = -32603'