I am putting this here in case it helps anybody (including me someday). This information is somewhere in the import wizard announcement thread (https://forum.proxmox.com/threads/n...ng-vmware-esxi-based-virtual-machines.144023/) but it takes some sifting... this way is with nice pictures.
For me Ubuntu 22 and Windows 2022 import from ESXi 6.5 and the wizard is flawless. (For the Windows 2022 it warned me about bios things that might not work (etc) but they did. I don't think Windows noticed that it got moved.)
Windows 2012 and 2016 take a little extra (I have tested this on ESXi 6.5 and ESXi 6.7U3, using Proxmox 8.2).
When I use the import wizard with Windows 2012r2, the wizard identifies the VM as Linux, which should be changed with the pulldowns:
The "Advanced" tab has this:
Which much be changed to this (the checkbox is checkable once VirtIO SCSI single is selected, so long as the OS Type is set to Microsoft Windows) this will change the disk listed above from scsi0 to sata0:
And typically the CD/ROM ide0 should be unchecked (that can't be migrated):
After that the import is perfect (Windows does not ask for drivers and nothing unusual seems to be jumping out from the event log).
The OS is detected by the wizard properly for Windows 2016 but it still needs the VirtIO-SCSI change.
Leaving the disk set to LSI 53C895A on either import ends the box up here:
(and for the record I am not using EFI on the ESXi originals, which seems to be a whole different can of beans):
RJD
For me Ubuntu 22 and Windows 2022 import from ESXi 6.5 and the wizard is flawless. (For the Windows 2022 it warned me about bios things that might not work (etc) but they did. I don't think Windows noticed that it got moved.)
Windows 2012 and 2016 take a little extra (I have tested this on ESXi 6.5 and ESXi 6.7U3, using Proxmox 8.2).
When I use the import wizard with Windows 2012r2, the wizard identifies the VM as Linux, which should be changed with the pulldowns:
The "Advanced" tab has this:
Which much be changed to this (the checkbox is checkable once VirtIO SCSI single is selected, so long as the OS Type is set to Microsoft Windows) this will change the disk listed above from scsi0 to sata0:
And typically the CD/ROM ide0 should be unchecked (that can't be migrated):
After that the import is perfect (Windows does not ask for drivers and nothing unusual seems to be jumping out from the event log).
The OS is detected by the wizard properly for Windows 2016 but it still needs the VirtIO-SCSI change.
Leaving the disk set to LSI 53C895A on either import ends the box up here:
(and for the record I am not using EFI on the ESXi originals, which seems to be a whole different can of beans):
RJD
