Software Update: VirtualBox 6.1.2

Oracle has released the first update for VirtualBox version 6.1. VirtualBox can be used to install other operating systems in a virtual environment on a computer. In this way it is possible to use different operating systems on the same hardware side by side and at the same time. VirtualBox is available for Windows, macOS, Linux, and Solaris, and is able to guest operating systems to turn. The changes made in version 6.1.2 are listed below:

This is a maintenance release. The following items were fixed and/or added:

• Virtualization core: fixed performance issue observed with Windows XP guests on AMD hosts (6.0.0 regression; bug #19152)
• Virtualization core: consistent IBRS/IBPB CPUID feature reporting, avoids crash of NetBSD 9.0 RC1 installer (bug #19146)
• GUI: fixed updating or runtime info
• GUI: in Display settings, do not show “2D video acceleration” checkbox if it is meaningless for the selected graphics adapter
• Audio: fixed audio input handling when VRDE is enabled
• Audio: fixed crash in the HDA emulation when using multi-speaker configurations
• Storage: fixed use of encrypted disks with snapshots involved (6.1.0 regression; bug #19160)
• Storage: improve performance of virtio-scsi
• Storage: read-only support for compressed clusters in QCOW2 images
• Windows installer: include unintentionally dropped vbox-img.exe utility again
• Windows host: when installing or removing an extension pack, retry the sometimes failing directory renaming (usually caused by anti-virus software accessing the directory)
• Linux host: Support Linux 5.5 (guest additions not yet)
• Windows guest: accelerate 2D video decoding (scaling and color space conversion) if the VM is configured to use VBoxSVGA with 3D enabled
• Windows guest: fix guest additions installer to upgrade the mouse filter driver reliably
• Windows guest: when uninstalling older Guest Additions with old 3D support enabled try restoring original Direct3D files
• Linux guest: improve resize and multi-monitor handling for VMs using VMSVGA (known remaining issue: do not disable a monitor “in the middle”, causes confusion)