Virtualbox upgraded - now no VM can be started anymore

extasic · Post by **extasic** » 3. Jan 2009, 23:32

Hi!

I was using Virtualbox 2.0.4 on Windows Vista x64 Host. Without really having any problems I decided to follow the announcement and upgrade Virtualbox to 2.1.0. So I removed Virtualbox using the Control Panel and installed the amd64 Version of Virtualbox 2.1.0. The installation proceeded without any problems.

When starting Virtualbox the VMs were imported correctly, but I couldn't start one of them correctly anymore. When I try to start them (I tried Windows XP 32bit Guests), the "Starting Virtual Machine... 0%" Window appears, but then nothing else happens. The process VBoxSVC consumes more than 60% of my CPU - when killing it, the VM boots as usual. Nevertheless using CD images doesn't work any more - when choosing e.g. the Guest Additions ISO, the error message says:

Callee RC:Unknown Status 0x800706BA (0x800706BA).

I disabled 3D acceleration (didn't even enable it), removed all network devices (not only disabled them), create a brand new VM - but it's always the same...

There's another strange thing: The main window still says "Starting" on the running VM, even if it has been shut down. When restarting Virtualbox, it says "Canceled" there.

I uploaded the log file here.

I already checked the bugtracker, but there was no directly related entry. I also downgraded to 2.0.6 - and as well to the original working version 2.0.4 - but I can't get it working anymore..

Do you know what I can try and what might be the problem?

Thank you in advance!

fctc · Post by **fctc** » 4. Jan 2009, 08:48

Have you tried rebuilding your VM?

Just go through the steps of creating a new VM, but use the old (existing) .VDIs when asked for primary drive.

I had to do that when I went from 2.06 to 2.10 with my VMs on top of 32-bit Vista.

FCTC

extasic · Post by **extasic** » 4. Jan 2009, 11:21

thank you for your answer!

unfortunately that didn't help. I used the existing (working) vdi for creating a new machine, but it still freezes at the following screen

any other ideas?

fctc · Post by **fctc** » 5. Jan 2009, 11:54

I have had aborted bootups from unexpected sources. I had to kill my CD pass-through. I have had USBs strangle boot ups.

My fix:
-Removed all VM peripherals, frequent shut down or kill of VM, reboots of host after each stage of remova.
-Started a NEW machine, used existing .VDI (which you indicated you tried), and lucked out.

Just guessing. I am by no stretch an expert with this. Lots of trial and error. I would also search or browse all references to 64-bit OS as I quite a few issues popping up.

Good luck,
FCTC