Oracle has announced on December 18 that its VirtualBox virtualization product for enterprises and end users had just reached version 4.3.6.The VirtualBox solution is capable of running a large number of OSes, including Windows, Linux, Macintosh, and Solaris hosts, not to mention a lot of other guest additions.
The developers of VirtualBox have started to release updates a lot more often than before, and even if this is just a maintenance version for the 4.3.x branch, a lot of fixes and changes have been implemented.
Highlights of VirtualBox 4.3.6:
• A Guru Meditation VINF_EM_TRIPLE_FAULT caused by VMCB caching with nested paging on certain AMD CPUs has been fixed;
• A Guru Meditation VERR_VMX_UNEXPECTED_INTERRUPTION_EXIT_TYPE that occurred while intercepting debug exceptions has been fixed;
• A Guru Meditation VERR_SVM_UNEXPECTED_EXIT while intercepting debug register accesses has been corrected;
• A VERR_SSM_STRUCTURE_MAGIC that occurred error when trying to load a saved state made with VBox 4.3.4, when VT-x/AMD-V is disabled, has been corrected;
• A few more MSRs have been added to the whitelist required by certain guests.
• Deleting inaccessible Vms is now possible (this was a regression introduced in one of the previous versions);
• The warnings in VM settings about the number of guest processors has been corrected;
• VirtualBox no longer automatically enables 64-bit guests on 64-bit hosts if VT-x/AMD-V is not available;
• Always expose the DMI memory information to Windows 2012 guests;
• A few occasional crashes that occurred on guest display resolution changes have been fixed;
• A fix has been added for a hang that occurred when launching a GUI VM through the API, which crashed due to GUI unavailability;
• Accessing the host driver from non-global zones is now allowed.
More details about this release can be found on the official announcement. You can also check our review of Virtualbox and you can also download VirtualBox 4.3.6 from Softpedia.