Bug#1015966: ci.debian.net: Please enable KVM support on all x86 runners
Hi Guilhem, Thanks for your report. As this isn't a bug against debci, it would have been more appropriate to file it salsa against our ci.d.n configuration project: https://salsa.debian.org/ci-team/debian-ci-config/issues/ On 24-07-2022 16:53, Guilhem Moulin wrote: Presumably all amd64 hosts actually do have KVM support but don't always advertise the capability to the runner. All amd64 (and i386) hosts apart from ci-worker13 are AWS VM's. I wouldn't be surprised if they don't support KVM. Would it be possible to enable KVM support on all x86 runners? Don't know. Alternatively, is there a mechanism to exclude specific runners for a given source package? https://salsa.debian.org/ci-team/debci/-/issues/166 (not yet, and probably not real soon) Also please consider pre-creating /dev/kvm on runners with KVM support (this is normally taken care of by udev but can be done manually), that way we can drop the ‘Restrictions: needs-root’ on our autopkgtests :-) Paul OpenPGP_signature Description: OpenPGP digital signature
Bug#1015966: ci.debian.net: Please enable KVM support on all x86 runners
Package: debci Severity: wishlist Dear Maintainer, In order to test behavior at early boot stage we have autopkgtests in src:cryptsetup (resp. src:dropbear) that launch a virtual machine and mock user interaction through the serial console (resp. SSH) to unlock the disks and check that boot eventually yields a login prompt. (These autopkgtests don't use ‘Restrictions: isolation-machine’; they launch QEMU themselves and interact with the guest at early boot stage.) This appears to work rather well and is reasonably fast on x86 thanks to hardware virtualization support. AFAICT the debci runners don't expose /dev/kvm, but the device can be created in the autopkgtest with `mknod /dev/kvm c 10 232` before calling QEMU. However not all amd64 runners seem to support KVM in the first place: ci-worker13 (which fortunately seem to pick most jobs) does support it but AFAICT neither do ci-worker02 nor ci-worker05. This means that depending on the runners the tests are more likely to timeout and fail. (Moreover we'd like to test multiple layouts to check for past regressions, and without KVM it gets very slow.) Presumably all amd64 hosts actually do have KVM support but don't always advertise the capability to the runner. Would it be possible to enable KVM support on all x86 runners? Alternatively, is there a mechanism to exclude specific runners for a given source package? Also please consider pre-creating /dev/kvm on runners with KVM support (this is normally taken care of by udev but can be done manually), that way we can drop the ‘Restrictions: needs-root’ on our autopkgtests :-) Thanks for maintaining debci! -- Guilhem. signature.asc Description: PGP signature
