Oracle VM VirtualBox 3.2.6 Released Earlier



VirtualBox 3.2.0


Oracle has released the latest update to the popular virtualization software VirtualBox 3.2.6. It’s a small, bug-fixing release but there is a long list of changes, from improvements to the underlying virtualization technology to fixes for specific operating systems. The update comes after the release ofVirtualBox 3.2.0 which introduced plenty of new features and implemented several changes and support for newer hardware.


“Oracle today released VirtualBox 3.2.6, a maintenance release of VirtualBox 3.2 which improves stability and fixes regressions,” the very short announcement on the VirtualBox homepageread.

Highlights of VirtualBox 3.2.6

Fixes to the virtual machine manager (VMM):
· fixed host crash when running 64-bit guests on 32-bit hosts with certain Intel CPUs - VT-x only;
· allow 64-bit SMP guests on 32-bit hosts - VT-x and AMD-V only;
· fixed Guru mediation if guests with more than 2GB are booted with VT-x/AMD-V disabled;
· fixed TR limit trashing - VT-x and 64-bit host only.

GUI fixes:
· added a workaround for a Linux kernel bug which affecting asynchronous I/O on ext4 / xfs file systems;
· added setting for multiple VRDP connections - useful if multiple screens are enabled;
· another fix for the keyboard capturing bug under Metacity;
· handle the extra key on the Brazilian keyboard on X11 hosts again;

Linux specific:
· re-read a directory after a file was removed;
· install the DRI driver in the right location on ArchLinux guests;
· fixed spurious mouse movement events in X11.

About VirtualBox
VirtualBox is a popular virtualization software now owned by Oracle after it bought Sun Microsystems. It works on all major x86 platforms and supports a large number of guest operating systems. VirtualBox is closed source but is offered for free. There is also an open-source version dubbed Virtual Box OSE (open source edition). 



Download Now

No response to “Oracle VM VirtualBox 3.2.6 Released Earlier”

Leave a Reply

Page Navigation

 
span.fullpost {display:inline;}