Skip to content

qemu: keep x86 CAS I/O on a single virtio queue - #63

Draft
fionera wants to merge 1 commit into
hermeticbuild:mainfrom
fionera:fionera/x86-cas-single-queue
Draft

fionera wants to merge 1 commit into
hermeticbuild:mainfrom
fionera:fionera/x86-cas-single-queue

Conversation

@fionera

@fionera fionera commented Nov 2, 2026

Copy link
Copy Markdown

Concurrent CAS traffic stalled with the embedded x86 microvm's four-queue virtio block configuration. Keeping the same CAS disk and guest CPU count but selecting one disk queue allowed the workload to finish.

Use one CAS virtio queue for x86 microvms while preserving the existing queue selection on other architectures. This is a targeted mitigation, not a root-cause diagnosis or a claim that virtio multiqueue is generally broken. The follow-up issue tracks reproducing the stall and restoring multiqueue safely.

The combined Linux integration run completed sustained CAS traffic and build/test execution with the single-queue setting. macOS/Windows VM hosts and a controlled before/after throughput benchmark have not been validated.

Mitigates #56; keep that issue open to investigate and eventually restore multiqueue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant