From: skvarlamatus@gmail.com
To: asmadeus@codewreck.org, 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: Mon, 14 Sep 2026 19:51:56 +0200 [thread overview]
Message-ID: <20260914175156.75298-1-skvarlamatus@gmail.com> (raw)
In-Reply-To: <aqautUJPkTMvmIGU@codewreck.org>
On Sun, Sep 13, 2026 at 14:09 +0000, asmadeus@codewreck.org wrote:
> I've looked at v1/v2 threads and I don't actually see any rationale
> explained: what's the benefit of this over e.g. virito or xen
> transports?
> Do you have/use an hypervisor that cannot do virito 9p (or virtfs) but
> has vsock or something like that?
virtio-9p is only supported by Qemu/KVM. Vsock transport works on any hypervisor
with vsock support and allows using userspace 9P servers.
The motivation behind this patch is primarily driven by podman machine's
use-case, which is file sharing on Windows [1] [2].
The hypervisor there is Hyper-V/WSL, which supports vsock for host-guest
data transfers [3], but not virtio-9p or virtfs. Having vsock transport in the
driver would simplify the codebase and make the use-case more flexible.
> On a similar topic, do you have an actual server that works with vsock?
Podman implements its own 9P server in Go using the p9 library [4] with
vsock support via virtsock [5], but it runs as part of podman machine.
For standalone 9p servers, I only know of diod and example implementations
of various 9p server libraries (i.e. [6]), but none of them support vsock.
As far as I know, there is one 9p FUSE client with native vsock support
(my contribution) [7].
[1] https://github.com/podman-container-tools/podman/blob/main/cmd/podman/machine/server9p.go
[2] https://github.com/podman-container-tools/podman/blob/main/cmd/podman/machine/client9p.go
[3] https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/make-integration-service
[4] https://github.com/hugelgupf/p9
[5] https://github.com/linuxkit/virtsock
[6] https://github.com/hugelgupf/p9/blob/main/cmd/p9ufs/p9ufs.go
[7] https://github.com/ftrvxmtrx/9pfs
--
Matus
next prev parent reply other threads:[~2026-09-14 17:52 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-09 16:17 skvarlamatus
2026-09-13 14:09 ` Dominique Martinet
2026-09-14 17:51 ` skvarlamatus [this message]
2026-09-14 23:44 ` Dominique Martinet
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=20260914175156.75298-1-skvarlamatus@gmail.com \
--to=skvarlamatus@gmail.com \
--cc=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=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
all inboxes | Powered by JetHome®