From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 1EA23816F for ; Thu, 2 Mar 2023 11:29:03 +0100 (CET) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 019462817 for ; Thu, 2 Mar 2023 11:28:33 +0100 (CET) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Thu, 2 Mar 2023 11:28:32 +0100 (CET) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 1E15E48D5E; Thu, 2 Mar 2023 11:28:32 +0100 (CET) Message-ID: <8f6365a4-7b85-1e49-07fa-a85a3ac897db@proxmox.com> Date: Thu, 2 Mar 2023 11:28:31 +0100 MIME-Version: 1.0 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:110.0) Gecko/20100101 Thunderbird/110.0 Content-Language: en-US To: Proxmox VE development discussion , Markus Frank References: <20221028123322.93142-1-m.frank@proxmox.com> <20221028123322.93142-7-m.frank@proxmox.com> From: Dominik Csapak In-Reply-To: <20221028123322.93142-7-m.frank@proxmox.com> Content-Type: text/plain; charset=UTF-8; format=flowed Content-Transfer-Encoding: 7bit X-SPAM-LEVEL: Spam detection results: 0 AWL 0.106 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment NICE_REPLY_A -0.09 Looks like a legit reply (A) SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record Subject: Re: [pve-devel] [PATCH docs v3 6/6] added noVNC clipboard documentation X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 02 Mar 2023 10:29:03 -0000 comments inline: On 10/28/22 14:33, Markus Frank wrote: > Signed-off-by: Markus Frank > --- > qm.adoc | 11 +++++++++++ > 1 file changed, 11 insertions(+) > > diff --git a/qm.adoc b/qm.adoc > index 4d0c7c4..3a575bc 100644 > --- a/qm.adoc > +++ b/qm.adoc > @@ -693,6 +693,17 @@ Selecting `serialX` as display 'type' disables the VGA output, and redirects > the Web Console to the selected serial port. A configured display 'memory' > setting will be ignored in that case. > > +You can enable the noVNC clipboard by setting 'clipboard' to 1. please add an example how to do that with e.g. qm set > +To use this, you need to install and enable spice-vdagent on the VM Guest: > +`apt install spice-vdagent` that should be a bit more generic, like 'install the spice guests tools' as with the option description, spice-vdagent is linux (and probably even debian) specific you can ofc mention the package, but in general that sentens should be valid for all guest os' > + > +Doing this will give you the ability to use the clipboard button of the novnc > +console. However, when using SPICE, you have to decide which clipboard you want > +to use, because the default SPICE clipboard implementation will be replaced by > +the qemu-vdagent implementation, which is used by noVNC. > +This means you cannot simply copy and paste into a SPICE session and instead > +need to use the noVNC button, when using SPICE with noVNC-clipboard. IMHO the sentences are too long, and a bit too technical. For an admin it should be enough to say that if they use a display hardware where they can use the SPICE console, only either the spice clipboard or novnc clipboard will work and that they must decide. (how the device is named and what replaces what is irrelevant for the admin, that's just an implementation detail and could be changing at any point in time, at which point the docs are wrong) > + > [[qm_usb_passthrough]] > USB Passthrough > ~~~~~~~~~~~~~~~