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.
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.
