Thanks for the advice @sdeziel. I don’t think I’m qualified to report such a bug tough I’m just trying to help debug a microk8s/dqlite issue, and my microk8s nodes happen to be on ubuntu:22.04 lxd images which have the -kvm kernel by default, and I fell into that rabbit hole.
I’m still trying to obtain a perf report on that vm. So I tried installing linux-virtual on the VM, updated the grub config, but it does not boot with the following error:
[ 1.002064] VFS: Cannot open root device "PARTUUID=72954768-850e-45d3-a9ca-d064a700c8b5" or unknown-block(0,0): error -6
[ 1.003779] Please append a correct "root=" boot option; here are the available partitions:
[ 1.005180] Kernel panic - not syncing: VFS: Unable to mount root fs on unknown-block(0,0)
Is there anything special to do to boot a generic kernel in a LXD virtual machine?
Nothing special needs to be done to boot that -virtual kernel, as long as the grub config is good, it should work. As a workaround, I’d try using root=/dev/sda2 as that is usually where the rootfs is on normal LXD VMs.
Still no luck. The -generic kernel does not detect any disk, apparently.
The grub config was generated by apt install linux-generic and nothing special stands out compared to the -kvm entries.
Oh, the ubuntu: remote uses images I’m not used to. Their rootfs is at /dev/sda1 with cloudinit-rootfs LABEL. Anyway, here’s what I did to get the VM booting the -virtual/-generic kernel: