Hi Bernhard, Thanks for your response! See my comments below: On Tue, Dec 19, 2023, at 3:24 AM, Bernhard M. Wiedemann via openSUSE Factory wrote:
On 19/12/2023 05.25, Xu Zhao wrote:
Currently I am blocked by using Qemu kvm to kick of specific tumbleweed snapshot image and test nvidia driver compile (sth like open build system). If anyone knows how to do that, or simply give code pointers on how OBS runs Qemu KVM, that would be very much appreciated.
https://github.com/nektos/act says
GitHub Actions are running in fully virtualized machines
so you probably cannot get KVM working there. But chroot or containers should be an option. Chroot or plain containers will not work because NVIDIA driver will not build when the host kernel gcc version is incompatible with the container kernel header. https://forums.developer.nvidia.com/t/conftest-failed-error-while-trying-to-... Conftest will fail when I was trying to cross-compile from a different kernel header files than the host kernel.
I was about to try https://github.com/docker/setup-qemu-action, since Docker claims that they could run QEMU on GitHub Action runners. However, I am not sure how to proceed (e.g., should I use tumbleweed:latest docker image or tumbleweed ISO).
OBS workers OTOH run on bare metal and thus have access to hardware needed for KVM.
Still, I am interested in what openSUSE Tumbleweed image is used in KVM. In the worst case, I could run self-hosted GitHub runner on my own bare-metal workstation, and run openSUSE Tumbleweed KVM images on it with GitHub actions.
Attachments: * OpenPGP_signature.asc
Best, Xu