kafisatz

How To migrate Gen2 Windows VM from Hyper-V

This assumes you have Windows Server 2022 Gen2 VM running on hyper-v that uses gen2 with UEFI and Secure Boot - it should work for win11 but i haven't tested that. This has only tested with a vanilla windows server 2022 VM so far (three times to write guide). I will comment this gist when i manage to move one of my domain controllers.

VM preparation

1. Dowload Virtio DVD and attach to running windows VM on Hyper-v
2. Log onto console of Windows VM to be migrated
3. Install VirtIO drivers (all drivers, this will also include spice tools)
4. Gracefully shutdown server
5. Export VM to CIFS location accessible by proxmox and mounted in proxmox

kafisatz

PROXMOX Setup Weirdness Observed

1. Most of the time gui setup didn't get dhcp address from my server, one time in 6 installs it did.
2. Sometimes gui setup populated an example IPv4 address, sometimes an actual IPv6 address and one time real DCHP IPv4 address
3. on one node in 6 installs it added a thunderbol0 entry to /etc/network/interaces resulting in what you see below, the fix was to remove from interfaces file

4. sometimes after setup the tunderbolt modules load and sometimes they don't - i don't know why, i currently have 1 machine with them specified in /etc/modules file and 2 machines without - i figured out this is (stupidly) by design, one machine in the cluster needs to manually have the the modules loaded (but this will cause other machines to load them on the fly) as such its best to define them on all nodes.

5. on node 3 i accidentally gave