virtualbox.org

It sounds like something gets left behind when upgrading, maybe some older component gets stuck.

vbox4me2 wrote:It sounds like something gets left behind when upgrading, maybe some older component gets stuck.

i have setup the Host two times. the first with Vista and the second xp x64. on both hosts i have the same Problem.

Hello,
Sorry for my bad english but i am french.

I have the same problem. AMD-V Was activated and fonctional. But i can't install windows server 2008 x64 or windows server 2008 x64 R2. it freeze at starting windows... and in safe mode it freeze after disk.sys.

I'm somewhat happy to hear I am not the only one having issues. AMD processors seemed to have been given the bump after 2.1.4. All 32 bit OS's work fine, but very few 64 bit OS's work with AMD processors. I have a newer Turion "Puma" Ultra CPU ZM-84 and Phenom 955 series. None will boot OpenSolaris, Solaris, XP 64, Windows 7 64, but.... they will boot Ubuntu 9 64 bit. Go figure. I'm sure it is a simple issue, but apparently not enough people have raised the issue. Please, someone look into this.

If a dev want it i can post my BIOS Image and more Hardware Informations. We are not alone and please dont ignore us.

Nille02 wrote: The same issue. Windows freeze at "Setup is starting Windows" and the VirtualBox process eat up 50% CPU on an DualCore System.

Sometimes i get an BSoD on the VM http://img145.imageshack.us/img145/121/bsody.png but not everytime.

PS: Again on VB 2.1.4 everything is fine.

I'm having similar problem with W7 64bit. My system was freezing too during the load of the installation. I was able to get beyond that by increasing the amount of RAM to the VM to 768MB. Once I did that, I got pass the freeze, but now I get a BSOD with error ox00000007E.

BTW, I am successful with installing the W7 32 bit guest.

Sounds like there are lots of us having issues with AMD-V in any version past 2.1.4. Dangling the SMP and OpenGL support in later versions in front of us is just plain cruel.

Memory isn't an issue for me with 8 gigs in both machines. Trying to setup a few demonstrations of VDI and VirtualBox for a University. I'm hopeful (crossing my fingers), that someone with a little more knowledge on the code can grace us with some insight as to why AMD processors are having such a hard time?

Post your findings in the bug tracker ticket please.

All I can tell you so far is that the problem appears restricted to certain AMD cpus. I've got a quad core Opteron and 6 core Shanghai system here and all 64 bits guests work just fine.

sandervl wrote:All I can tell you so far is that the problem appears restricted to certain AMD cpus. I've got a quad core Opteron and 6 core Shanghai system here and all 64 bits guests work just fine.

Its maybe an problem with Nested Paging ?

bump

See http://forums.virtualbox.org/viewtopic. ... 468#p86468
Hopefully this will solve your problem.

Yes, I've just fixed a very old bug that affects 64 bits guests on AMD machines.

This are great news i hope the new version coming soon.

I have the same issue with a 32-bit Windows 7 host and a 64-bit Windows 7 guest. The Windows setup hangs at the "Starting Windows" screen. I do have hardware virtualization and it is enabled, because XP Mode works. Is it a requirement to have a 64-bit host?

Hello,

I have exactly the same problem on a T9600 Core Duo 2. Using Virtualbox 3.0.6 on Windows Vista x86 host with VT-x enabled in Bios all x64 guest OS (Windows x64 all versions) lock up during startup, same problem as described with the other posters.

I am going to try to downgrade to 3.0.4 and see if I have the problem there as well.

In the mean time, is there anybody with a solution to this problem or will there be a fix in the next version ?

Kris.