I'm starting to think some unreliable test runs — "waiting for the VM to finish booting" never being paired up with a "(finished: waiting for the VM to finish booting, in N.M seconds)" — could be caused by KVM not being set up:

Virtualisation disk image created.
Could not access KVM kernel module: No such file or directory
qemu-kvm: failed to initialize kvm: No such file or directory
qemu-kvm: falling back to tcg

I don't know which level this happens at, but I'm running the nixos/nix:2.18.1 container and setting system-features = benchmark big-parallel kvm nixos-test. What else do I need to do to enable KVM?

I'm starting to think some unreliable test runs — "waiting for the VM to finish booting" never being paired up with a "(finished: waiting for the VM to finish booting, in N.M seconds)" — could be caused by KVM not being set up:

Virtualisation disk image created.
Could not access KVM kernel module: No such file or directory
qemu-kvm: failed to initialize kvm: No such file or directory
qemu-kvm: falling back to tcg

I don't know which level this happens at, but I'm running the nixos/nix:2.18.1 container and setting system-features = benchmark big-parallel kvm nixos-test. What else do I need to do to enable KVM? /dev/kvm does not exist within the Docker image.

In reply to @k900:0upti.me
Gitlab managed runners aren't guaranteed to have KVM AFAIK

In reply to @raitobezarius:matrix.org
To debug this properly, you'd need to attach all sorts of logs from the firmware, the kernel and QEMU itself

In reply to @raitobezarius:matrix.org
Well if it's a VM, you can enable debugging of OVMF if you are using UEFI, you can modify the scripts to make QEMU log information about itself and you can boot the kernel with the right log level, send this as artifacts and bring them