3. Notable Bug Fixes

3.1. Bug Fixes in Oracle VM 3.1.1
3.2. Bug Fixes in Oracle VM 3.0.3

This section discusses any notable bug fixes in Oracle VM. There are many other bugs that are fixed in this release; this section highlights the more notable ones. This information is useful to users who have used previous releases of Oracle VM.

3.1. Bug Fixes in Oracle VM 3.1.1

The following notable bugs are fixed in Oracle VM Release 3.1.1:

  • Outage scenario requires acknowledging multiple events on multiple objects. (13845733)

  • The installer does not allow the reuse of an existing database. (13744793)

  • Cannot remove server pool file system from Oracle VM Manager if the server pool file system is corrupted. (13601257)

  • Unable to create a repository on a LUN that already has partitions on it. (13596838)

  • HVM guests failed to start or panic when MEM is not equal to MAXMEM. (13560881)

  • Cannot remove VM and Oracle VM Server from Oracle VM Manager if the Oracle VM Server goes away. (13473061)

  • OCFS2 storage repository size is not updated in core and user interface even if repository is refreshed. (13449381)

  • Oracle VM Server boot over multipath SAN fails to initialize DM MP devices. (13341598)

  • VM start is pending. (13044663)

  • API for CPU utilization returning negative values. (12999197)

  • Resizing a physical disk/LUN does not resize the file system. (12962538)

  • Oracle VM Server fails to boot from multipath SAN disks. (12682785)

3.2. Bug Fixes in Oracle VM 3.0.3

The following notable bugs are fixed in Oracle VM Release 3.0.3:

  • Oracle VM Manager upgrade improvements significantly reduces upgrade time.

  • IP addresses entered in Oracle VM Manager are always validated to ensure correct formatting. An error message is displayed if the IP address is not properly formatted.

  • The Linux kernel device manager (udev) has been improved to increase performance. The most significant improvement is that the time udev takes to run after booting the server has been shortened from 2-3 minutes to just seconds, eliminating system 'hangs' and other problems in systems which are sensitive to startup time.

  • When the management network also fulfills the role of virtual machine network, a bridge for virtual machine network connectivity is created on Oracle VM Servers as they are added to the environment. As a result, virtual machines will continue to work properly when migrated to a new Oracle VM Server.

  • DHCP is able to be used for VLAN Group interfaces. (13322814)

  • Both Oracle VM Server and the Unbreakable Enterprise Kernel (UEK) have been patched to prevent the flood of kernel warning messages caused by illegal configuration of certain Broadcom NetXtreme II XGb (bnx2x) network controllers. If an illegal configuration is detected, only one warning message per controller card is displayed.

  • Several network throughput issues with certain Broadcom NetXtreme II XGb (bnx2x) network controllers on Oracle VM Server have been resolved: default TPA settings have no adverse effect on network throughput, and network between virtual machines and NFS storage no longer hangs with bnx2x controllers.

  • When using the untagged VLAN segment, the user must configure IP address information on the NIC port, not on the VLAN interface. This eliminates duplicate configurations and any associated risks of misconfiguration.

  • A late locking scheme has been implemented for networks on virtual machine clones: the virtual NIC connection in the virtual machine is only locked at the end of the clone operation. As a result, locking issues with ethernet networks no longer occur when multiple virtual machines are cloned in parallel from the same template.

  • In Oracle VM Manager, the Acknowledge All Events button effectively clears all events, not just the items visible in the current list view.