Exported/Imported Windows XP Appliance Not Working

Discussions about using Windows guests in VirtualBox.
Post Reply
DevotedDad
Posts: 3
Joined: 3. Dec 2009, 06:12
Primary OS: Mac OS X Leopard
VBox Version: OSE other
Guest OSses: Windows

Exported/Imported Windows XP Appliance Not Working

Post by DevotedDad »

Hello,

Running VirtualBox 3.1.2 on Mac (10.6.2) host. I have a Windows XP Pro SP3 guest that's running fine under the Mac host ... I've exported this guest as an appliance, then imported it into VirtualBox 3.1.2 host running on Windows XP Pro. The import goes fine, no issues ... however each time the guest is started it gets to the login screen and simply reboots. I've examined the settings - they're all the same as they are on the Mac host. The Windows XP host has plenty of memory, ample hard drive space, etc.

Anyone have any ideas what might be causing this situation?

Thank you.
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Exported/Imported Windows XP Appliance Not Working

Post by Perryg »

I would look closely at the original settings. They need to match exactly.
Some settings are not included in the export.
DevotedDad
Posts: 3
Joined: 3. Dec 2009, 06:12
Primary OS: Mac OS X Leopard
VBox Version: OSE other
Guest OSses: Windows

Re: Exported/Imported Windows XP Appliance Not Working

Post by DevotedDad »

There are a couple of differences upon a closer look ... for example, IO APCI is disabled on the original system and enabled on the import (would this cause the issue?) ... the other is the amount of video memory, slightly less on the imported version.

Thoughts?

Thank you!
Perryg
Site Moderator
Posts: 34369
Joined: 6. Sep 2008, 22:55
Primary OS: Linux other
VBox Version: OSE self-compiled
Guest OSses: *NIX

Re: Exported/Imported Windows XP Appliance Not Working

Post by Perryg »

IO APIC is needed for VT-x/AMD-v so yes it would effect it. Especially if the machine you moved it to does not support hardware-v in the bios and the original did.
If it tried to boot in that case you would be caught in an endless loop of booting.
Try with it off and see if you can at least get it to boot in safe mode (press F8 at boot time). Then windows should see everything and fix itself. (hopefully)
Post Reply