From: Dominique Martinet <asmadeus@codewreck.org>
To: skvarlamatus@gmail.com
Cc: ericvh@kernel.org, lucho@ionkov.net, linux_oss@crudebyte.com,
v9fs@lists.linux.dev, linux-kernel@vger.kernel.org,
stefanha@redhat.com, sgarzare@redhat.com
Subject: Re: [PATCH v3] net/9p: add vsock transport
Date: Tue, 22 Sep 2026 17:26:15 +0900 [thread overview]
Message-ID: <arI7p2EinDektW0n@codewreck.org> (raw)
In-Reply-To: <20260916194204.99506-1-skvarlamatus@gmail.com>
skvarlamatus@gmail.com wrote on Wed, Sep 16, 2026 at 09:42:04PM +0200:
> On Mon, Sep 14, 2026 at 23:44 +0000, asmadeus@codewreck.org wrote:
> > Right, diod has an open issue[1] for vsock but since there were no
> > obvious client available either it was never done.
> > I don't think it's difficult to do (probably more work to add the option
> > parsing than the actual vsock support)
>
> Definitely agree. I think with this in the client, it could encourage
> more servers to add vsock support too.
Just had a quick look at diod code and their handling of the listen
option is purely string based, passed to getaddrinfo() to figure out if
the user requested ipv4/ipv6 -- I'm pretty sure getaddrinfo() doesn't
want to have anything to do with vsock, but I don't suppose there's a
canonical string representation for vsock is there? (something like
`cid:<cid>:<port>` instead of the usual <cid>:<port> couple printed?)
I didn't want to add a new option such as --vsock-listen, but I'd hate
to disambiguate vsock from ipv4/v6 as a string even more... :)
FWIW commit message ended up like this (everything ellipsed is exactly
as you sent), so just extending the sentence a bit to mention Hyper-V
and podman machine:
```
net/9p: add vsock transport
Add vsock as a transport option for 9P client connections. This
allows mounting 9P filesystems over VM sockets without requiring TCP/IP
networking or additional userspace tools, which can be useful with
hypervisors other than Qemu/KVM, for example Hyper-V/WSL which is used
by podman machine on Windows[1][2].
[implementation details]
Usage:
mount -t 9p -o trans=vsock[,port=<port>] <CID> /mnt/point
Link: https://github.com/podman-container-tools/podman/blob/main/cmd/podman/machine/server9p.go [1]
Link: https://github.com/podman-container-tools/podman/blob/main/cmd/podman/machine/client9p.go [2]
[sign-offs/reviews]
```
Thanks,
--
Dominique Martinet | Asmadeus
prev parent reply other threads:[~2026-09-22 8:26 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 16:17 [PATCH v3] net/9p: add vsock transport skvarlamatus
2026-09-13 14:09 ` Dominique Martinet
2026-09-14 17:51 ` skvarlamatus
2026-09-14 23:44 ` Dominique Martinet
2026-09-16 19:42 ` skvarlamatus
2026-09-22 8:26 ` Dominique Martinet [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=arI7p2EinDektW0n@codewreck.org \
--to=asmadeus@codewreck.org \
--cc=ericvh@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux_oss@crudebyte.com \
--cc=lucho@ionkov.net \
--cc=sgarzare@redhat.com \
--cc=skvarlamatus@gmail.com \
--cc=stefanha@redhat.com \
--cc=v9fs@lists.linux.dev \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox