Skip to content

Add vhost_user_vsock support for cvd load configuration#2725

Open
k311093 wants to merge 1 commit into
google:mainfrom
k311093:vhost
Open

Add vhost_user_vsock support for cvd load configuration#2725
k311093 wants to merge 1 commit into
google:mainfrom
k311093:vhost

Conversation

@k311093

@k311093 k311093 commented Jun 17, 2026

Copy link
Copy Markdown
Collaborator

Since vhost_user_vsock is not enabled by default at x86_64, we need to turn it on manually to support multiple docker instance scenario.

But there is a no way to set it by using Host Orchestrator API. So add support for vhost_user_vsock to cvd load configuration file that can be used for Host Orchestrator API.

@k311093 k311093 force-pushed the vhost branch 2 times, most recently from 433a2cf to 6525898 Compare June 17, 2026 06:22
@k311093 k311093 marked this pull request as ready for review June 18, 2026 04:07
@k311093 k311093 added the kokoro:run Run e2e tests. label Jun 18, 2026
@GoogleCuttlefishTesterBot GoogleCuttlefishTesterBot removed the kokoro:run Run e2e tests. label Jun 18, 2026

@ikicha ikicha left a comment

Copy link
Copy Markdown
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, a few nits.

Comment thread base/cvd/cuttlefish/host/commands/cvd/cli/parser/instance/vm_configs_test.cc Outdated
Since vhost_user_vsock is not enabled by default at x86_64, we need
to turn it on manually to support multiple docker instance scenario.

But there is a no way to set it by using Host Orchestrator API. So
add support for vhost_user_vsock to cvd load configuration file that
can be used for Host Orchestrator API.
@k311093 k311093 added the kokoro:run Run e2e tests. label Jun 18, 2026
@GoogleCuttlefishTesterBot GoogleCuttlefishTesterBot removed the kokoro:run Run e2e tests. label Jun 18, 2026
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.

3 participants