Migration from VMware

Jul 20, 2026
9
2
3
Hi.
I'm in a bit of a pickle.
My Proxmox experience is not the highest. But i have many years in VMware, Hyper-V, TrueNAS and some in Nutanix.

I have a VMware server (Standalone) with some VM's, that i want to migrate to Proxmox (Standalone).
- I did a fresh install of Proxmox, created 2 ZFS'sm one with SAS and one with SATA drives.
- Applied license key (Community edition).
- Run updates on Proxmox.
- Connect the Proxmox to VMware using "Datacenter" "Storage" and added VMware ESXi connection.
- Proxmox and VMware is on the same subnet.
- The Servers that I'm migrating is a Windows Server 2016.
- Proxmox guest tools and drivers installed.

So now i have the VMware option on the Proxmox server (As I have done in other migrations).
I do the migation using the option in Proxmox, copy is OK.
Then i try to start the VM, it does the "Loading screen", until "Inaccessable Boot Device" and reboot.
Then i changed thru all the SCSI Controller options, and i found that the "MegaRaid" can boot just fine.
So I think "SUCCESS", boot the VM, set IP. But many services wound start.

The installation goes from running smooth, to buggy within 10-15 minuttes.
I get a log of NTFS and disk errors in the eventlog.
So I run a chkcsk, and reboot. But the chkdsk faila at 2%, I try skipping the check, and now the VM fails with "bad system config info".
I drop this migration, and i delete the VM.

I go to to the original VM on VMware, and do a full checkdisk, sfc, dism and so on. All is fine.
Check eventlogs, and things are all OK.

New migration, same result.

So i create a new VM only for testing, Windows Server 2019 (Not 2016, as the original machine).
And it has the same issues, I tried some of the same debugging.
I had a colleauge take a look at it, and we tried using some other debugging, and a lot of other steps, to many to write here.

So now I'm at a bit of a loss, and needs some input.



Proxmox: 9.2.3 (Fully updated).
VMware ESXi: 6.5.0 Update 1 (Build 5969303)
 
Try to downgrade to .266 or .271. .285 has a known bug. Try this first.

I forgot to say, use virtio single SCSI. But first you need to load the driver, otherwise you will have blue-screen.
 
Last edited:
Try to downgrade to .266 or .271. .285 has a known bug. Try this first.

I forgot to say, use virtio single SCSI. But first you need to load the driver, otherwise you will have blue-screen.
Hi again.
I removed the version of Virtio and installed the one you suggested. + i changed the SCSI controller to Virtio Single SCSI.
What i end up with, it a "Inaccessable boot device".
Then it boots in automatic repair mode.
 
I have licensed tools that normaly is used for baremetal recovery.
I will take a look at other such options, if i cant get this simple option working.
Starwind has a nice tools as well...
https://www.starwindsoftware.com/starwind-v2v-converter
I never used, but got friends that did it...
I rather use clonezilla or redorescue as I pointed out... Redorescue always work for me...
But, go ahead, and try others...

Best regards.
 
HI. I tried your fix now, and it seemed to revolve it! (+ changing the controller to VirtIO SCSI single".
It did a "Getting ready", reboot and now i have a screen
I will follow up tomorrow.
Great stuff, I will do a fistbump to the author!
 
  • Like
Reactions: Jens-Complea
Hi, my experience with VMware VM´s is first do a copy from the master image, from the copy move to Hyper-V temporal environment using StarWind (Freeware) when the VM is start up on Hyper-V, run MergeIDE file from Proxmox VE https://pve.proxmox.com/wiki/File:Mergeide.zip and migrate from Hyper-V now to Proxmox VE, start the VM with Bus IDE, install the VirtIO the newest available on the VM, shutdown and change the BUS to VirtIO SCSI the VM start again with the normal way, remember to change the Network to VirtIO Net from Intel E1000, 1000E or VMXNET3 and your are almost done. The last one is set ballon service to have dynamic RAM and use. I hope this info help you, let me know.