Hi Everyone,
I'm trying to figure out what went differently between a couple VM migrations from Vmware to these two Proxmox PVE servers. I have two PowerEdge R510's that I'm using for what I'm calling transfer stations. These transfer stations are supposed to thin provision these VMDKs to Qcow2 on massive hard drive servers, I should be able to put most of the VM's on these two R510's. Then I might compress them down with ZSTD to another server for long term storage.
So I have already migrated all of the VM's from one VMware server to a Proxmox server. All of them are working fine, and employees are fine with them. I then start round 2 of migration to the transfer servers where their old VM's will stay in a pristine state and easily turned on. Proxmox Transfer Station 1 received one VM and I put several onto Proxmox Transfer Station 2. All VM's transferred using the built in VM migration tool, all moved as Qcow2, all migrated to 20TB datastores, and both datastores configured as directories with EXT4, not as ZFS or LVM. The PVE Servers are identical as both were setup at the same time, same models, same moments for updates and times for reboots.
The 2 differences I see is that Transfer Station 1 has a different vmware ESXI Host added, whereas Transfer Station 2 has another. The other is that Transfer Station 1 required me to turn off Virtualization in BIOS during the installation as it was oddly bugging out and not allowing me to install Proxmox. Once the installation worked I turned virtualization back on. Within VMware everything is thick provisioned and lazily zeroed. I just don't understand the end result of Transfer Station 1 is successfully running the VM as a thin provisioned disk and Transfer Station 2 is not.
I'm trying to figure out what went differently between a couple VM migrations from Vmware to these two Proxmox PVE servers. I have two PowerEdge R510's that I'm using for what I'm calling transfer stations. These transfer stations are supposed to thin provision these VMDKs to Qcow2 on massive hard drive servers, I should be able to put most of the VM's on these two R510's. Then I might compress them down with ZSTD to another server for long term storage.
So I have already migrated all of the VM's from one VMware server to a Proxmox server. All of them are working fine, and employees are fine with them. I then start round 2 of migration to the transfer servers where their old VM's will stay in a pristine state and easily turned on. Proxmox Transfer Station 1 received one VM and I put several onto Proxmox Transfer Station 2. All VM's transferred using the built in VM migration tool, all moved as Qcow2, all migrated to 20TB datastores, and both datastores configured as directories with EXT4, not as ZFS or LVM. The PVE Servers are identical as both were setup at the same time, same models, same moments for updates and times for reboots.
The 2 differences I see is that Transfer Station 1 has a different vmware ESXI Host added, whereas Transfer Station 2 has another. The other is that Transfer Station 1 required me to turn off Virtualization in BIOS during the installation as it was oddly bugging out and not allowing me to install Proxmox. Once the installation worked I turned virtualization back on. Within VMware everything is thick provisioned and lazily zeroed. I just don't understand the end result of Transfer Station 1 is successfully running the VM as a thin provisioned disk and Transfer Station 2 is not.
Last edited: