From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Marc-André Lureau" <marcandre.lureau@gmail.com>
Cc: Gerd Hoffmann <kraxel@redhat.com>, QEMU <qemu-devel@nongnu.org>
Subject: Re: vnc clipboard support
Date: Fri, 29 Jan 2021 12:21:37 +0000 [thread overview]
Message-ID: <20210129122137.GA4008275@redhat.com> (raw)
In-Reply-To: <CAJ+F1CLerj6GSN-XQftZf8m=_cCdcJb1Yn-yFGDNP_D18uN5FA@mail.gmail.com>
On Fri, Jan 29, 2021 at 03:58:00PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Jan 29, 2021 at 3:24 PM Daniel P. Berrangé <berrange@redhat.com> wrote:
> >
> > On Fri, Jan 29, 2021 at 12:18:19AM +0400, Marc-André Lureau wrote:
> > can have QEMU open the vsock device internally, it feels a bit silly to
> > have one part of QEMU writing to a vsock device, and then another part
> > of QEMU reading back from the very same device. Especially because you
> > have now introduced the extra problem of having to allocate unique
> > vsock addresses for each instance and deal with possibility of external
> > apps maliciously trying to interact with your vsock backend.
> >
> > As above though, I think the way spice used virtio-serial was suboptimal
> > and it should have had one extra virtio-serial device per seat.
>
> And per service? and libvirt to hotplug stuff? Sounds insane to me.
> And what about services that need to handle several connections in the
> guest. For example, the way spice-webdavd works is really a pain, it
> has to multiplex guest connections over virtio-serial... All of this
> would be so much simpler with a single vsock connection and some kind
> of bus.
I wasn't really suggesting it for something like spice-webdavd, just
the spice agent functionality, which is not really connection-oriented
stuff. ie its a simple RPC like service where there's only ever one
client and server endpoint. spice-webdavd would clearly be better
based on vsock, since it is inherantly a multi-connection architecture.
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 :|
next prev parent reply other threads:[~2021-01-29 12:23 UTC|newest]
Thread overview: 46+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-01-28 17:12 vnc clipboard support Gerd Hoffmann
2021-01-28 17:35 ` Daniel P. Berrangé
2021-01-29 7:59 ` Gerd Hoffmann
2021-01-28 17:38 ` Christophe de Dinechin
2021-01-29 8:03 ` Gerd Hoffmann
2021-01-29 10:50 ` Christophe de Dinechin
2021-01-29 11:08 ` Daniel P. Berrangé
2021-01-29 14:19 ` Christophe de Dinechin
2021-01-29 14:32 ` Daniel P. Berrangé
2021-02-01 15:27 ` Christophe de Dinechin
2021-02-01 15:51 ` Daniel P. Berrangé
2021-02-01 16:31 ` Christophe de Dinechin
2021-02-01 16:56 ` Daniel P. Berrangé
2021-02-01 17:28 ` Christophe de Dinechin
2021-02-01 17:40 ` Daniel P. Berrangé
2021-02-01 18:45 ` BALATON Zoltan
2021-02-02 11:31 ` Gerd Hoffmann
2021-02-02 12:31 ` BALATON Zoltan
2021-02-02 12:38 ` Daniel P. Berrangé
2021-02-02 13:35 ` Gerd Hoffmann
2021-02-02 16:36 ` Gerd Hoffmann
2021-02-02 21:00 ` Marc-André Lureau
2021-02-03 9:40 ` Gerd Hoffmann
2021-02-02 11:10 ` Gerd Hoffmann
2021-02-02 11:17 ` Daniel P. Berrangé
2021-02-02 11:44 ` Gerd Hoffmann
2021-01-29 15:04 ` Gerd Hoffmann
2021-02-01 17:07 ` Christophe de Dinechin
2021-01-29 11:49 ` Gerd Hoffmann
2021-01-29 13:28 ` Christophe de Dinechin
2021-01-28 17:57 ` Laszlo Ersek
2021-01-29 8:09 ` Gerd Hoffmann
2021-01-29 10:02 ` Daniel P. Berrangé
2021-01-28 20:18 ` Marc-André Lureau
2021-01-28 20:47 ` BALATON Zoltan
2021-01-29 7:59 ` Christophe de Dinechin
2021-01-29 8:27 ` Gerd Hoffmann
2021-01-29 8:34 ` Marc-André Lureau
2021-01-29 10:33 ` Gerd Hoffmann
2021-01-29 11:10 ` Daniel P. Berrangé
2021-01-29 11:24 ` Daniel P. Berrangé
2021-01-29 11:58 ` Marc-André Lureau
2021-01-29 12:21 ` Daniel P. Berrangé [this message]
2021-01-29 12:02 ` Gerd Hoffmann
2021-01-29 12:10 ` Marc-André Lureau
[not found] <CWLP265MB5209050A121EB63FE07F9BD5A8689@CWLP265MB5209.GBRP265.PROD.OUTLOOK.COM>
2023-04-30 16:20 ` VNC " Philipp Hahn
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=20210129122137.GA4008275@redhat.com \
--to=berrange@redhat.com \
--cc=kraxel@redhat.com \
--cc=marcandre.lureau@gmail.com \
--cc=qemu-devel@nongnu.org \
/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).