public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Markus Frank <m.frank@proxmox.com>
Subject: Re: [pve-devel] [PATCH docs v2 3/3] vnc-clipboard: change 'live-migration not working' note
Date: Thu, 8 Jan 2026 16:31:51 +0100	[thread overview]
Message-ID: <bb3d53e6-386d-457f-83b6-6bb8a9d9a10e@proxmox.com> (raw)
In-Reply-To: <20260108101103.82029-4-m.frank@proxmox.com>

Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>

On 1/8/26 11:11 AM, Markus Frank wrote:
> The live-migration feature now works with QEMU 10.1:
> 5d56bff11e ("ui/vdagent: add migration support")
> 
> Signed-off-by: Markus Frank <m.frank@proxmox.com>
> ---
> v2:
> * update live-migration limitation note instead of removing it entirely
> 
>   qm.adoc | 9 +++------
>   1 file changed, 3 insertions(+), 6 deletions(-)
> 
> diff --git a/qm.adoc b/qm.adoc
> index eb6ab4d..6a46d23 100644
> --- a/qm.adoc
> +++ b/qm.adoc
> @@ -1030,13 +1030,10 @@ SPICE, virtio or virgl, you'll need to choose which clipboard to use.
>   This is because the default *SPICE* clipboard will be replaced by the
>   *VNC* clipboard, if `clipboard` is set to `vnc`.
>   
> -// TODO: Change NOTE below when live-migration patch is packaged in pve-qemu:
> -// https://lists.gnu.org/archive/html/qemu-devel/2025-05/msg05656.html
>   NOTE: In order to enable the VNC clipboard, QEMU is configured to use the
> -qemu-vdagent device.
> -https://lists.gnu.org/archive/html/qemu-devel/2021-08/msg05393.html[Currently,
> -the qemu-vdagent device does not support live migration.] This means that a VM
> -with an enabled VNC clipboard cannot be live-migrated at the moment.
> +qemu-vdagent device. Live migration support for this device was added with
> +QEMU Version 10.1. VMs running on a QEMU or machine version below 10.1
> +with an enabled VNC clipboard cannot be live-migrated.
>   
>   [[qm_usb_passthrough]]
>   USB Passthrough



_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel


  reply	other threads:[~2026-01-08 15:32 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-08 10:10 [pve-devel] [PATCH qemu-server/manager/docs v2 0/3] live-migration with VNC clipboard Markus Frank
2026-01-08 10:10 ` [pve-devel] [PATCH qemu-server v2 1/3] vga: allow live-migration with clipboard Markus Frank
2026-01-08 15:20   ` Dominik Csapak
2026-01-09 13:19     ` Fiona Ebner
2026-01-09 13:17   ` [pve-devel] applied: " Fiona Ebner
2026-01-08 10:10 ` [pve-devel] [PATCH pve-manager v2 2/3] ui: display: update 'live-migration with VNC-clipboard not working' note Markus Frank
2026-01-08 15:24   ` Dominik Csapak
2026-01-09 13:26   ` [pve-devel] applied: " Fiona Ebner
2026-01-08 10:10 ` [pve-devel] [PATCH docs v2 3/3] vnc-clipboard: change 'live-migration " Markus Frank
2026-01-08 15:31   ` Dominik Csapak [this message]
2026-01-09 13:34   ` [pve-devel] applied: " Fiona Ebner

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=bb3d53e6-386d-457f-83b6-6bb8a9d9a10e@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=m.frank@proxmox.com \
    --cc=pve-devel@lists.proxmox.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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal