Tuesday, 3 February 2026

VM Prep for conversion to PVE from VMWare

To make my life easier I have been working at automating the conversion process from VMWare virtual machines to Proxmox VE 9. The hardest part being of course having to load the VirtIO SCSI driver into Windows and having it recognise that at boot the first time it comes up in PVE.

To accomplish this there are two scripts I run. The first script that I made will:

- Save hardware inventory (CPU, RAM, Disks, IP) to C:\temp\notes.txt
- Uninstall VMware Tools (Registry & Chocolatey)
- Install QEMU Guest Agent & VirtIO Drivers from a specified network share
- Setup the VirtIO SCSI driver as a service within Windows set to autostart at boot

The second script that I downloaded from here attaches a fake drive to the machine while it is running using the VirtIO SCSI controller. This is the magic that makes it fully bootable immediately.

After the first boot check the notes.txt file and update the network adapter with a static IP if required, and if there are additional unmounted drives use that document to ensure you use the right drive letters when attaching them again.

The first script: https://github.com/proudcanadianeh/Powershell-Scripts/blob/master/Windows/VMWareToPVE.ps1
The second script: https://github.com/croit/load-virtio-scsi-on-boot/tree/main

When importing to Proxmox using the Import Guest feature, be sure to unselect the checkbox to Prepare for VirtIO SCSI, change the SCSI controller to VirtIO Single, and the network adapter to VirtIO Paravirtualized.

No comments:

Post a Comment

Proxmox Backup Server - Recover a ZFS Datastore that is 100% full

This has happened to me a couple times now where my ZFS pool has filled to 100% causing not only backups to fail, but also the ability to ru...