Virtualbox 2.2.0 available and unstable use 2.1.4

[WarraWarra]

http://www.virtualbox.org/wiki/Downloads

Edit:
They added ich6 instead piix4 as well as sata achi.

Yeah they updated again and released today.

To be IBM Virtualbox or to to be Sun Virtualbox that is the question LMAO.

http://www.theregister.co.uk/2009/04/08 ... albox_2_2/

With the 2.1 release last December, Sun was already supporting VMware's VMDK and Microsoft's VHD virtual machine disk formats along with VirtualBox's own VDI native format.

Time to update and see.

[Thev00d00]

woooop wooop! Compiz in a VM ftw

[WarraWarra]

For the newby's or anyone using the 2.2 in windows please note they still have some major issues with stability especially with the sata achi if this is enabled and any guest OS you try to boot on it.

If testing SL in windows virtualbox I would recommend you stick to the old hardware ie: scsi / ide and piix4 and stay away from the ich6 or sata achi new parts as you might end up with 90% boot failures / install failures and severe virtualbox lockup's until they fixed this.

Best is still to use the previous version of Virtualbox in windows.

The defective build = 45846

[WarraWarra]

Just thought I would post alternative download links to virtualbox as even in their forums they are having serious doubts about 2.2.0 stability.

So for all windows users / new users wanting to first test drive SL in Virtualbox you can use this links to get a stable copy of Virtualbox.

http://download.virtualbox.org/virtualbox/2.1.4/

[Thev00d00]

Surely you would you should reccomend the virtualbox bin package via entropy?

Code: Select all

equo install virtualbox-bin

[thenthenio]

Pay attention with VirtualBox 2.2.0 I found a number of problems and I was afraid not to be able to recover my VMs.

I updated my SL box and VirtualBox was updated too to 2.2.0.
When starting the VirtualBox GUI it notified the need for updating configuration files, after that it HANGED.
There was no way to wave it running with the old configuration.
Manually renaming my .VirtualBox folder I was able to run VirtualBox GUI as a new installation.
Then I was not able to import or open the existing virtual machines.
So I created them from scretch using the exiisting .vdi (disks) files.
The (Window$) VM were starting but all CRASHING at the beginning of the boot process with a typical WIN BLUE SCREEN and then looping back to boot (asking for normally or maintenance mode), none of the modes was good and the VM was looping again and again: blue screen-boot-blue screen-boot...
I also tried booting from CDROM and performing CHKDSK /F (as suggested by NT loader) but that failed too.

The solution was:

In VirtuaBox GUI -> Details tab -> General VM setttings -> Advanced tab: select IDE controller type as PIIX3

That cured the problem and VMs boot as usual.

Cheers.
Mauro

[WarraWarra]

That is good to hear.

In win 2.2.0 it is sata achi and ich6 in lin 2.2.0 even down to piix4 is causing issues.

Can you confirm if you can get the virtual machine now contaminated with 2.2.0 converted to be used back in 2.1.4 or are you stuck with 2.2.0 and piix3 until a fix arrives.

Speed and performance good / slow as piix4 was linked to pentuim4 north bridge if I remember correctly and does 4.1gnome boot on this ? as it is not too happy with older hardware.

PS> just noted 2.2.2 is out anyone want to take a chance on it ?

Please report results of 2.2.2 before we add it to entropy

http://www.virtualbox.org/wiki/Downloads

[thenthenio]

Can you confirm if you can get the virtual machine now contaminated with 2.2.0 converted to be used back in 2.1.4 or are you stuck with 2.2.0 and piix3 until a fix arrives.

I don't know how to revert to 2.1.4...
Anyway I'll wait for VirtualBox 2.2.2 in Entropy.

Mauro

[WarraWarra]

This is a very old post , virtualbox 3.0.2 is out already for some time.