Display issues with a vm being moved from Fusion to VB

[56Nine]

We have a recent WInXP vm that was on Fusion that was recently moved to Fusion 4.3 using these instructions (blog.tcs.de/convert-vmware-fusion-to-virtual-box-on-mac-os-x-mountain-lion/). As the machine starts up this message appears and does not allow the VM to continue: "The virtual machine window is optimized to work in 32-bit color but the virtual display is currently set to 0-bit" I've seen other similar references online to report fixing this with guest additions, but he machine will not start up, and I've not seen any reference to the 0-bit feedback I'm getting

I would appreciate any information/insight that could be provided and possibly point me in a direction.

Thank you,

Darwin

[mpack]

That message is just a warning, it will not stop the VM from continuing. To fix it remove the VMWare tools from inside the guest (those are only compatible with VMWare), and install the VirtualBox Guest Additions. Boot up in safe mode if you have to to get rid of the VMWare stuff.

[56Nine]

Unfortunately the VM would not boot, the onscreen msg said the OS will not load. And it just stops.

Not sure what happened with this, we just purchased the the latest version of fusion and got it up and running....so much for moving this VM now.

Oh well.

[mpack]

You are no more likely to be able to move a PC image between different virtual platforms than between physical platforms. VM platforms don't all emulate identical hardware, even assuming you considered that when creating the VM recipe. If you treat it as a migration problem then it's no harder than any other migration.

p.s. If you want me to consider the error messages you are seeing then you need to say what they are.