From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Paolo Bonzini <pbonzini@redhat.com>
Cc: "Stefano Garzarella" <sgarzare@redhat.com>,
"Marc-André Lureau" <marcandre.lureau@gmail.com>,
"Roman Kiryanov" <rkir@google.com>,
"Peter Maydell" <peter.maydell@linaro.org>,
alex.bennee@linaro.org, "QEMU Developers" <qemu-devel@nongnu.org>,
"JP Cottin" <jpcottin@google.com>,
"Erwin Jansen" <jansene@google.com>,
"Mehdi Alizadeh" <mett@google.com>
Subject: Re: Hermetic virtio-vsock in QEMU
Date: Wed, 8 May 2024 14:32:45 +0100 [thread overview]
Message-ID: <Zjt-_VI79QwR2UEF@redhat.com> (raw)
In-Reply-To: <CABgObfb8o3L_FawdwFX7Ow-+LN7wyGbvSLWubJrpyTgH3uo-uQ@mail.gmail.com>
On Wed, May 08, 2024 at 03:00:30PM +0200, Paolo Bonzini wrote:
> On Wed, May 8, 2024 at 2:51 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> > Designwise, a native VSOCK backend in QEMU really should implement the
> > same approach defined by firecracker, so that we have interoperability
> > with systemd, firecracker and cloud-hypervisor. See
> >
> > https://gitlab.com/qemu-project/qemu/-/issues/2095
> > https://github.com/firecracker-microvm/firecracker/blob/main/docs/vsock.md#firecracker-virtio-vsock-design
> >
> > This involves multiple UNIX sockets on the host
> >
> > 1 * /some/path - QEMU listens on this, and accepts connections
> > from other host processes. The client sends
> > "PORT <num>" to indicate that guest port it
> > is connecting to
> >
> > n * /some/path_$PORT - QEMU connect to this for outgoing connections
> > from the guest. Other host processes need
> > to listen on whatever path_$PORT need to be
> > serviced
>
> The former is quite horrible, but okay. Out of curiosity, which
> clients are using that convention?
I've no idea. The RFE above came out of a discussion with systemd
upstream when they were implementing their SSH-over-vsock host SSH
plugin
https://github.com/systemd/systemd/pull/30777
where it was noted that their code for using AF_VSOCK natively
wouldn't work with firecracker or cloud-hypervisor. Although
they've got native AF_VSOCK support there merged, conceptually
it looks desirable to have a common way of exposing AF_VSOCK
on the host.
Also, aside from cross-OS portability, this has the other benefit
that arbitarary users on the same host can make use of AF_VSOCK,
without worrying about CID clashes in the host kernel between
guests they're not aware of. All guests can just use the same
fixed CID and the UNIX socket exposure on the host namespaces
them.
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
prev parent reply other threads:[~2024-05-08 13:33 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-03 21:30 Hermetic virtio-vsock in QEMU Roman Kiryanov
2024-04-15 11:20 ` Daniel P. Berrangé
2024-04-17 19:31 ` Roman Kiryanov
2024-04-18 9:34 ` Daniel P. Berrangé
2024-05-07 8:10 ` Stefano Garzarella
2024-05-08 6:20 ` Roman Kiryanov
2024-05-08 7:49 ` Stefano Garzarella
2024-05-08 9:13 ` Marc-André Lureau
2024-05-08 9:38 ` Stefano Garzarella
2024-05-08 12:37 ` Paolo Bonzini
2024-05-08 12:51 ` Daniel P. Berrangé
2024-05-08 13:00 ` Paolo Bonzini
2024-05-08 13:32 ` Daniel P. Berrangé [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=Zjt-_VI79QwR2UEF@redhat.com \
--to=berrange@redhat.com \
--cc=alex.bennee@linaro.org \
--cc=jansene@google.com \
--cc=jpcottin@google.com \
--cc=marcandre.lureau@gmail.com \
--cc=mett@google.com \
--cc=pbonzini@redhat.com \
--cc=peter.maydell@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=rkir@google.com \
--cc=sgarzare@redhat.com \
/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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).