[ PCA / OVM ] Restart of Virtual Machine With Start Policy of "Best Server" Takes Excessive Time After Upgrade of OVM / PCA
Last updated on APRIL 16, 2018
Applies to:Oracle VM - Version 3.4.1 to 3.4.4 [Release OVM34]
Private Cloud Appliance - Version 2.3.1 and later
After upgrade of PCA to 2.3.1 or 2.3.2 (which upgrades OVM component to 3.4.x), or upgrade of OVM to 3.4.x from 3.2.x or 3.3.x, a restart of a virtual machine subject to Start Policy of "Best Server" can take several minutes.
Prior to the upgrade (from PCA 2.2.x, incorporating OVM 3.2, or OVM releases prior to3.4.x), restart of such a vm would take only a few seconds.
The delay occurs regardless of whether:
- the vm is restarted using OVM Manager UI or CLI
- the vm is restarted using a command within the vm (e.g. "reboot")
The delay does not occur if the vm is (re)started on an OVM Server / PCA Compute node using the "xm create" command.
The delay does not occur if the vm has "Start Policy" of "Current Server"
Newly created vm's with "Start Policy" of "Best Server" are also affected.
Upgrade to PCA 2.3.1 or 2.3.2 from prior releases
Upgrade to OVM 3.4.x from prior releases
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