fix: Add keyboard drivers to CI guest kernels #5051
Merged
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.
Firecracker supports sending a CTRL+ALT+DEL event to the guest, to
trigger a reboot, and we had an integration test for this. However, the
integration test was broken (see #5050), and actually, our guest kernels
dont have the necessary drivers compiled in to actually receive the
CTRL+ALT+DEL.
Fix this by actually enabling the relavant Kconfigs. We don't re-build
the artifacts just yet, as it'll happen anyway in a few days when we
branch off the next release.
tested it on ARM as well, the kernel just ignores the superfluous config options it seems
License Acceptance
By submitting this pull request, I confirm that my contribution is made under
the terms of the Apache 2.0 license. For more information on following Developer
Certificate of Origin and signing off your commits, please check
CONTRIBUTING.md.PR Checklist
tools/devtool checkstyleto verify that the PR passes theautomated style checks.
how they are solving the problem in a clear and encompassing way.
in the PR.
CHANGELOG.md.Runbook for Firecracker API changes.
integration tests.
TODO.rust-vmm.