virtualbox.org

After update of VirtualBox (my current updated and not working for Windows guests version is 3.0.2 r49928) my Windows guests keep on crashing. The windows logo is shown and when it should switch to desktop the BSOD comes in and restarts the VM (this is on Fedora 11). I tried to do a whole new install - the same thing. I tried it on a different machine (Ubuntu 8.0.4) - fully updatet Vbox and again fresh install - same thing. I've tried to import a working XP image - same thing, i've tried installing win7 same thing ...
I am sure this is a bug but i don't seem to find anybody else with this problem therefore .... i would appreciate some help on this one ...

mitch

Mitch,

Tell us a little about the machine,
Host memory, guest settings, Etc...
What did you upgrade from?
32 or 64 bit host?

OK here's the whole story - i had Fedora 10 and VirtualBox - all running smoothly Win XP guest. I decided to installl Feroda 11 and oufcourse after that installed Virtualbox - imported my Win XP guest and everything worked OK for about 2 weeks. Some day the upgrade icon came up and i clicked to update - i saw that VBox is going to be upgraded to including my kernel and a bunch of stuff. After the upgrade my WinXP guest does not work any more - like i said before it crashes just before it would display the desktop. i decided to delete the WinXP and import it from backup - the import went OK but the same problem appeared. The next thing i did was a whole new install of Win7 as a guest - install went OK but after reboot BSOD appears again. I decided to downgrade Vbox to 3.0.0 but that didn't help either. The next thing was to try Vbox 3.0.2 on a fresh Ubuntu 8.0.4 install - tried to import the same XP image and BSOD is here again - i didn't try to fresh install Win7 on Ubuntu Host but i don't think it will help...
U asked about my memory on the host... my host is HP 8510p with 4GB memory. and everything is 32 bit - host and guest...

btw linux RHEL guest works without any problem...

thanks in advance

Look in the guest settings and make sure the VT-x/AMD-v is unchecked and well as IO APIC.
You may need to leave the IO APIC on for the Windows guest to boot , but try without first.

i've tried that too - unchecked everything from USB, network, VT***, IOAPIC, ....
will try again thou and write the outcome ...

thanks 4 help

Switch the virtual network adapter to the IntelPro/1000 T server and see if it windows will get happy again.

incredible ... i am on Ubuntu 8.04 host right now ... it is true that i've tried to check and uncheck all sorts of functions on feroda 11 and it didn't work/help ...
i've unchecked the boxes u mentioned on ubuntu and it seems to work - done a couple of restarts and works well ...

thank you very much and hope that the my problem is truly resolved (not to appear again sometime)
have fun,

Mitch

I've tested it out...

Host: Ubuntu 8.0.4 fully updated
Running VirtualBox 3.0.2 r49928 and Win XP sp3 guest

When in the Settings -> System -> Motherboard -> Enable IO APIC is checked the Win crashes .. BSOD
...but it goes like this ...
with the IO APIC enabled: ...when i import the guest the first boot is ok... when i restart it, it doesn't boot anymore..it crashes
if i then stop the guest, uncheck the mentioned box and start it, the guest still doesn't boot..
after deleting and importing the guest one more time and unchecking the box the guest works OK ... several restarts.

The reason for this is Version 3.0.X has SMP capabilities and if you have IO APIC Windows tries to install the SMP kernel.
Leave the IO APIC off and you should be alright.