Page 1 of 1

2.2.0 - x64 guests doesn't get started anymore

Posted: 16. Apr 2009, 22:25
by bumsbomber
Hi!

Since i've updated from VirtualBox 2.1.4 x64 to VirtualBox 2.2.0 my x64 guests doesn't get started anymore. I've get this message when i try to start them:

Image

Code: Select all

Windows could not start because of a general computer hardware
configuration problem.
Attempting to load an x64 operating system, however this CPU
is not compatible with x64 mode.
Please install an x86 32-bit operating system.
As descriped in the help of VB, i activated VT-x in the settings of my VM.

Image

With 2.1.4 my x64 guests (WinXP Pro x64 and Win7 x64) worked without any problems. After updating to 2.2.0 they won't start anymore. VT-x is activated in BIOS. There are no problems/errors occured while the install of VBox 2.2.0. I also can't install new x64 guests. The host is WinXP Pro x64 SP2.

Does anyone have suggestions?

Re: 2.2.0 - x64 guests doesn't get started anymore

Posted: 24. Apr 2009, 23:04
by bumsbomber
I know, begging for answers sucks - but I really need help.
x64 guests still doesn't work, I don't understandy why.

Re: 2.2.0 - x64 guests doesn't get started anymore

Posted: 24. Apr 2009, 23:22
by vbox4me2
I'd suggest to go back to 2.1.4 and open a bug ticket on bugtracker if this isn't listed there.

Re: 2.2.0 - x64 guests doesn't get started anymore

Posted: 24. Apr 2009, 23:28
by Perryg
Try reinstalling VBox and this time do it as administrator (right click the install file, then left click run as... Select admin)
Select the repair function and see if this helps.
You will need to reboot after the install, and you will also need to reload the guest additions.
Before starting the guest make sure that the VT-x has a check mark and try to open the guest.

Edit: I see that vbox4me responded as I was hitting the send key. Still would not hurt to try this also.

Re: 2.2.0 - x64 guests doesn't get started anymore

Posted: 24. Apr 2009, 23:35
by bumsbomber
Haha, begging works :D

Thanks for answers - but it's soooo typical: After starting the begging here I found the solution deep in google results with a very complex search term :lol: . It's a bug in BIOS of the abit mainboard. I had to restart pc and deactivate VTx in BIOS. Then I had to shut down the PC completely (& plug it off) - after a few seconds I had to start the PC and reactivate VT-x in BIOS and restart the PC again. Now it works :)

Stupid BIOS.