Host system resets (crashes) when using VMWare or VirtualBox and 64-bit guest systems
- by sinni800
I have been trying to install virtual systems on VMWare for a while now and encountered strange behaviour from my PC.
The behaviour is as follows:
On "automatic" virtualization mode it either outputs a cryptic error message (can MAYBE give later, if I can reproduce) right on startup (before even the BIOS) or it resets the complete HOST system (blackscreen, bios...)
If I install a Windows XP on it it works well on "binary translation" mode.
If I try installing Linux on it, in "binary translation" mode it crashes 1 or 2 seconds after I hit enter on the GRUB selection screen (after the first page of kernel messages rolled in)
Using VirtualBox it crashes right in the BIOS. It gave me a Bluescreen though! 0x00000101: CLOCK_WATCHDOG_TIMEOUT: a clock interrupt was not received on a secondary processor within the allocated time interval
NEWS: I tried VirtualBox again and it did not completely crash the computer this time. It gave me a critical error and a log file: http://pastebin.com/yKZSDs91
In conclusion, it will crash instantly if VT-x is activated. If not, it seemingly only crashed if I try to install something with 64 bits.
Another update: Yes, it ONLY crashes when the guest is 64 bit!
What I tried:
Reinstalling Windows (my Windows installation was quite broken so it seemed natural. Didn't work though.)
New BIOS
What I am certain of:
Virtualization extensions are activated in the BIOS
What my computer specs are:
ASUS P8P67 LE mainboard, newest BIOS/EFI firmware
Intel Core i5 2500k
Ati Radeon HD 5770
16 GB Corsair 1333mhz DDR3 RAM, 4 X 4 GB
