virtualbox.org

Hi every body, I don´t know if this is the correct place for this post. Let's see.
1. I had VBox 2.2.4 installed, host vista x64. Lot's of VM´s, mostly linux flavors, one bsd, one solaris, one windows xp x86.
2. Upgraded to VBox 3.0.0. Started XP VM, it was really SLOW, when it finally finished booting, I installed the additions. It hanged. Would not boot again.
3. Decided to recover my entire vista "C" drive. (Acronis), OK, Started VBox 224 again: XP guest was totally corrupted, had to erase it.
4. Looked arround some. Waited a couple of days, out comes VBox 3.0.2
5. Installed it. (Upgrade). Booted an Linux Mint 7.0 x86 guest. SLOW to boot, but no as slow as the xp before. Installed the guest addins. It took a COMPLETE HALF AN HOUR TO INSTALL. (guest has 2gb ram assigned).
6. Rebooted guest. X wont come up, I don't even get the login screen, just a black screen with a garbled green small border on top.
7. Went back to 2.2.4. Thanks god this time I had also backuped the guest VM.

This is a disaster. NEVER before I had these problems when upgrading VBox. Usually I upgraded, installed the new additions in the guests & went on working...
All my 10 or 12 Guests are highly customized. I don't want to install everything again.
Please guys; what gives what should I do

Hi,

I have the same issue. As soon as I have upgraded to version 3.0.2 r49928 and install VBoxAdditions the Guest stopped working. I find out that is possible to log in, though. I'm using a Guest for OpenSolaris 200906 and as soon as the black screen appears with blue bar on top (It seams that it compresses the log in image on top) I write the user name, press Enter, then write the password and hit Enter again, and I'm able to log in, and the image recovers correctly. It shows the OpenSolaris Desktop correctly. Only the Log in appears garbled.

Hope that this issue is resolved very soon.

Best regards to All.

J. Ramos.

I find that the upgrade goes smoother if you uninstall the current version before installing the new version.
Next with 3.0.x you have a different approach to installing the guest additions. In Windows you must do this in safe mode. Otherwise the drivers that VBox installs will get over written again with the Windows drivers and strange graphics things can happen.
Then you should look at the processor tab in the guest and make sure that you have one CPU selected and also that you do not have I/O-APIC turned on, if this is a 32 bit guest. If it is a 64 bit guest and you have a 64 bit host you will need to see if you have the right kernel installed in the guest for SMP.

Perryg, maybe. But I have 12 VM,s. Most of them with ioapic enabled, till now they alll worked ok and survived multiple vbox upgrades without a hitch. Be they linux, solaris, pcbsd, xp, win7. and be they x86 or x64 variants.
Never had to uninstall additions, never had to install additions in safe mode in the windows variants, etc.
Always (till now) upgrade has been as smooth as a kids face...
If a MAJOR change in all these variables is necesary, vbox people should warn before hand:
1. If uninstalling previous ver is mandatory
2. If uninstalling additions in guest is mandatory
3. If CHANGING GUEST HARD PARAMETERS is mandatory
4. I mean a general (AND LOUD AND CLEAR) readme or how to, etc.

I as, many others use this for work not for playing arround. If I have to reinstall all my VM's with their customizations it's a pain in the *s* and it would make me lose time, and time is money

Maybe I´ll wait for a fix, if it comes, OK, if not i'll start thinking about vmware.