Start of QEMU K3s based CI #13
Draft
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Even without nested virt I have run into a weird issue: https://www.reddit.com/r/VFIO/comments/1c1aynj/qemu_or_ovmf_efi_firmware_hangs_with_no_output/ |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
One possible way to have CI with GPUs is to setup a VM with k3s and NVIDIA installed. Boot the VM with GPU
passthrough, run the tests, then rollback to a snapshot (delete the overlay we used).
It would be nice to script creating the VMs. Also in cases where VM is not QEMU or is not a VM we can just run
the generic portion of the tests. Copying the docker image into the container runtime is K3s specific, but it
could substituted for a repo.
#9