XP migrate failed to 1.1

[GarthK]

BTW, the version of VMWare server is 1.0.8. Hope that helps.

I had a VMWare Server XP vm already set up with a single, growable, IDE file. I followed the steps in the HowTo as follows:

1. Uninstall VMWare enhancements
2. Skip the vmware-vdiskmanager since the disk was already correct
3. Create a new KVM with similar physical characteristics
4. Qemu-img the vmdk file to a qcow2
5. Delete the original qcow2 file and replace with the converted one
6. Start the vm

Here's where it starts to go bad. What happens in the console window is a brief flash of the initial Windows XP logo followed by a blue screen of death that disappears in an instant. Then I am asked if I want to restart XP in a variety of diagnostic modes, all of which do the same thing. The process repeats indefinitely.

I logged the output but wasn't sure how to read it. So, I trashed the migrated vm and started a clean install of XP from an iso file as a test and that worked fine. However, I have a couple of 2k3 servers that I still would like to migrate.

Any help appreciated.

Thanx,
Garth

 

[tom]

BTW, the version of VMWare server is 1.0.8. Hope that helps.

I had a VMWare Server XP vm already set up with a single, growable, IDE file. I followed the steps in the HowTo as follows:

1. Uninstall VMWare enhancements
2. Skip the vmware-vdiskmanager since the disk was already correct
3. Create a new KVM with similar physical characteristics
4. Qemu-img the vmdk file to a qcow2
5. Delete the original qcow2 file and replace with the converted one
6. Start the vm

Here's where it starts to go bad. What happens in the console window is a brief flash of the initial Windows XP logo followed by a blue screen of death that disappears in an instant. Then I am asked if I want to restart XP in a variety of diagnostic modes, all of which do the same thing. The process repeats indefinitely.

I logged the output but wasn't sure how to read it. So, I trashed the migrated vm and started a clean install of XP from an iso file as a test and that worked fine. However, I have a couple of 2k3 servers that I still would like to migrate.

Any help appreciated.

Thanx,
Garth

Looks like you did not follow the howto.

see http://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE#Enable_IDE_in_the_registry

 

[GarthK]

So the registry hack for IDE is necessary even if the vm box is already configured for IDE?

Garth

 

[tom]

So the registry hack for IDE is necessary even if the vm box is already configured for IDE?

Garth

I am not sure, try it. I always did with this IDE registry without issues.

Also, please configure your winxp box that it does not reboot automatically - therefore you will see the BSOD reason.

 

[GarthK]

I'll give it a try as soon as I get home from work.

Thanx,
Garth

 

[GarthK]

Well, that fixed it. I applied the intelide.reg file, did the qemu-img command and brought it up just fine. The only thing that didn't work was switching to the virtio network driver. I had to switch back to the RTL NIC to get it to work.

Thanx,
Garth

 

[dignus]

Well, that fixed it. I applied the intelide.reg file, did the qemu-img command and brought it up just fine. The only thing that didn't work was switching to the virtio network driver. I had to switch back to the RTL NIC to get it to work.

Thanx,
Garth

Did you install the drivers for the virtio interface? http://pve.proxmox.com/wiki/Paravirtualized_Network_Drivers_for_Windows

 

[GarthK]

No, but now I'll go back and follow the rest of the HowTo since I can get past the step that calls for starting the box.

Thanx for the help,
Garth