Migrating a virtual machine from Hyper-V to Proxmox VE

[DEZERTIR]

Hello! After migrating and converting the virtual machine and starting it in hyperv , I noticed that the RAM settings aren't changing even after changing them through the graphical interface. gemu-agent is installed.

Please help.

 

[UdoB]

Please post English text (I see Cyrillic) - it increases the chance for a helpful reply ;-)

 

[DEZERTIR]

Please post English text (I see Cyrillic) - it increases the chance for a helpful reply ;-)

i change language

 

[gfngfn256]

After migrating and converting the virtual machine and starting it in hyperv

You probably mean migrated FROM Hyper-V & started in PVE.

You don't provide much info about your server (HW) & the VM you are trying to run.

You seem to have configured NUMA on, with 32 Processors on 2 sockets. While this may have been correct on the Hyper-V rig - this may not be the case with the PVE server.

I don't think 32 Processors with only 4GB ram seems correct.

 

[Pierre Martin]

Hey DEZERTIR,

I've migrated a few VMs from Hyper-V to Proxmox before and ran into pretty much the exact same issue—after conversion and boot, changing RAM via the GUI does nothing, even with qemu-agent installed. Reboots didn't help either.

I ended up switching approaches and used Vinchin Backup & Recovery for a full machine migration and format conversion. It worked perfectly first try; RAM, CPU, and disk settings all adjusted normally in Proxmox, and the agent was recognized right away. Saved me a ton of time fiddling with configs manually.

If you're still stuck on this, give their migration feature a shot— the interface is clean too. I can share the steps I used back then if you need.

Good luck, hope you sort it out soon!

 

[DEZERTIR]

Hey DEZERTIR,

I've migrated a few VMs from Hyper-V to Proxmox before and ran into pretty much the exact same issue—after conversion and boot, changing RAM via the GUI does nothing, even with qemu-agent installed. Reboots didn't help either.

I ended up switching approaches and used Vinchin Backup & Recovery for a full machine migration and format conversion. It worked perfectly first try; RAM, CPU, and disk settings all adjusted normally in Proxmox, and the agent was recognized right away. Saved me a ton of time fiddling with configs manually.

If you're still stuck on this, give their migration feature a shot— the interface is clean too. I can share the steps I used back then if you need.

Good luck, hope you sort it out soon!

Hi Martin, thanks for sharing your experience. I hope it helps.
Yes, it would be great if you shared your steps.