Qemu-kvm-one: Error loading uncompressed kernel without PVH ELF Note Could not create domain from /var/lib/one//datastores/0/31/deployment.0

Community Support VM Configuration / Contextualization
1

Please, describe the problem here and provide additional information below (if applicable) …

On instantiating an ubuntu based VM using the opennebula supplied firecracker kernel, I get the following error:

Wed Mar 13 15:06:44 2024 [Z0][VMM][I]: Failed to execute virtualization driver operation: deploy.

Wed Mar 13 15:06:44 2024 [Z0][VMM][E]: DEPLOY: error: Failed to create domain from /var/lib/one//datastores/0/31/deployment.0 error: internal error: qemu unexpectedly closed the monitor: 2024-03-13T15:06:43.512284Z qemu-kvm-one: Error loading uncompressed kernel without PVH ELF Note Could not create domain from /var/lib/one//datastores/0/31/deployment.0 ExitCode: 255

Wed Mar 13 15:06:44 2024 [Z0][LCM][E]: deploy_failure_action, VM in a wrong state
Wed Mar 13 15:07:14 2024 [Z0][LCM][I]: VM running but monitor state is POWEROFF
Wed Mar 13 15:07:14 2024 [Z0][VM][I]: New LCM state is SHUTDOWN_POWEROFF
Wed Mar 13 15:07:14 2024 [Z0][VM][I]: New state is POWEROFF
Wed Mar 13 15:07:14 2024 [Z0][VM][I]: New LCM state is LCM_INIT

Versions of the related components and OS (frontend, hypervisors, VMs):

Kernel: Kernel 5.4 x86_64 - Firecracker
Disk: ubuntu 22.04 image

Steps to reproduce:

Rerun template

Current results:

Failed

Expected results:

VM running

I cannot find many details as to the KVM_CPU_FEATURES that could be added to the template and not sure if possible whether these should be set at ths VM or HOST or BARE METAL LEVEL

2

Hello, @Derek_Northcote , and welcome to the forum

Have you checked the documentation at Firecracker Driver — OpenNebula 6.8.2 documentation ? Is it possible that you get more relevant information about the problem on the /var/lib/one/datastores/<sys_ds_id>/<vm_id>/logs.fifo file

Thank you!

3

You should review the configuration because qemu and qemu-kvm-one are words, not expected in the Firecracker context…

4

Thanks for the replies. Turns out cgroups v2 was enabled in the host. Disabling this solved the issue.