virtualbox.org

VB: 3.0.4 Host: XP pro sp3 Guest XP Home Sp2

Hi!
I installed VBox 3.0.4 on a XP pro sp3, and added a XP home sp2 as a guest. Works fine.
Then I exported the XP guest and imported that appliance again as a second guest.
That new guest boots up OK, but crashes at shutdown. Then it tries to reboot but crashes at boot, tries to reboot, and crashes...over and over.
I have to close it manually. The next time i reboot it it gets into this "crash and reboot" loop.
What is the problem?
The "first" guest works fine.
But I find it impossible to "clone" it.
HELP!

Look closely at the difference in the guest settings.
Make the clone setting to match the original and try again.

Thank you for trying to help me!
I'm not sure exactly what you mean.
If I export an "appliance", doesnt that mean that the guest OS is copied?
And I should be able to import it as a new guest OS?
Maybe I have missed something?

When you export a VM ( I am assuming that is what you mean by appliance) and then you import it, it is the full working OS of the original VM.
There are some areas that can not be exported at this time and that is why I am telling you to look at the settings and make sure that the original and the imported one say the same thing. Only change setting on the second one to match the first one.

Checking...

The only difference that I can see is the harddrive settings:

Working machine:

WinXP.vdi (Normal, 30,00 GB)


Not working machine:

928280fd-974b-477f-9b61-a76aaafc876c}_4.vmdk

What should I do with this??

Try disabling the sound and the USB support and see if it works. If it works then turn them on one at a time to see which one is causing the problem.

I tried to disable sound and USB as suggested. No improvement.

I finally managed to pause the machine exactly when the "blue screen of death" occurs at the boot sequence.
The following file is reported to be the cause of the problem:

intelppm.sys

DRIVER_UNLOADED_WITHOUNT_CANCELLING_PENDING_OPERATIONS

*** STOP: 0x000000CE (0xF796C7F8,0x00000000,0xF796C7F8,0x00000000)

intelppm.sys
...

Read this ticket. It has some information in it that should help. http://www.virtualbox.org/ticket/420

It works!

I changed the guests registry setting as Virtual PC Guy explains on
http://blogs.msdn.com/virtual_pc_guy/ar ... 84461.aspx

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Processor
(didn't exist on my VM)

Or
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Intelppm

And changing the 'Start' value to '4'.

The first VM does not have any of these registry settings, so i guess that the new copy of the VM created them at its first crash.
Virtal Guy says that this may occur when VM:s are moved to another processor.
But why did this one crash? The Host is on the same OS.

Next test: Export THIS VM and import it to a new VM...

Yepp!

This VM can be exported and imported to the same host and it works like a charm!

Now i can have a "template" OS with all my basic apps to start clean with.
Or just an empty OS to test apps with.

Note that this problem is a windows problem, FreeDos and Ubuntu was no problem to clone.

Thanks for the support!