KVM (RHV, OLVM, Proxmox VE) • Re: [PVE] Vmware VM recovery leaves it unbootable due to virtual HW being replaced

Hi,

I noticed this to. Veeam creates the VM with the virtIO SCSI controller instead of the SATA controller. I'm not sure if VMWare paravirtual will work, since we uninstall vmware tools before the migration. Anyhow, it's a bit of work to get the VM to boot after migration. You have to detach the virtual disk, re-attach it as SATA. Add a smaal 1GB virtual disk as VirtIO SCSI, so that after installing the virtio tools the controller drivers are installed and Windows is able to boot from it. Boot the VM, install virtio tools, shutdow the vm. Detach the SATA disks and re-attach them using the virtio SCSI controller. I also changed the CPU to x86-64-v2-AES, while Veeam sets it to a processor with less capabilities.

I opened a support call for this issue, case #07690336 and the support engineer created a feature request for this, but it seems to be a known issue.

Statistics: Posted by FrancWest — May 07, 2025 2:38 pm

---