ext/sockets: AF_VSOCK support addition. - #23623
Draft
devnexen wants to merge 5 commits into
Draft
Conversation
vsock carries traffic across the VM boundary with no NIC, no IP and no DNS, so it works before guest networking is up, or where there is none at all as in AWS Nitro Enclaves. A guest connects to VMADDR_CID_HOST and a host to the guest's context ID, both through the usual socket_bind()/socket_connect() with the CID passed as the address string.
devnexen
force-pushed
the
socket_avsock
branch
from
September 9, 2026 03:41
17a71b8 to
4ad8b38
Compare
to really work no test can be exercised really).
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
1 participant
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.
vsock carries traffic across the VM boundary with no NIC, no IP and no DNS, so it works before guest networking is up, or where there is none at all as in AWS Nitro Enclaves. A guest connects to VMADDR_CID_HOST and a host to the guest's context ID, both through the usual socket_bind()/socket_connect() with the CID passed as the address string.