qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Daniel P. Berrangé" <berrange@redhat.com>
To: Roman Kiryanov <rkir@google.com>,
	Stefano Garzarella <sgarzare@redhat.com>
Cc: 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: Thu, 18 Apr 2024 10:34:43 +0100	[thread overview]
Message-ID: <ZiDpM7ZusU0SvH7K@redhat.com> (raw)
In-Reply-To: <CAOGAQerx0DmHvJNf05wuJFOtXVwDFTt7fy0-GmBZ7xKoLAHTKQ@mail.gmail.com>

On Wed, Apr 17, 2024 at 12:31:41PM -0700, Roman Kiryanov wrote:
> Hi Daniel,
> 
> thank you for looking into this. I checked how VHOST_USER_VSOCK and it
> refers to the vhost-user protocol. It is implemented in the
> subprojects/libvhost-user library, but this library depends on poll.h
> and linux/vhost.h files. Do you know if it builds/works on Windows?

Stefano recently ported it to work on any POSIX platform,
but obviously that still excludes Windows:

  https://lists.nongnu.org/archive/html/qemu-devel/2024-04/msg00388.html

I'm unclear what blockers there are wrt Windows, but perhaps
Stefano (CC'd) can advise.

Personally, while I think vhost-user is a good option for the
vast majority of cases, I believe QEMU ought to natively
implement a simple self contained AF_UNIX backend for vsock,
avoiding need to depend on 3rd party software for its use.

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 :|



  reply	other threads:[~2024-04-18  9:35 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é [this message]
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é

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=ZiDpM7ZusU0SvH7K@redhat.com \
    --to=berrange@redhat.com \
    --cc=alex.bennee@linaro.org \
    --cc=jansene@google.com \
    --cc=jpcottin@google.com \
    --cc=mett@google.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 NNTP newsgroup(s).