Moving VM from AMD laptop to Intel

[ve3id]

Hi,

I have moved VMs at different times in the past, usually when winchesters fail on me. I usually just copy the vdi and install it in a new machine on the new cpu. However, I am now migrating from an amd laptop to an intel one.

I can boot the windows XP virtual disk just fine in safe mode, so I know basic functionality is there. My apps then work and have access to the net. But when I try to boot normally it crashes with a hard stop and tells me to remove the last installed device. processr.sys is the last thing mentioned before doing a memory dump.

Can anybody suggest a recovery method? I have thought of trying to upgrade the VM to windows 7, but am afraid of losing all my installed applications.

I am running SuSE leap 42.1 on a lenovo T430 and Virtualbox 5.0.16_SUSE r105871

Thanks in advance for any help.

Nigel

[Perryg]

How to move guests created with => version 4.*

Make sure that the guest/s are truly shut down before moving ( not saved state )

Then if you have an issue post the guests log file ( as an attachment ) after it fails.

[mpack]

Moving bare VDIs is not the recommended way. See Howto: Move a VM.

Make sure that the VM is shut down, not in a saved state. That should ensure that the CPU change is not significant to VirtualBox - though it may still be significant to guest OS's and apps that require activation.

[ve3id]

Thanks for the replies above. I went back to the original machine, started up and shut down the VMs for both windows XP and 98, then transferred new copies of all the directories and files under ~Virtualbox to the new machine. I followed the directions given in the two posts above.

After this, both xp and 98 machines failed because of USB2.0 so I disabled that in the guest settings temporarily. Then XP crashed exactly as before but 98 booted fine.

But when I went to look for extensions and guest additions were only available for 5.0.20 and I had 5.0.16 so I downloaded the rpm for 5.0.20 and installed it. Only problem I see here is they do not have a build for leap 42.1 so I used the one for openSuSE 13.2 64 bit.

Both before and after installing the extension pack, I still get the same crash.

I have never had any problems like this before, been using Virtualbox for years. Any help will be really appreciated. I have attached the machine log.

Thanks
Nigel

[Perryg]

Code: Select all

00:00:00.627148 HM: HMR3Init: Falling back to raw-mode: VT-x is disabled in the BIOS for all CPU modes

I would enable hardware virtualization in the hosts BIOS and try again.

[ve3id]

Brilliant! That did it! I'll buy you a beer next time I am in town. I didn't see it amongst all the noise.

cheers,
Nigel