Migrate Windows Server 2019 VM on ESXI 6.7 to Proxmox

[Armando Ramos Roche]

Hello everyone,
I am trying to migrate the services that I currently have virtualized in ESXI 6.7 to proxmox. But it has been impossible for me.
I have tried all the routes that appear in https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE and I have managed to pass the hdd correctly towards proxmox.
But when I turn on the vm in proxmox it doesn't boot me out of the hdd.
Can somebody help me?

 

[aaron]

Did you set the BIOS type correctly? (BIOS / UEFI)
How did you define the disk? SATA / SCSI-virtio / Virtio-block...?

Windows does not come with virtio drivers out of the box so at first you need to set the disk to SATA or IDE. Once it´s booted attach the virtio driver cd iso and create a small temporary disk with the mode you want. Windows will detect a device it does not know and will ask for the driver.
Once the driver is installed you should be able to remove the temporary disk, change the type of the main disk, change the boot order in VMs options, and then shutdown and start the VM again.

 

[Armando Ramos Roche]

Did you set the BIOS type correctly? (BIOS / UEFI)
How did you define the disk? SATA / SCSI-virtio / Virtio-block...?

Windows does not come with virtio drivers out of the box so at first you need to set the disk to SATA or IDE. Once it´s booted attach the virtio driver cd iso and create a small temporary disk with the mode you want. Windows will detect a device it does not know and will ask for the driver.
Once the driver is installed you should be able to remove the temporary disk, change the type of the main disk, change the boot order in VMs options, and then shutdown and start the VM again.

Thanks for everything,
It turns out that I had to put the UEFI bios. When I did it worked.
But when I entered the server I was not in the domain and the name of the server had changed.

 

[aaron]

But when I entered the server I was not in the domain and the name of the server had changed.

Are you sure you migrated the right server? The server name should not change just because of the migration.

 

[FelHey]

Hello Everyone,
I'm desperate.

I’m trying to migrate a windows server 2016 VM from VMware ESXi 6.5 to Proxmox 6.4-13 and it looks impossible.

I follow the exact procedure of the proxmox wiki on that link https://pve.proxmox.com/wiki/Migration_of_servers_to_Proxmox_VE

Here is the last VM config that I tried it let me boot up, but the CPU goes 80% Ram 98% and when windows start-up I can view the desktop, but everything freezes.

I could start the VM and work a bit in windows safe mode, but all services are stopped. Please help… I’m very confused…

bios: uefi
boot: order=sata0
cores: 16
memory: 49152
name: Cameras
net0: e1000=32:BB:8C:C3:5C:0B,bridge=vmbr0,firewall=1,tag=4
sata0: local-zfs:vm-200-disk-0
sata1: Seagate8TB:vm-200-disk-0,size=2000G
smbios1: uuid=7e0be481-ec86-4556-a16b-508bee5bbf1e
sockets: 2
vmgenid: 33ec9b56-32de-48c5-a31d-c89afe4cced0

I have tried all the following vm config :

Error Windows trouble shooting
bios: uefi
boot: order=sata0
cores: 16
memory: 49152
name: Cameras
net0: e1000=32:BB:8C:C3:5C:0B,bridge=vmbr0,firewall=1,tag=4
sata0: local-zfs:vm-200-disk-0
sata1: Seagate8TB:vm-200-disk-0,size=2000G
smbios1: uuid=7e0be481-ec86-4556-a16b-508bee5bbf1e
sockets: 2
vmgenid: 33ec9b56-32de-48c5-a31d-c89afe4cced0
hotplug: disk,network,usb,memory,cpu
ostype: win10
numa: 1
---------------------------------------------------------------------------
Not bootable
bios: ovmf
boot: order=sata0
cores: 16
memory: 49152
name: Cameras
net0: e1000=32:BB:8C:C3:5C:0B,bridge=vmbr0,firewall=1,tag=4
sata0: local-zfs:vm-200-disk-0
sata1: Seagate8TB:vm-200-disk-0,size=2000G
smbios1: uuid=7e0be481-ec86-4556-a16b-508bee5bbf1e
sockets: 2
vmgenid: 33ec9b56-32de-48c5-a31d-c89afe4cced0
---------------------------------------------------------------------------
Freezed :
bios: uefi
boot: order=ide0
cores: 16
memory: 49152
name: Cameras
net0: e1000=32:BB:8C:C3:5C:0B,bridge=vmbr0,firewall=1,tag=4
ide0: local-zfs:vm-200-disk-0
ide1: Seagate8TB:vm-200-disk-0,size=2000G
smbios1: uuid=7e0be481-ec86-4556-a16b-508bee5bbf1e
sockets: 2
vmgenid: 33ec9b56-32de-48c5-a31d-c89afe4cced0
---------------------------------------------------------------------------
Work 1 hour and freeze black screen
bios: uefi
boot: order=sata0
cores: 16
memory: 49152
name: Cameras
net0: e1000=32:BB:8C:C3:5C:0B,bridge=vmbr0,firewall=1,tag=4
sata0: local-zfs:vm-200-disk-0
sata1: Seagate8TB:vm-200-disk-0,size=2000G
smbios1: uuid=7e0be481-ec86-4556-a16b-508bee5bbf1e
sockets: 2
vmgenid: 33ec9b56-32de-48c5-a31d-c89afe4cced0

 

[aaron]

Please don't necro bump a thread that is almost 2.5 years old and open a new one. Please also tell us then which procedure you used (there are several on that wiki page) and did you remove the VMware guest tools before?