Migrating OpenWrt from Hyper-V to Proxmox VE: A Step-by-Step Guide with Performance Benchmarking

📝 Motivation for Migration
The reason for the migration is that my bypass gateway, which used OpenWRT, was originally deployed in the Hyper-V of my daily-use PC. Since I’ve purchased a new N4100 industrial PC with four 2.5G Ethernet ports, this setup now allows me to achieve a full-house 2.5G network, significantly improving internal network transmission speeds. Additionally, it enables me to separate the software router (along with associated bypass gateways, secondary routers, DNS servers, and other components) from my daily-use PC, reducing network fluctuations caused by issues with my computer. This allows my daily-use PC to focus on work and using Moonlight + Sunshine for streaming Steam games. Moreover, after the migration, my daily-use PC can be put into sleep mode or shut down to save on electricity costs (well, not really). Another advantage is the separation of software router data and system data, allowing me to store backup data for PVE on an SMB-mounted disk, minimizing the workload and losses in case of an "All in Boom" scenario.
▌ Key Benefits Observed:
Network Separation: Dedicated N4100 mini-PC replaces gaming PC hosting OpenWRT
2.5Gbps LAN Upgrade: 4×2.5G ports enable full-home high-speed transfers
Energy Efficiency: Reduce idle power consumption by 62W (24×7 operation)
Disaster Recovery: Store PVE backups on SMB shares (non-host storage)
📝 Migration Procedure
Export Hyper-V Virtual Machine

notion image
In Hyper-V Manager:
In Hyper-V Manager, select the virtual machine you wish to export—let's take OpenWRT as an example. Right-click on it, choose Export, and then select the destination location to save the exported files.
Store in accessible location (minimum 2× disk space required)
Locate VHDX disk:
After exporting, the folder will include the following subfolders: Snapshots, Virtual Hard Disks, and Virtual Machines. The VHDX disk file for the OpenWRT virtual machine is located within the Virtual Hard Disks folder. For example, my ImmortalWrt VHDX file is named immortalwrt-23.05.3-x86-64-generic-squashfs-combined-efi.vhdx. To simplify future conversion and import operations, you can rename the file to something shorter, such as openwrt.vhdx. This will reduce the amount of typing required when entering commands and minimize the risk of import errors due to incorrect file names.
Exported Folder Structure:
├── Snapshots
├── Virtual Hard Disks
│ └── immortalwrt-23.05.3-x86-64-generic-squashfs-combined-efi.vhdx (rename to openwrt.vhdx)
└── Virtual Machines
Plain text
Pro Tip: Shorten filename to avoid path errors in CLI commands

More：https://en.deeprouter.org/article/migrate-openwrt-hyperv-to-proxmox-guide