VM with disk migrated from KVM instance not booting on PVE

arielzn

New Member
Sep 29, 2021
1
0
1
34
We are migrating from a former libvirt/KVM setup to Proxmox.
I did the procedure of converting the OS disk images from qcow to raw, I then create the VM on Proxmox and attach the converted OS disk.
This went all fine for several VMs, but one of them is failing to boot.

After finding correctly the initrd image in /boot and start booting from it, it gets stuck on:

Code:
...

[    1.434759] sd 2:0:0:0: [sda] 1010827264 512-byte logical blocks (518 GB/482 GiB)
[    1.436474] sd 2:0:0:0: [sda] Write Protect is off
[    1.437645] sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn't support DPO or FUA
[    1.441196]  sda: sda1 sda14 sda15
[    1.442864] sd 2:0:0:0: [sda] Attached SCSI disk

it just stays there forever. I can't get an initramfs shell .

The only "weirdness" this image has respect to the ones migrated fine, is a partition layout with a UEFI one:


Code:
sda     254:0    0   482G  0 disk 
├─sda1  254:1    0 481.9G  0 part /
├─sda14 254:14   0     3M  0 part 
└─sda15 254:15   0   124M  0 part /boot/efi

The others are just a single sda1 with all / there.

I tried also to change the Bios to OVMF for this VM, it will find correctly the efi partition, then the intird and start booting and it gets stuck at the exact same place.

Any ideas how I could modify the image to get it correctly booting on PVE ?
 
Last edited:

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!