ci: fix arm64 QEMU block hotplug coverage - #98
Merged
Conversation
This file contains hidden or 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
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.
Summary
Root cause
The arm64 QEMU
virtmachine cannot hotplug avirtio-blk-pcidevice directly onpcie.0. The previous scripts ignored the monitor error, accepted static/dev/vd*nodes as proof of device presence, and could react to echoed marker commands before the guest actually executed them. CapOS also disabledCONFIG_HOTPLUG_PCI_PCIE, so devices attached through a root port were not enumerated by the guest.Validation
bash -non all changed QEMU scriptsshellcheckon all changed QEMU scriptsgit diff --checkcargo test --workspace --all-targets— 156 passedThe full rebuilt CapOS arm64 image path is exercised by this PR CI.