2008/12/17 Michael H. Warfield <span dir="ltr"><<a href="mailto:mhw@wittsend.com">mhw@wittsend.com</a>></span><br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
:<br>
<div class="Ih2E3d"><br>
On Wed, 2008-12-17 at 18:43 -0500, Marc Ferguson wrote:<br>
<br>
> Ok so, I'm in front of my computer now. I'm running<br>
> VirtualBox-2.0.6_39765_fedora9-1.x86_64. The error is:<br>
<br>
> A problem has been detected and windows has been shut down to prevent<br>
> damage to your computer.<br>
<br>
> I stopped typing and took a screen shot of the window. It's attached.<br>
<br>
</div> I'm working from memory here and I don't have any references at hand<br>
but I believe that there are some known problems with Windows and the<br>
ACPI drivers between the Intel and AMD versions that have shown up like<br>
his. By default, both drivers are loaded and, most of the time, it<br>
works. Under certain conditions, which seem to be aggravated by<br>
virtualization, however, the Intel driver (IIRC) running in an AMD<br>
environment bluescreens. I remember reading about this in one of the<br>
VirtualBox forums describing migration (which is not the case here).<br>
The updated version of VirtualBox may have triggered this. There are<br>
some pretty serious differences between the 1.x VirtualBox and the 2.x<br>
VirtualBox. You may have to go in and remove a bad driver. Search the<br>
virtual box forums for virtual machine migration and you may find<br>
something.<br>
<div class="Ih2E3d"><br>
> --<br>
> Marc F.<br>
> <a href="http://www.fergytech.com" target="_blank">www.fergytech.com</a><br>
><br>
> "When life gives me lemons... I make Linuxaide!"<br>
<br>
</div> Mike<br>
<font color="#888888">--<br>
Michael H. Warfield (AI4NB) | (770) 985-6132 | mhw@WittsEnd.com<br>
/\/\|=mhw=|\/\/ | (678) 463-0932 | <a href="http://www.wittsend.com/mhw/" target="_blank">http://www.wittsend.com/mhw/</a><br>
NIC whois: MHW9 | An optimist believes we live in the best of all<br>
PGP Key: 0xDF1DD471 | possible worlds. A pessimist is sure of it!<br>
<br>
</font><br>_______________________________________________<br>
Ale mailing list<br>
<a href="mailto:Ale@ale.org">Ale@ale.org</a><br>
<a href="http://mail.ale.org/mailman/listinfo/ale" target="_blank">http://mail.ale.org/mailman/listinfo/ale</a><br>
<br></blockquote></div><br>Well, I ended up doing a REPAIR on my WIndows client and I'm working on downloading/installing the service packs and getting it back to status quo. I wish I could spend more time and actually solve it, but the funny thing is the more I tried to solve the issue the more I got fed up with it. I thought to myself, "This is why I'm NOT on a windows system. Why should I even care to fix this in a virtual environment." And for that reason alone, that's why I love VirtualBox.<br>
<br>Thanks, everyone, for the suggestions. I'm making my snapshots at every major hurdle now and they are being saved on my other partition.<br clear="all"><br>-- <br>Marc F.<br><a href="http://www.fergytech.com">www.fergytech.com</a><br>
<br>"When life gives me lemons... I make Linuxaide!"<br>