Just a quick note between v3.0.4 and VBox 3.0.6 Beta1
When booting a Guest Win2003 64bits, it shows up the Windows filling bar at booting and then it turns the screen black and stays there forever... consuming an average of 50%.
Sometimes it does boot, but stays consuming a 50% processor.
The 32 Bits Guests works like a charm, no problems at all.
I'm beginning to wonder if this is a problem with all 64-bit guests, or at least with all 64-bit guests under certain conditions. I just upgraded from VirtualBox 2.2.4 to 3.0.6 this evening, and the first three virtual machines that I tried to boot up all hung somewhere during the bootup process (such as during the OpenSUSE or Windows 7 splash screen), just as described by others in this thread. I also noticed that they were using up to 50% CPU utilization, as has also been noted by others here. I was about to wipe everything, uninstall 3.0.6, and go back to 2.2.4 and re-install from my virtual machine backups, when I decided to try one of my other virtual machines. To my great surprise, it worked perfectly. I tried two more, which also worked perfectly. I then noticed that all of the machines that worked perfectly were 32-bit guests, while all three of the machines that failed were 64-bit guests. My host is Windows XP SP3 (32-bit), and I am using VT-x and nested paging on all of the virtual machines (I have an Intel Core i7). Thus, this could be a problem specific to VT-x (since I need to use VT-x to run the 64-bit guests on my 32-bit host), or it could be related to all 64-bit guests. Is anyone with an AMD machine (or other non-Intel machine) also having these problems with 64-bit guests? Thanks!
