lcow: disable virtio-vsock init #2461
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
When a kernel is built with virtio-vsock we encounter a kernel panic in our init script, while trying to read entropy from the host. Parsing through the boot logs, it seems like the hv_sock transport is not being initialized: ``` [ 0.712310] NET: Registered PF_VSOCK protocol family [ 0.716225] hv_vmbus: registering driver hv_sock [ 0.719551] hv_vmbus: unregistering driver hv_sock [ 0.723281] IPI shorthand broadcast: enabled ``` Disabling `virtio_vsock_init` seems to fix the problem: ``` [ 0.829397] NET: Registered PF_VSOCK protocol family [ 0.831728] initcall virtio_vsock_init blacklisted [ 0.835999] hv_vmbus: registering driver hv_sock [ 0.837906] IPI shorthand broadcast: enabled ``` For kernels built without virtio-vsock, skipping `virtio_vsock_init` is a no-op: ``` [ 0.539320] NET: Registered PF_VSOCK protocol family [ 0.541417] hv_vmbus: registering driver hv_sock [ 0.549999] IPI shorthand broadcast: enabled ``` Signed-off-by: Maksim An <maksiman@microsoft.com>
helsaawy
approved these changes
Jun 19, 2025
ambarve
approved these changes
Jun 19, 2025
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.
When a kernel is built with virtio-vsock we encounter a kernel panic in our init script, while trying to read entropy from the host. Parsing through the boot logs, it seems like the hv_sock transport is not being initialized:
Disabling
virtio_vsock_initseems to fix the problem:For kernels built without virtio-vsock, skipping
virtio_vsock_initis a no-op: