Hello,
Am 29.04.23 um 17:29 schrieb octavef...@outlook.fr:
I'm trying to use the copy/paste with VNC.
I'm launching qemu with:
$ qemu-system-x86_64 -hda debiandisk.img vnc :1
I'm using tightvncviewer which has support for copy/paste.
I try to copy text between guest and host.
It doesn't wor
Hello,
I'm trying to use the copy/paste with VNC.
I'm launching qemu with:
$ qemu-system-x86_64 -hda debiandisk.img vnc :1
I'm using tightvncviewer which has support for copy/paste.
I try to copy text between guest and host.
It doesn't work. Neither from host to guest or guest to host.
As fa
21.05.2021 15:51, Gerd Hoffmann wrote:
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Marc-André Lureau
Message-id: 20210
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Marc-André Lureau
Message-id: 20210519053940.1888907-1-kra...@redhat.com
Mes
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Marc-André Lureau
---
ui/vnc.h | 24
ui/vnc-clipboard.c | 3
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
Reviewed-by: Marc-André Lureau
---
ui/vnc.h | 24
ui/vnc-clipboard.c | 3
On Fri, Apr 23, 2021 at 12:34 PM Gerd Hoffmann wrote:
> This patch adds support for cut+paste to the qemu vnc server, which
> allows the vnc client exchange clipbaord data with qemu and other peers
> like the qemu vdagent implementation.
>
> Signed-off-by: Gerd Hoffmann
>
Reviewed-by: Marc-Andr
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
---
ui/vnc.h | 24
ui/vnc-clipboard.c | 323 +
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
---
ui/vnc.h | 24
ui/vnc-clipboard.c | 323 +
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
---
ui/vnc.h | 24
ui/vnc-clipboard.c | 323 +
Hi,
> > I don't see the
> > agent doing the same (I might be missing something).
>
> Hmm, ok. Guess I should better be prepared to receive messages larger
> than VD_AGENT_MAX_DATA_SIZE ...
Confirmed. Cut+paste large text blocks in the guest -> hangs qemu
vdagent implementation, because the m
On Wed, Mar 03, 2021 at 06:27:27PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Wed, Mar 3, 2021 at 4:13 PM Gerd Hoffmann wrote:
>
> > Hi,
> >
> > > > +case Z_BUF_ERROR:
> > > > +out_len <<= 1;
> > > > +if (out_len > (1 << 20)) {
> > > >
> > >
> > > 1Mb isn't tha
Hi
On Wed, Mar 3, 2021 at 4:13 PM Gerd Hoffmann wrote:
> Hi,
>
> > > +case Z_BUF_ERROR:
> > > +out_len <<= 1;
> > > +if (out_len > (1 << 20)) {
> > >
> >
> > 1Mb isn't that much, is it? Well, since it handles only text for now it's
> > probably enough. Would it
Hi,
> > +case Z_BUF_ERROR:
> > +out_len <<= 1;
> > +if (out_len > (1 << 20)) {
> >
>
> 1Mb isn't that much, is it? Well, since it handles only text for now it's
> probably enough. Would it make sense to make this a #define for clarity ?
Yep. While talking about
On Fri, Feb 19, 2021 at 5:25 PM Gerd Hoffmann wrote:
> This patch adds support for cut+paste to the qemu vnc server, which
> allows the vnc client exchange clipbaord data with qemu and other peers
>
clipboard
like the qemu vdagent implementation.
>
> Signed-off-by: Gerd Hoffmann
> ---
> ui/vn
This patch adds support for cut+paste to the qemu vnc server, which
allows the vnc client exchange clipbaord data with qemu and other peers
like the qemu vdagent implementation.
Signed-off-by: Gerd Hoffmann
---
ui/vnc.h | 24
ui/vnc-clipboard.c | 326 +
Hi,
> > Well, spice isn't that much better. Has a short, fixed list too:
> >
> > VD_AGENT_CLIPBOARD_UTF8_TEXT
> There has been some attempts to support generic mime types in Spice clipboard:
> https://lists.freedesktop.org/archives/spice-devel/2018-May/043782.html
>
> (If I am not mistaken, I
Hi
On Tue, Feb 2, 2021 at 9:18 PM Gerd Hoffmann wrote:
>
> On Tue, Feb 02, 2021 at 02:35:34PM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > The VNC protocol is way too crude. It is limited to transferring
> > > plain text, and provides no way to specify or negotiate a character
> > > set. The R
On Tue, Feb 02, 2021 at 02:35:34PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > The VNC protocol is way too crude. It is limited to transferring
> > plain text, and provides no way to specify or negotiate a character
> > set. The RFB spec says apps should use latin-1. In reality few, if any,
> > impl
Hi,
> The VNC protocol is way too crude. It is limited to transferring
> plain text, and provides no way to specify or negotiate a character
> set. The RFB spec says apps should use latin-1. In reality few, if any,
> impls do charset conversion so most Linux impls will be sending UTF8
> while Wi
On Tue, Feb 02, 2021 at 01:31:23PM +0100, BALATON Zoltan wrote:
> On Tue, 2 Feb 2021, Gerd Hoffmann wrote:
> > > > My preferred solution is to have QEMU leverage the existing SPICE
> > > > guest agent if at all possible, because that's already widely
> > > > available in existing guest OS.
> > >
>
On Tue, 2 Feb 2021, Gerd Hoffmann wrote:
My preferred solution is to have QEMU leverage the existing SPICE
guest agent if at all possible, because that's already widely
available in existing guest OS.
I think spice is not as widely available as VNC (or even Synergy) so the
idea to strip one of
On Tue, Feb 02, 2021 at 11:17:09AM +, Daniel P. Berrangé wrote:
> On Tue, Feb 02, 2021 at 12:10:15PM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > > How do you rate-limit intelligently to avoid overflowing the guest
> > > > keyboard buffers?
> > >
> > > Like I said earlier in this thread,
> > My preferred solution is to have QEMU leverage the existing SPICE
> > guest agent if at all possible, because that's already widely
> > available in existing guest OS.
>
> I think spice is not as widely available as VNC (or even Synergy) so the
> idea to strip one of those down to just a guest
On Tue, Feb 02, 2021 at 12:10:15PM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > > How do you rate-limit intelligently to avoid overflowing the guest
> > > keyboard buffers?
> >
> > Like I said earlier in this thread, this is a big problem with
> > keyboard injection.
>
> It's a solved problem thou
Hi,
> > How do you rate-limit intelligently to avoid overflowing the guest keyboard
> > buffers?
>
> Like I said earlier in this thread, this is a big problem with
> keyboard injection.
It's a solved problem though, the qemu vnc server has throttling
implemented already. There even is an opt
On Mon, 1 Feb 2021, Daniel P. Berrangé wrote:
IMHO keyboard injection is only barely better than no clipboard
at all, and I don't think we should settle for that as a solution.
From this discussion it looks like doing keyboard injection is not a good
solution as it has more problems than what
On Mon, Feb 01, 2021 at 06:28:38PM +0100, Christophe de Dinechin wrote:
>
>
> > On 1 Feb 2021, at 17:56, Daniel P. Berrangé wrote:
> >
> > On Mon, Feb 01, 2021 at 05:31:52PM +0100, Christophe de Dinechin wrote:
> >>
> >>
> >>
> >> But the VNC clipboard protocol is not scancode based. So wher
> On 1 Feb 2021, at 17:56, Daniel P. Berrangé wrote:
>
> On Mon, Feb 01, 2021 at 05:31:52PM +0100, Christophe de Dinechin wrote:
>>
>>
>>> On 1 Feb 2021, at 16:51, Daniel P. Berrangé wrote:
>>>
>>> On Mon, Feb 01, 2021 at 04:27:43PM +0100, Christophe de Dinechin wrote:
> On
> On 29 Jan 2021, at 16:04, Gerd Hoffmann wrote:
>
> Hi,
>
>> Unless we para-virtualize the keyboard?
>
> The main advantage of paste via key events is that it doesn't require
> guest support.
The main disadvantage, though, is that it does not work at all ;-)
Imagine pasting Ademar's favo
On Mon, Feb 01, 2021 at 05:31:52PM +0100, Christophe de Dinechin wrote:
>
>
> > On 1 Feb 2021, at 16:51, Daniel P. Berrangé wrote:
> >
> > On Mon, Feb 01, 2021 at 04:27:43PM +0100, Christophe de Dinechin wrote:
> >>
> >>
> >>> On 29 Jan 2021, at 15:32, Daniel P. Berrangé wrote:
> >>>
> >>>
> On 1 Feb 2021, at 16:51, Daniel P. Berrangé wrote:
>
> On Mon, Feb 01, 2021 at 04:27:43PM +0100, Christophe de Dinechin wrote:
>>
>>
>>> On 29 Jan 2021, at 15:32, Daniel P. Berrangé wrote:
>>>
>>> On Fri, Jan 29, 2021 at 03:19:45PM +0100, Christophe de Dinechin wrote:
> On
On Mon, Feb 01, 2021 at 04:27:43PM +0100, Christophe de Dinechin wrote:
>
>
> > On 29 Jan 2021, at 15:32, Daniel P. Berrangé wrote:
> >
> > On Fri, Jan 29, 2021 at 03:19:45PM +0100, Christophe de Dinechin wrote:
> >>
> >>
> >>> On 29 Jan 2021, at 12:08, Daniel P. Berrangé wrote:
> >>>
> >>>
> On 29 Jan 2021, at 15:32, Daniel P. Berrangé wrote:
>
> On Fri, Jan 29, 2021 at 03:19:45PM +0100, Christophe de Dinechin wrote:
>>
>>
>>> On 29 Jan 2021, at 12:08, Daniel P. Berrangé wrote:
>>>
>>> On Fri, Jan 29, 2021 at 11:50:10AM +0100, Christophe de Dinechin wrote:
> O
Hi,
> Unless we para-virtualize the keyboard?
The main advantage of paste via key events is that it doesn't require
guest support. Requiring any kind of software in the guest (paravirt
keyboard driver, agent figuring the keymap, whatever else) kills that
advantage. And if we need guest cooper
On Fri, Jan 29, 2021 at 03:19:45PM +0100, Christophe de Dinechin wrote:
>
>
> > On 29 Jan 2021, at 12:08, Daniel P. Berrangé wrote:
> >
> > On Fri, Jan 29, 2021 at 11:50:10AM +0100, Christophe de Dinechin wrote:
> >>
> >>
> >>> On 29 Jan 2021, at 09:03, Gerd Hoffmann wrote:
> >>>
> >>> Hi,
> On 29 Jan 2021, at 12:08, Daniel P. Berrangé wrote:
>
> On Fri, Jan 29, 2021 at 11:50:10AM +0100, Christophe de Dinechin wrote:
>>
>>
>>> On 29 Jan 2021, at 09:03, Gerd Hoffmann wrote:
>>>
>>> Hi,
>>>
> (1) Have some guest agent (spice does it that way).
>Advantage: more flex
> On 29 Jan 2021, at 12:49, Gerd Hoffmann wrote:
>
> Hi,
>
>> - What I'm suggesting is that qemu-vnc could then switch to simply
>> relaying VNC traffic to that in-guest server. You'd get the smart update
>> algorithm that Apple has put in place to deal with transparency and the
>> like, as
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é
> 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
Hi,
> - What I'm suggesting is that qemu-vnc could then switch to simply
> relaying VNC traffic to that in-guest server. You'd get the smart update
> algorithm that Apple has put in place to deal with transparency and the
> like, as well as a level of guest OS integration that would otherwise be
On Fri, Jan 29, 2021 at 12:18:19AM +0400, Marc-André Lureau wrote:
> Hi
>
> On Thu, Jan 28, 2021 at 9:14 PM Gerd Hoffmann wrote:
>
> > Hi folks,
> >
> > I'm looking for a good way to implement cut+paste support for vnc.
> >
> > The vnc core protocol has support for text/plain cut+paste, and th
Hi
On Fri, Jan 29, 2021 at 4:03 PM Gerd Hoffmann wrote:
>
> Hi,
>
> > - the spice protocol had a number of iterations to fix some races. It would
> > be great not to repeat the same mistakes, and I don't know if VNC have the
> > same flaws or not.
>
> # grep CAP.*CLIPBOARD.*, /usr/include/spice
Hi,
> - the spice protocol had a number of iterations to fix some races. It would
> be great not to repeat the same mistakes, and I don't know if VNC have the
> same flaws or not.
# grep CAP.*CLIPBOARD.*, /usr/include/spice-1/spice/vd_agent.h
VD_AGENT_CAP_CLIPBOARD,
VD_AGENT_CAP_CLIPBO
Hi
On Fri, Jan 29, 2021 at 3:24 PM Daniel P. Berrangé wrote:
>
> On Fri, Jan 29, 2021 at 12:18:19AM +0400, Marc-André Lureau wrote:
> > Hi
> >
> > On Thu, Jan 28, 2021 at 9:14 PM Gerd Hoffmann wrote:
> >
> > > Hi folks,
> > >
> > > I'm looking for a good way to implement cut+paste support for
On Fri, Jan 29, 2021 at 11:50:10AM +0100, Christophe de Dinechin wrote:
>
>
> > On 29 Jan 2021, at 09:03, Gerd Hoffmann wrote:
> >
> > Hi,
> >
> >>> (1) Have some guest agent (spice does it that way).
> >>> Advantage: more flexible, allows more features.
> >>> Disadvantage: requires a
On Fri, Jan 29, 2021 at 12:34:32PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Jan 29, 2021 at 12:28 PM Gerd Hoffmann wrote:
>
> >
> > Well. That is a completely different level of desktop integration.
> > It surely makes sense to have that, and dbus-over-vsock looks like
> > a reasonable
> On 29 Jan 2021, at 09:03, Gerd Hoffmann wrote:
>
> Hi,
>
>>> (1) Have some guest agent (spice does it that way).
>>> Advantage: more flexible, allows more features.
>>> Disadvantage: requires agent in the guest.
>>
>> What about running the option to relay data to a VNC server in
On Fri, Jan 29, 2021 at 12:34:32PM +0400, Marc-André Lureau wrote:
> Hi
>
> On Fri, Jan 29, 2021 at 12:28 PM Gerd Hoffmann wrote:
>
> >
> > Well. That is a completely different level of desktop integration.
> > It surely makes sense to have that, and dbus-over-vsock looks like
> > a reasonable
On Thu, Jan 28, 2021 at 06:57:24PM +0100, Laszlo Ersek wrote:
> On 01/28/21 18:12, Gerd Hoffmann wrote:
> > Hi folks,
> >
> > I'm looking for a good way to implement cut+paste support for vnc.
> >
> > The vnc core protocol has support for text/plain cut+paste, and there
> > is an extension addi
Hi
On Fri, Jan 29, 2021 at 12:28 PM Gerd Hoffmann wrote:
>
> Well. That is a completely different level of desktop integration.
> It surely makes sense to have that, and dbus-over-vsock looks like
> a reasonable choice.
>
(using vsock & dbus also goes in the direction where UIs and remote serv
Hi,
> Some things I keep in mind:
> - the spice protocol had a number of iterations to fix some races. It would
> be great not to repeat the same mistakes, and I don't know if VNC have the
> same flaws or not.
Sure. One of the reasons I've started this discussion ;)
> - the GNOME desktop is w
Hi,
> Just a random thought: the guest should not be able to sniff, steal, or
> overwrite host-side clipboard (selection) content, without the host user
> explicitly requesting a clipboard operation.
Sure. vncviewer has command line options for that, and you can also
change it at runtime (F8 -
Hi,
> > (1) Have some guest agent (spice does it that way).
> > Advantage: more flexible, allows more features.
> > Disadvantage: requires agent in the guest.
>
> What about running the option to relay data to a VNC server in the
> guest if there is one running? In other words, using
Christophe
(Typos are from my iPhone)
> Le 28 janv. 2021 à 21:24, Marc-André Lureau a
> écrit :
>
>
> Hi
>
>> On Thu, Jan 28, 2021 at 9:14 PM Gerd Hoffmann wrote:
>> Hi folks,
>>
>> I'm looking for a good way to implement cut+paste support for vnc.
>>
>> The vnc core protocol has supp
On Thu, Jan 28, 2021 at 05:35:04PM +, Daniel P. Berrangé wrote:
> On Thu, Jan 28, 2021 at 06:12:24PM +0100, Gerd Hoffmann wrote:
> > Hi folks,
> >
> > I'm looking for a good way to implement cut+paste support for vnc.
> >
> > The vnc core protocol has support for text/plain cut+paste, and t
On Fri, 29 Jan 2021, Marc-André Lureau wrote:
I also had recently some thoughts about how to implement clipboard sharing
in a more general way for QEMU.
I admit I like Christophe's suggestion ("it's somebody else problem"), but
it falls short to me as I don't know of a common open-source remotin
Hi
On Thu, Jan 28, 2021 at 9:14 PM Gerd Hoffmann wrote:
> Hi folks,
>
> I'm looking for a good way to implement cut+paste support for vnc.
>
> The vnc core protocol has support for text/plain cut+paste, and there
> is an extension adding support for other formats. That'll cover one
> part of
On 01/28/21 18:12, Gerd Hoffmann wrote:
> Hi folks,
>
> I'm looking for a good way to implement cut+paste support for vnc.
>
> The vnc core protocol has support for text/plain cut+paste, and there
> is an extension adding support for other formats. That'll cover one
> part of the problem, exch
> On 28 Jan 2021, at 18:12, Gerd Hoffmann wrote:
>
> Hi folks,
>
> I'm looking for a good way to implement cut+paste support for vnc.
>
> The vnc core protocol has support for text/plain cut+paste, and there
> is an extension adding support for other formats. That'll cover one
> part of th
On Thu, Jan 28, 2021 at 06:12:24PM +0100, Gerd Hoffmann wrote:
> Hi folks,
>
> I'm looking for a good way to implement cut+paste support for vnc.
>
> The vnc core protocol has support for text/plain cut+paste, and there
> is an extension adding support for other formats. That'll cover one
> pa
Hi folks,
I'm looking for a good way to implement cut+paste support for vnc.
The vnc core protocol has support for text/plain cut+paste, and there
is an extension adding support for other formats. That'll cover one
part of the problem, exchanging cut+paste data between vnc client and
qemu vnc
61 matches
Mail list logo
