[SOLVED] Migrating a VMware Windows 2019 to Proxmox using Veeam

[Jaques]

Hi all!

I'm trying to migrate a VMware Windows 2019 VM using Veeam from ESX to Proxmox.

Prior to making my final Veeam backup I've installed the Virtio tools. Took a full backup then restored to the new Proxmox host.

During the restore process I selected he host within Veeam, along with RAW storage. The VM restores correctly, but when I start it Windows kicks up an ACCESSIBLE BOOT DEVICE error.

Thanks in advance!

 

[Jaques]

Wanted to add if I run this command after mounting the Virtio ISO I see the disks

>drvload vioscsi.inf

When I reboot and try listing disks from command prompt under Troubleshooting it doesn't see them.

Seems like the driver install isn't persistent.

 

[jiajie]

Detach the disk, try changing the disk to SATA mode to see if it can boot, and don’t forget to modify the boot order.

 

[SteveITS]

This might help:
https://pve.proxmox.com/wiki/Migrate_to_Proxmox_VE#Automatic_ESXi_Import:_Step_by_Step

And/or https://pve.proxmox.com/wiki/Paravirtualized_Block_Drivers_for_Windows

 

[gfngfn256]

>drvload vioscsi.inf

Yes AFAIK that only loads the driver - but doesn't install it to your Windows install.

I believe you need to use the dism command to actually install the drivers. See an example here through Windows Recovery.

 

[Jaques]

Thanks everyone, it worked!

What worked for me was detaching and remounting as a SATA disk. Creating a small 1GB drive as SCSI which let Windows install the drivers.

I'm going to test this method on another VM shortly: https://hull.au/blog/install-virtio-drivers-from-windows-recovery/

 

[Jaques]

I found this method https://hull.au/blog/install-virtio-drivers-from-windows-recovery/ ideal.

 

[gfngfn256]

Happy you got it working, maybe mark this thread as Solved.
At the top of the thread, choose the Edit thread button, then from the (no prefix) dropdown choose Solved.