Migrating Windows 2000 VM from VMware 5 to Proxmox 6.3.3

[jasonberenson]

Greetings,

I followed the Proxmox guide on migrating a Windows 2000 VM from VMware to Proxmox. I was able to pull over the vmdk's, mf and ovf files. Then I did:

qm importovf 200 test.ovf rpool-SSD

It seems to create a VM with the correct disk. It starts to boot and once it passes the following screenshot, it fails with inaccessible disk.

Here's the .conf file the import created:

boot: order=ide0;ide2
cores: 2
ide0: rpool-SSD:vm-200-disk-0
ide1: rpool-SSD:vm-200-disk-1
memory: 4096
name: test
smbios1: uuid=667ac4bf-034f-4bdd-89c7-b8d6384f8481
vmgenid: 914d8b4a-1019-4662-beb6-be209a4159cb

As per the guide, I changed 'scsi' to 'ide'. I'm pretty sure it's still trying to use SCSI and because there are no virt-io SCSI drivers on the VM, it won't be able to see the disk.

Any pointers are much appreciated.

(Side note: yes, I'm aware win2k is old. This is a customer requirement)

 

[depe3153]

hiii there, do you already set your BIOS to UEFI after running qm inport??

 

[t.lamprecht]

hiii there, do you already set your BIOS to UEFI after running qm inport??

I do not think Windows 2000 supports UEFI, some Itanium-CPU variants did support a predecessor of UEFI, but for i386/x64 general UEFI support was first available in Windows Vista.

boot: order=ide0;ide2

There's a non-existent device (ide2) mentioned in your boot order config.

Also, the OS type setting is missing from the config, set it to Windows 2000, e.g., in the web-interface's VM Options, that should improve the selection of virtual devices for this VM.

 

[depe3153]

I do not think Windows 2000 supports UEFI, some Itanium-CPU variants did support a predecessor of UEFI, but for i386/x64 general UEFI support was first available in Windows Vista.

oooo yes your right, i test it and can not booting if i change to UEFI.

 

[jasonberenson]

@depe3153 - I tried both SeaBIOS and UEFI

@t.lamprecht - I've tried many different variations. Here's the latest .conf:

boot: c
bootdisk: ide0
cores: 2
ide0: rpool-SSD:vm-200-disk-0,size=45340M
memory: 4096
name: test
net0: virtio=F2:23:AE:35:28:A8,bridge=vmbr0,firewall=1
numa: 0
ostype: w2k
scsihw: virtio-scsi-pci
smbios1: uuid=27d17e71-e618-4018-b612-088309a1d5ac
sockets: 1
vmgenid: 163a2c57-b3c2-40a6-a379-04e145e075e0

I've tried importing the VM with:

qm importovf 200 /tmp/test-vm/acctng.ovf rpool-SSD

I've also tried creating the VM structure manually and importing the disk with:

qm importdisk 200 /tmp/test-vm/acctng-disk1.qcow2 rpool-SSD

I did the above disk import with the original vmdk and then also converted that vmdk to qcow2 and tried with that.

No luck on any of them. As you can see in the images, it starts to boot Windows, and then gives a blue screen complaining about the drive. I'm pretty sure this is a driver issue, but I'm not sure how to resolve it.

I have a bunch of Win2008 VMs I need to test with as well.

 

[jasonberenson]

One small update:

I imported a Windows 2008 Server VM using:

qm importovf 201 COUTURE.ovf rpool-SSD

Booting with the default settings didn't work. I had to detach the disk, change it to IDE, re-attach and it booted.

I believe I can create a small disk with SCSI, then install the drivers and Qemu agent on the VM and then switch the main disk to SCSI.

I'm still stuck on the Win2k VM though.

 

[depe3153]

hi there.
i was able to load my vmdk in my test machine. i load the SCSI driver to the 2000 server first recreate the vmdk file and convert to qcow.
i follow this guidance link. i hope it will be your solution

 

[jasonberenson]

Looks like I just needed to run MergeIDE.bat from here:

https://www.vmwaremine.com/2016/11/30/migrate-windows-2000-server-to-nutanix-ahv/
https://www.virtualbox.org/attachment/wiki/Migrate_Windows/MergeIDE.zip

Ran that, exported the VM once more, imported and it booted just fine.