Discuss VirtualBox 2.1.2 Release

Post by **TerryE** » 22. Jan 2009, 17:48

This topic is for discussions on the VirtualBox 2.1.2 Release as announced today. For discussions on 2.1.0 see Discuss VirtualBox 2.1.0 Release. However, users are recommended to upgrade to 2.1.2 at the earliest convenience.

wumpus42 · Post by **wumpus42** » 22. Jan 2009, 18:03

I had installed a Windows 7 Beta Guest under VBox 2.1.0 as 'Other Windows'. I've since upgraded to VBox 2.1.2. Can I just change the VM def to "Windows 7" or should I re-install the guest? I changed it and all seems fine, but I just wanted to make sure.

Post by **TerryE** » 22. Jan 2009, 18:04

There was a variant of this topic created here which I've locked because I want to keep this discussion in a standard place. Key points discussed are:

bqbauer wrote:On 64-bit Solaris, new 64-bit guests seem still to be limited to 3584MB memory, apparently contrary to the release notes. I made sure I'm running the 64-bit VB since they're packaged together now, and even rebooted after uninstalling 2.1.0 and installing 2.1.2.

nvivo wrote:Good job, but the disk compact option is still unavailable.

The error message on "VBoxManage modifyvdi compact" changed from "Temporarily unavailable" to "disk operation not implemented".

sej7278 wrote:Solaris 10 (specifically U6) guest additions ... install fine on 10u6 64-bit, but still seem to do nothing - no seemless or window resizing or mouse integration.....

You should try redhat 4u7 32-bit, the additions won't even install!

They do seem to have fixed redhat 5u2 32-bit as window resizing works again now.

Still no sound from windows 7beta1 though.

Post by **Martin** » 22. Jan 2009, 18:17

TerryE wrote:There was a variant of this topic created here which I've locked because I want to keep this discussion in a standard place. Key points discussed are:
nvivo wrote:Good job, but the disk compact option is still unavailable.

The error message on "VBoxManage modifyvdi compact" changed from "Temporarily unavailable" to "disk operation not implemented".

The command was changed from "modifyvdi" to "modifyhd".

Martin

mivok · Post by **mivok** » 22. Jan 2009, 19:20

Martin wrote:The command was changed from "modifyvdi" to "modifyhd".

It still isn't implemented if you use modifyhd, however, clonehd is supposed to work without corrupting the image. I'm testing this currently (waiting for zerofree to finish).

Post by **Sasquatch** » 22. Jan 2009, 20:02

wumpus42 wrote:I had installed a Windows 7 Beta Guest under VBox 2.1.0 as 'Other Windows'. I've since upgraded to VBox 2.1.2. Can I just change the VM def to "Windows 7" or should I re-install the guest? I changed it and all seems fine, but I just wanted to make sure.

No that doesn't matter. The OS type is only a template for some settings like RAM and hard disk (when creating a new disk).

rober1s · Post by **rober1s** » 22. Jan 2009, 21:16

According to this comment from the release notes:

GUI: raised the RAM limit for new VMs to 75% of the host memory

Our Linux host (Kubuntu 8.04, 32-bit dual Quad-core Xeons) has 8 GB of physical RAM, which the host can see and use, enabled via the kernel HIGHMEM and PAE configuration.

On this host, we should therefore be able to allocate 0.75 X 8.0 = 6 GB for a new VM. However, the GUI still allows a maximum memory allocation of only 3.584 GB for a new Windows XP VM.

Is the wording on the comment in the release notes incorrect? Should it have been stated as

GUI: raised the RAM limit for new VMs to 75% of the host memory, or 3.584, whichever is smaller

redxii · Post by **redxii** » 22. Jan 2009, 22:01

How can I tell I have 2.1.2? I installed inplace, but saw the About page says 2.1.0, I uninstalled then installed, and it still says 2.1.0? I'd say it's 2.1.2 since I doubt 2.1.0's files were signed January 21, 2009.

Post by **stephanecharette** » 22. Jan 2009, 22:14

redxii wrote:How can I tell I have 2.1.2? I installed inplace, but saw the About page says 2.1.0, I uninstalled then installed, and it still says 2.1.0? I'd say it's 2.1.2 since I doubt 2.1.0's files were signed January 21, 2009.

$ vboxwebsrv --version
Sun xVM VirtualBox Webservice Version 2.1.2

Or in the GUI, click Help->About. In the bottom of the window it should say "Version 2.1.2 Copyright (C) 2009 Sun Microsystems, Inc....." At least mine does.

Stéphane

redxii · Post by **redxii** » 22. Jan 2009, 22:20

(Windows)

It says copyright 2009, but it says 2.1.0. 2.1.0 says copyright 2008. vboxwebsrv.exe says 2.1.2

microkid · Post by **microkid** » 22. Jan 2009, 22:31

redxii wrote:(Windows)

It says copyright 2009, but it says 2.1.0. 2.1.0 says copyright 2008. vboxwebsrv.exe says 2.1.2

Post by **Sasquatch** » 22. Jan 2009, 22:38

Both my Linux as Windows (XP) say 2.1.2.

bill_mcgonigle · Post by **bill_mcgonigle** » 23. Jan 2009, 00:57

I had a heck of a time getting the update downloaded. Firefox 3 just bailed. Speed Download 5 got a corrupted download ("codec overrun" error from diskimagmounter).

Finally, I was able to download with:

curl -v -L -O http://download.virtualbox.org/virtualb ... 85-OSX.dmg

and it verified and installed fine. Hope that helps somebody.

(no, no other sites exhibit this problem)

fredlwm · Post by **fredlwm** » 23. Jan 2009, 02:02

On Linux, moving from 2.1.0 to 2.1.2 changed something. When I launch the GUI, it starts using the CPU. Load average is around 1,00 after some time, but doesn't increase.

This is on kernel 2.6.28.

joggel · Post by **joggel** » 23. Jan 2009, 11:54

I'm running linux (openSuSE 11.0) guest on wxp 32bit host.
Just upgraded from 2.1.0 to 2.1.2 and some very annoying memory management behavior from 2.1.0 (host stood still for 1h until I killed the VM when copying a lot of data to a vdi disk) has been repaired.

Thanks a lot!

virtualbox.org

Discuss VirtualBox 2.1.2 Release

Discuss VirtualBox 2.1.2 Release

Guest memory

Re: Discuss VirtualBox 2.1.2 Release

very positive