Comment 26 for bug 1810972

My workaround is to build “Compose” the KVM Guest using Virt-Manager AND, using UEFI!!!

To do that, I have to run on each KVM Host (Pod):

sudo apt install ovmf

Then, compose the KVM Guests using “Firmware = UEFI”, instead of “BIOS”.

Voialá! Problem solved!

No more kernel panic and MaaS can take over the VM after a simple “Pod Refresh”!

It’s even better now! I mean, when deleting a Pod, even accidentally, ALL the VMs will be left untouched! I really like this. So, no more Composing KVM Guests via MaaS UI for me (for now).

More details here:

https://discourse.maas.io/t/maas-2-5-bionic-pod-composing-guests-kernel-panic-no-init/302