Server 2003 Blue Screen after P2V

[mwuz]

We are attempting to P2V a Windows 2003 x64 Server so we can back it up and archive it. I was unable to use VMware Converter or Starwind's converter so I made an image with Clonezilla, created a small vm, and restored the image with Clonezilla. This all went well but I can't boot into the new vm, it blue screens.

I found this KB: https://pve.proxmox.com/wiki/Windows_2003_guest_best_practices but I wonder if there is more I need to do.

1. Should I be installing the VirtIO drivers before imaging the old server?
2. Is it OK to configure a SCSI disk or should I be using IDE? (I P2V'd a 2008 server and after dropping the SCSI drive and adding it back as IDE I was able to login, that's why I'm asking).
3. Is the x86-64-v2-AES processor OK for a 2003 server?

I'd prefer to adjust my config and have things magically work however I think I might need to add the VirtIO drivers to the server and then reimage it.

What do I need to look at to get this machine

 

[mariol]

Please post your VM config of your Server 2003

qm config <vmid>

 

[mwuz]

@mariol thank you for replying! Here it is:

acpi: 1
bios: seabios
boot: order=ide0;scsi0
cores: 2
cpu: x86-64-v2-AES
ide0: none,media=cdrom
machine: pc-i440fx-8.1
memory: 4096
meta: creation-qemu=8.1.5,ctime=1726773558
name: svr-AD1
net0: e1000=00:50:56:a4:c5:dd,bridge=vmbr1
ostype: w2k3
scsi0: datastore_vm:vm-109-disk-0,size=150G
smbios1: uuid=422463c1-e1ba-1cca-07b7-538525aa431a
sockets: 1
vmgenid: 718dc34c-ee74-4f7f-bdf5-1269b02333de
~                                                                                                                                                           
~                                                                                                                                                           
~                                                                                                                                                           
~                                                                                                                                                           
~                                                                                                                                                           
"/etc/pve/qemu-server/109.conf" 16 lines, 397 bytes

I'll do this in the future instead of describing the config. Thanks for any help you can give.

MJ

 

[mariol]

Hello @mwuz

thanks for the config. What i can see is that you use SCSI type for your virtual disk already. You have to boot first with IDE and installed the driver pack [1]. For Windows Server 2003 VirtIO 0.1.113 works very well [2]

[1] https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows
[2] https://fedorapeople.org/groups/vir...ownloads/archive-virtio/virtio-win-0.1.113-1/

 

[jhr]

I have good experiences with virtio-win-0.1.96.iso, but @mariol is right, you have to start with IDE a then install drivers. I am using virtio virtio0: local-zfs:vm-106-disk-1,size=50Gvirtio1: local-zfs:vm-106-disk-2,size=476672M.
You can also install drivers on physical server before cloning, if it's possible.