a7t7d wrote:I'm getting the same issue with a non p2v XP (clean install inside Virtualbox) exported appliance.
a7t7d wrote:As I stated, all settings identical, default IDE controller
mpack wrote:That statement is ambiguous. Please confirm that you have checked, and that the IDE controller is the same before and after.
There really aren't too many options here. Either a disk corruption has occurred (easily tested by mounting the hdd in a different VM and running chkdsk on it), or something is different in the VM settings. How else does the imported VM "know" to crash?
The problem seems to be caused by the following file: intelppm.sys
*** STOP: 0x000000CE (0xF88B58F8,0x00000000,0xF88B58F8,0x00000000)
esproul wrote:Edit: a search for this error shows this ticket: http://www.virtualbox.org/ticket/420. I'll try the workaround it describes and post my result. It might be an important data point that I exported this guest from an AMD-based system and imported on an Intel-based one, so it may well be related to the processor model.
thomson wrote:Thank you all for your help but xok's posting 9/9/09 quoted below worked for me too, just deleting the intelppm.sys files, nothing else. Thank you esproul for putting me onto it.
2009-09-09 02:48:05 changed by xok ¶
This problem happened to me.
The fastest fix is to boot in Safe Mode + Networking (F8 at startup)
- Go to %Systemroot%\Inf\ and delete all OEM#.inf
- Search for intelppm.sys in the c:\windows\ (search for hidden directories and system files) - Delete the 3 results of intelppm.sys
- Reboot the Guest normally
Users browsing this forum: Bing [Bot] and 37 guests