Conversation
This was referenced Aug 22, 2026
1stvamp
force-pushed
the
refactor/vhost-user-block-delegate
branch
from
August 25, 2026 01:17
9db1d56 to
9a9a8f3
Compare
zulinx86
added
the
Status: Awaiting assignee
1stvamp
force-pushed
the
refactor/vhost-user-block-delegate
branch
2 times, most recently
from
September 8, 2026 11:05
4f5fb32 to
42cc375
Compare
1stvamp
force-pushed
the
refactor/vhost-user-block-delegate
branch
3 times, most recently
from
September 14, 2026 23:53
7cbf8f2 to
22e962a
Compare
1stvamp
force-pushed
the
refactor/vhost-user-block-delegate
branch
from
September 20, 2026 10:51
22e962a to
4f97583
Compare
1stvamp
force-pushed
the
refactor/vhost-user-block-delegate
branch
from
October 1, 2026 13:50
4f97583 to
0000bb5
Compare
The vhost-user frontends duplicate everything that is not specific to the virtio device type they implement: connecting to the backend socket, negotiating virtio and protocol features, fetching the config space, allocating queues and eventfds, and setting up the backend's vrings on activation. Add VhostUserDevice to hold that shared state, built from a VhostUserDeviceSpec carrying the parts that do vary: socket path, queue count and size, the features to offer, the config space size, whether CONFIG is mandatory, and the metrics name. Device types embed it and keep their own state alongside. Two details worth noting for the callers that follow. Fetching the config space is skipped when the backend does not ack CONFIG, leaving an empty config space, since only a frontend with no device-specific fallback needs to insist on it. And activate() sets up the queues the guest marked ready rather than every allocated queue, because the number a driver initialises is dictated by the backend-owned config space, so initializing an unconfigured queue returns NotReady and aborts activation. Real vring indices are preserved: queues 0 and 2 being ready maps to vrings 0 and 2, not 0 and 1. Activating with no ready queues is rejected rather than quietly setting up nothing. The spec is validated before the socket is touched, since a frontend built from it may be configured at runtime rather than from constants: the queue count is bounded by what the PCI notification region can address, the queue size has to be a power of two, and the config space size has to fit the protocol's own limit. The config space size is a size rather than an upper bound, in that the backend has to return exactly that many bytes. The vhost crate checks the size the reply declares but not the length of the payload behind it, so the length is checked here too. Otherwise a backend could declare the size that was asked for, send fewer bytes, and leave the guest reading past the end of what it sent. No device type uses this yet. Signed-off-by: Wes Mason <wes@1stvamp.org>
The block device carried its own copy of the feature negotiation, config
space fetch, queue allocation and vring setup, none of which is specific
to block. Move that state into VhostUserDevice and keep only the
block-specific fields here: the drive id, partuuid, cache type and the
root and readonly flags.
Most of the behaviour is unchanged. Block still offers the same feature
set, including FLUSH when the cache type is Writeback, still treats
CONFIG as optional, and still reports metrics under block_{drive_id}.
Activating without a ready queue reports QueueError::NotReady as before,
though it now comes from the generic readiness check rather than from
initializing queue 0. The double-activation assert moves into the
generic device, which owns the state it guards.
read_only is now read from the features the backend acked rather than
from a local that a later shadowing narrowed, so the ordering trap fixed
in "fix(vhost-user-block): honour a readonly backend" cannot come back.
VhostUserBlockError keeps its existing variants and their messages,
which surface through the API, and gains one for the generic errors
block itself cannot produce.
One behaviour does change. Fetching the config space now goes through
the shared frontend, which requires the backend to return as many bytes
as were asked for, so a backend that answers a 60 byte request with
fewer now fails to attach where before it was accepted and left the rest
of the config space short.
Signed-off-by: Wes Mason <wes@1stvamp.org>
1stvamp
force-pushed
the
refactor/vhost-user-block-delegate
branch
from
October 2, 2026 12:25
0000bb5 to
0f3261f
Compare
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
3 participants
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.
Changes
Moves vhost-user-block onto the shared
VhostUserDevicefrontend, so it no longer carries its own copy of the feature negotiation, config space fetch, queue allocation and vring setup. It keeps the fields that are specific to it: the drive id, partuuid, cache type, and the root and readonly flags.One behaviour does change. Fetching the config space now goes through the shared frontend, which requires the backend to return as many bytes as were asked for, so a backend that answers a 60 byte request with fewer now fails to attach where before it was accepted and left the rest of the config space short.
read_onlyis now read from the features the backend acked rather than from a local that a later shadowing narrowed, so the ordering trap fixed in #6083 cannot come back.Reason
De-duplicates the vhost-user frontend between block and the generic device that follows, so there is one implementation of the protocol handling rather than two.
This is step 2 of the 3 @ShadowCurse asked for in #6072.
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 checkbuild --allto verify that the PR passesbuild checks on all supported architectures.
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.This is part 3 of 4 in a stack made with GitButler: