Oracle VM: Failure to start guest Virtual Machine: "Hotplug scripts not working"
Last updated on APRIL 04, 2017
Applies to:Oracle VM - Version 2.2 to 3.1.1 [Release OVM22 to OVM31]
***Checked for relevance on 24-May-2012***
In some cases, starting an Oracle VM guest Virtual Machine (VM) may fail with the the following error (as denoted in Oracle VM Server /var/log/ovs-agent/ovs_operation.log):
Traceback (most recent call last):
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 2057, in _restart
File "/usr/lib/python2.4/site-packages/xen/xend/XendDomainInfo.py", line 1078, in waitForDevices
File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 140, in waitForDevices
return map(self.waitForDevice, self.deviceIDs())
File "/usr/lib/python2.4/site-packages/xen/xend/server/DevController.py", line 153, in waitForDevice
raise VmError("Device %s (%s) could not be connected. "
VmError: Device 2 (vif) could not be connected. Hotplug scripts not working.
Or with error logs below on Oracle VM Manager:
PowerOn Failed : Result - failed:failed:Error: Device 2 (vif) could not be connected. Hotplug scripts not working.
The Oracle VM Server may be experiencing heavy load
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms