Virtualbox - Windows boots to plain blue screen
 

Hello, I had a dell amd turion laptop running ubuntu 10.04. I run windows xp via virtualbox.

I switched over to a toshiba intel core duo laptop and put ubuntu 10.04 on it. I am not able to get my virtualbox windows xp install to load all the way.

I get the windows starting screen, so it looks like it's booting. It then goes to a plain blue screen and just sits there. No disk activity or anything.

Any ideas on what the heck is going on?
-Thanks

Check under the settings of your xp, make sure Enable IO APIC is enabled.

Also if any error messages are displayed please list them.

I think that this is called the Blue Screen Of Death (BSOD). It's a "windows thing".

You could ask that nice Mr. Bill Gates about this, but he seems to have skipped off into the sunset (with the money).

Maybe you should ask that this post be moved to "LQ - General", where it will have better exposure to people who can help you: Just click "Report" and ask. The mods will do their thing :)

Best wishes.

Also you may need to enable virtualization in you BIoS and in your VBox settings, check under "System", "Acceleration" make sure you have both virtualization options checked.

HTH

Forrest

p.s. if it were to be moved anywhere, Linux - Virtualization would probably be much better than General.

@ {BBI}Nexus{BBI}

OK, i did this, nothing changed. No errors or anything.


@ tredegar

Definetly not a blue screen of death as the same virtualbox hard drive image file works great on the other dell laptop that i am replacing. The blue screen is the same as the default blue that microsoft uses as a background color...not the bright blue used in the blue screen of death.


@ forrestt

I misstated, i'm actually running kubuntu 10.04, so there is no system, acceleration. The cpu is a T2080 and i don't know if it had hardware virtualization or not.


Any other ideas? Thanks for all the help.

It might be a long shot... then again, might not be...

I had something similar happening to me some time ago, couldn't figure it out. The issue was actually very simple...

Turned out that the XP start procedure had popped up a dialog (modal) message box - but VirtualBox didn't, so it was behind the XP boot-up blue screen.
(I don't remember what message it was, one of those with the 'click here not to see this message again' type things... might have been something relating to screen resolution...)

I found it by chance by using the change-window key shortcut, ie. Alt+TAB (might have been the change application-shortcut, ie. Ctrl+TAB, so try them both).

Cheers!
CJ

OK, i disabled compiz and its definetly a bsod issue. processor.sys error.

This sucks and you gotta love windows. I'm just going to reinstall as that will fix this issue.

-Thanks

When I said system acceleration, I meant inside the virtual box GUI.

Forrest

@ Forrestt

Where do you see system? I see "Machine Devices Help" up at the top. No system or acceleration in any of those menus.

Anyhow, I was thinking, why is this a Windows issue. It's really a VB issue i would think...since isn't one of the points of a virtual windows install that it be portable? Oh well, I just did a reinstall.

When you go to the settings for the VM you are trying to edit.

How is this a VB issue? It was winblows complaining about an invalid sys file. VB merely provides an environment that fools the op/sys into thinking it is running on real hardware. I would think it was the switch from one processor (AMD) to the other (Intel) that was the problem. Even when winblows is installed on real hardware, you can't just take that install, insert it into another machine without encountering issues because, some of the hardware winblows had registered previously has now changed. To have better portability you should consider exporting your VM (Virtual Machine/s) instead.