virtualbox.org

Hi,

I'd like to build a VM of Windows XP embedded.

In order to keep it simple I have a flat vmdk harddisk image, where I copy the XP embedded to. I can boot this system. Unfortunately shortly after booting, right before the XP embedded initialization starts, I get a blue screen:

DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

The responsible driver differs, whether I include the "processor" component, "intel processor" component or "intel PIII processor" component: it's processr.sys, intelppm.sys or p3.sys, respectively.

Has anyone experience or a slight idea how I can prevent this BSOD?

BTW, I doubt that the XP embedded image is the culprit, because it works in VMWare server. However, I would prefer to use VirtualBox...

Thanks!

This driver has some bugs. We added a workaround for it before, but apparently that doesn't work with XP embedded.

Could you create a ticket on our bugtracker? Unfortunately there's no quick solution. I'm not sure if XP will work if you simply delete this driver.

Thank you for your reply!

sandervl wrote:Could you create a ticket on our bugtracker?

Done.

Best regards

Forgot that there's already one. (420) We'll discuss it there, ok?

There's a workaround documented here:
http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx

Configuration: host OS = Ubuntu 9.04 VirtualBox = 3.0.0 Guest OS= Windows XP SP2

I received the same symptom

1. Windows crashes during boot
2. The dump says
DRIVER_UNLOADED_WITHOUT_CANCELLING_PENDING_OPERATIONS

which is related to intelppm.sys

Tried to remove intelppm.sys, but didn't work.

Fixed by http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx

How can I do the registry key workaround when I can not boot the VM ?

is there a simple answer to this? How can the registry be edited on a virtual machine that BSODs before the desktop appears?

Neff wrote:How can the registry be edited on a virtual machine that BSODs before the desktop appears?

safe mode?!

hit [F8] key early when booting

Win 7 Embedded runs without any problems in a VM, and is much easier than XP embedded.

sandervl wrote:Forgot that there's already one. (420) We'll discuss it there, ok?

There's a workaround documented here:
http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx

so what happens if these keys are not in the registry?

You create them using regedit.

what is xp emberdded all about

Thats something you can enter in google.

Neff wrote:is there a simple answer to this? How can the registry be edited on a virtual machine that BSODs before the desktop appears?

Yes, there is. Boot up with the Windows installation disk, go into the recovery console, and type You can run listsvc first to see the list of all services and drivers. In my case, the BSOD mentioned the AMDK8.sys driver as the problem, so I ran listsvc, noticed that amdk8 was listed with a startup type of System, and ran disable amdk8. I quit out of the Recovery Console, rebooted, and Windows was happy.

In my case, the VM guest was a Windows Server 2003 machine, but I believe the same thing will work for XP. This is probably too late to help any of the previous posters, but maybe some people from the future will stumble across it and find it useful.

fixedwheel wrote:

Neff wrote:How can the registry be edited on a virtual machine that BSODs before the desktop appears?

safe mode?!

hit [F8] key early when booting

This works for me!