Migrate from Hyper-V to Proxmox VE 9

H

Hammer72

New Member
Feb 4, 2026
5
0
1
Hi
First time here, hoping I am in the right place.

I have hit a hurdle trying to migrate a RHEL9 VM from Hyper-V 2019 to Proxmox VE9. Each time I attempt to start up the migrated VM I get errors that /dev/sda2 is missing.
I have run through the migration steps, but was wondering if there is a well hide secret to get this working.

Steps Taken Thus far:
Export VM on Hyper-V (Gen1 vm powered off, no checkpoints present)
Copy vhdx file to Proxmox to location /var/lib/vz/images
use command qemu-img convert -p -f vhdx -O raw Test1_hdisk0.vhdx Test1.raw to convert image
Create a VM shell with id of 512101
Import the raw disk image to new VM shell using command: qm importdisk 512101 Test1.raw VMstore. This Completes successfully
Log onto the PVE GUI select the Unused disk and edit the device
Change the boot order under VM_Name > options > Boot Order > Set scsi0 to first boot device
Start the VM, by default it gets an exception kernel error, reboot into maintenance mode to run the dracut -f command, this fails due to /dev/sda2 missing. Attempt to update the Grub with command grub2-mkconfig -o /boot/grub2/grub.cfg also gives error about /dev/sda2 missing
Edit the /etc/fstab and comment out my 2 file systems, /home and /var, on the sda2 logical device
System will now boot error free, but in reality I need these file systems to be present.

Any help or point in the right direction would be appreciated. If you have experienced anything similar would love to know how you resolved it.
Currently this is a POC to test a migration road map from Hyper-V to Proxmox, so would like to iron out any issues before attempting any real VM work loads.

Kind Regards.
 
Hi
Yes I have check with lsblk and see that both swap and root are on sda2 as well. See lsblk output below and /etc/fstab

lsblk
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 32G 0 disk
├─sda1 8:1 0 1G 0 part /boot
└─sda2 8:2 0 27G 0 part
├─rhel-root 253:0 0 15G 0 lvm /
└─rhel-swap 253:1 0 2G 0 lvm [SWAP]
sr0 11:0 1 1024M 0 rom

cat /etc/fstab

#
# /etc/fstab
# Created by anaconda on Wed May 21 10:26:17 2025
#
# Accessible filesystems, by reference, are maintained under '/dev/disk/'.
# See man pages fstab(5), findfs(8), mount(8) and/or blkid(8) for more info.
#
# After editing this file, run 'systemctl daemon-reload' to update systemd
# units generated from this file.
#
/dev/mapper/rhel-root / xfs defaults 0 0
UUID=01f26fe0-4b24-457a-82c2-5035c5c96469 /boot xfs defaults 0 0
#/dev/mapper/rhel-home /home xfs defaults 0 0
#/dev/mapper/rhel-var /var xfs defaults 0 0
/dev/mapper/rhel-swap none swap defaults 0 0

If I edit the fstab and remove the comment from /home, then try and mount /home I get the following error:
mount -a
mount: /home: special device /dev/mapper/rhel-home does not exist.

Check what is in /dev/mapper and all I see is root and swap.
I feel like I am doing something fundamentally wrong with the migration process.
 
Hammer72 said:
├─rhel-root 253:0 0 15G 0 lvm /
└─rhel-swap 253:1 0 2G 0 lvm [SWAP]
Click to expand...
Hammer72 said:
#/dev/mapper/rhel-home /home xfs defaults 0 0mand
Click to expand...
Hammer72 said:
mount: /home: special device /dev/mapper/rhel-home does not exist.
Click to expand...
There is, indeed, no rhel-home as seen in your lsblk output. Is it possible there was another disk that you did not transfer?
Also, please use "CODE" </> tags to surround your configuration/command output

Blockbridge : Ultra low latency all-NVME shared storage for Proxmox - https://www.blockbridge.com/proxmox
 
Hey Hammer72,

I saw your post about the migration hurdles from Hyper-V to Proxmox—sounds frustrating, especially with those disk and boot issues. I've been through similar VM moves myself, and one tool that helped me a lot was Vinchin Backup & Recovery. It handles conversions and migrations pretty smoothly, including from Hyper-V to Proxmox, without as many manual tweaks.

If you're open to trying it, it might simplify the process for you. No pressure, just sharing what worked in my experience. Let me know if you have questions!

Best,
Pierre Martin
 
Hi
I decided to bring the test VM back online on the Hyper-V to verify the number of disks. From the below we can see there is only the one disk allocated.
<lsblk>
NAME MAJ:MIN RM SIZE RO TYPE MOUNTPOINTS
sda 8:0 0 32G 0 disk
├─sda1 8:1 0 1G 0 part /boot
└─sda2 8:2 0 27G 0 part
├─rhel-root 253:0 0 15G 0 lvm /
├─rhel-swap 253:1 0 2G 0 lvm [SWAP]
├─rhel-var 253:2 0 5G 0 lvm /var
└─rhel-home 253:3 0 5G 0 lvm /home
sr0 11:0 1 1024M 0 rom

To answers the question about multiple disks, only one disk assigned.
 
Pierre Martin said:
Hey Hammer72,

I saw your post about the migration hurdles from Hyper-V to Proxmox—sounds frustrating, especially with those disk and boot issues. I've been through similar VM moves myself, and one tool that helped me a lot was Vinchin Backup & Recovery. It handles conversions and migrations pretty smoothly, including from Hyper-V to Proxmox, without as many manual tweaks.

If you're open to trying it, it might simplify the process for you. No pressure, just sharing what worked in my experience. Let me know if you have questions!

Best,
Pierre Martin
Click to expand...
Thanks Pierre
I will give this a looking, see if this works for me as well. Fingers crossed.
 
You must log in or register to reply here.
Top Bottom
Back