4.1 Bug Fixes in Oracle VM 3.4.5

Oracle VM Release 3.4.5 includes the notable bugs that have been fixed in previous 3.4.x errata releases. Additionally, Oracle VM Release 3.4.5 includes a number of enhancements, as described in Section 3.1, “What's New in Oracle VM Release 3.4.5?”.

Notable bugs fixed in Oracle VM Release 3.4.5 are as follows:

  • To resolve SSH connection issues with the Oracle VM Manager Command Line Interface, the SSH server implementation used by the CLI has been updated to support all required security algorithms. Systems accessing Oracle VM Manager using OpenSSH Release 7.0 can now connect to the CLI using the stronger default security protocols. (24742496)

  • Connection leaking in the Oracle WebLogic component used by Oracle VM Manager has been fixed. This eliminates login failures, database corruption issues and connection errors experienced by some Oracle VM Manager users due to a lack of available resources. This fix reduces the occurrence of error messages such as "no resources available in pool ovm-odof-ds to allocate to applications" and "Waiting for connection". (26675991)

  • The Oracle VM Server installer can now complete the installation process in case xen.gz is not present; for example in the case of ipxe-, uefi- ,and iscsi-based installation. (24376778)

  • Virtual machine logging has been enhanced to indicate what causes the migration of a VM. For example, when a VM is live-migrated due to a DRS policy, administrators see information such as "CPU usage is at 41.1% which is over the threshold of 25.0%". (27911937)

  • Several issues have been addressed with the Oracle VM Agent and generic Oracle Storage Connect plugin. This includes better retrieval of device mapping information when EMC Power Path is in use. (27901631)

  • The RDMA functionality has been improved to correctly detect and configure Mellanox network interface cards, whether they provide Ethernet or InfiniBand connectivity. This allows Oracle VM to complete its boot sequence on systems with Mellanox cards installed and RDMA enabled. (25238309)

  • Scripts in the Oracle VM Agent have been improved to correctly detect Ethernet and InfiniBand interfaces manufactured by Mellanox. This eliminates issues with creating bond interfaces on servers containing network interfaces of the affected types. (26541812)

  • The Oracle VM devmon service has been hardened to correctly handle block devices with long names and paths, as well as multipath devices. This significantly reduces the risk of the service crashing due to a buffer overflow. (27486687 and 27486525)

  • The method to persist certain server pool settings, such as the cluster timeout, has been improved. Customized server pool settings are now correctly preserved even after a regeneration of the Oracle VM Manager database. (26795755)

  • If a virtual machine is configured with CPU pinning, it can now be cloned to a template. This operation failed in previous versions. (26789306 and 26365024)

  • Statistics collection through the Oracle VM Agent has been improved to make sure that repository file system details are always communicated correctly to the Oracle VM Manager. (26003962)

  • An issue was resolved where virtual machines configured with an amount of RAM close to the maximum provided by the host server, regularly failed to start or restart. The Oracle VM code now makes sure that there is enough scrubbed RAM available before the VM is started. (27534600)

  • An issue in Xen 4.4.4-155.14 through 4.4.4-155.17 has been resolved to allow Oracle Solaris guests with multiple vCPUs to boot correctly. (27525698)

  • The Oracle VM Manager code for operations on virtual machines with high availability enabled has been improved to ensure the correct VM status is always reported. (27241657)

  • Thanks to better management of C-states in Xen, virtual machines can now take advantage of higher frequencies of physical CPUs at times when the load on other CPUs in the system is low. (27182738)

  • When "Best Server" is selected as the VM start policy, an improved algorithm now selects a server more efficiently than before. This results in significantly better performance and shorter times for a virtual machine to start up or Live Migrate. (27161103)

  • The upgrade code has been hardened to ensure that an Oracle VM Server can never be upgraded to a version higher than Oracle VM Manager. In a normal upgrade scenario, the Oracle VM Manager is upgraded first, and can be used to manage certain older Oracle VM Server versions until they are also upgraded. However, managing newer Oracle VM Server versions is not supported. (26988270)

  • With certain devices, SCSI inquiry commands generate warning messages in the logs, because the commands are not supported by the device and considered illegal. Since there is no impact on functionality, the logging has been modified to write DEBUG instead of WARNING. (26932873)

  • It is now acceptable that the URL of the Oracle VM Manager Web Interface starts with "https://console.<domain>". Previously, the word "console" at the start of the URL would be rejected, and the connection attempt would result in an "Error 404: Page not found". (26283106)

  • Additional checks for resource locking have been included in Oracle VM Server for SPARC, to avoid crashes due to duplicate removal attempts and similar purge list issues. (26241929)

  • Virtual machines running Oracle Linux with UEK R2 no longer lock up during live migration, thanks to a fix that allows processes to be frozen and thawed correctly through Xen. To take advantage of this fix, you must upgrade the virtual machine kernel to the latest version of UEK R2. (25644455)

  • A newly implemented Xen boot parameter, dom0_vcpus_pin, allows administrators to specify how dom0 vCPUs are mapped to the server's physical CPUs. This results in more flexible and accurate CPU pinning. Further information on CPU pinning can be found in Oracle VM Virtual Machine Control, in the Oracle VM Administrator's Guide. (25559771)

  • Code changes have been implemented to make sure that configuration updates to a virtual machine, such as disk migrations, are always represented correctly in the vm.cfg file. Previously, discrepancies sometimes occurred when jobs failed and modifications were not rolled back. (24626034)

  • Several issues have been addressed with Template and Virtual Appliance data truncation in the MySQL database. Previously, origin file paths longer than 4,000 characters could result in job errors and Oracle VM upgrade failures. (23099378)

  • In the storage configuration section of the Anaconda installer, a call to a non-existent kernel module has been removed. The many resulting non-fatal log messages no longer appear, which makes debugging much simpler. (27525259)