From: Fiona Ebner <f.ebner@proxmox.com>
To: Markus Frank <m.frank@proxmox.com>,
Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v1 1/3] vga: allow live-migration with clipboard
Date: Wed, 19 Nov 2025 15:46:18 +0100 [thread overview]
Message-ID: <3085cf3f-da2f-45a2-a8bb-25a0ca78345e@proxmox.com> (raw)
In-Reply-To: <aa8142eb-9b90-490f-9c61-8cd1cf622bdd@proxmox.com>
Am 19.11.25 um 3:17 PM schrieb Markus Frank:
> On 2025-11-17 17:43, Fiona Ebner wrote:
>> Am 17.11.25 um 5:41 PM schrieb Fiona Ebner:
>>> Am 17.11.25 um 5:28 PM schrieb Markus Frank:
>>>> The live-migration feature now works with qemu's upstream commit:
>>>> 5d56bff11e ("ui/vdagent: add migration support")
>>>>
>>>> Signed-off-by: Markus Frank <m.frank@proxmox.com>
>>>> ---
>>>> src/PVE/API2/Qemu.pm | 5 -----
>>>> src/PVE/QemuMigrate.pm | 5 -----
>>>> src/PVE/QemuServer.pm | 2 +-
>>>> 3 files changed, 1 insertion(+), 11 deletions(-)
>>>>
>>>> diff --git a/src/PVE/API2/Qemu.pm b/src/PVE/API2/Qemu.pm
>>>> index 02f5caec..314b6a48 100644
>>>> --- a/src/PVE/API2/Qemu.pm
>>>> +++ b/src/PVE/API2/Qemu.pm
>>>> @@ -5267,11 +5267,6 @@ __PACKAGE__->register_method({
>>>> my ($local_resources, $mapped_resources,
>>>> $missing_mappings_by_node) =
>>>>
>>>> PVE::QemuMigrate::Helpers::check_local_resources($vmconf, $res-
>>>> >{running}, 1);
>>>> - my $vga = PVE::QemuServer::parse_vga($vmconf->{vga});
>>>> - if ($res->{running} && $vga->{'clipboard'} && $vga-
>>>> >{'clipboard'} eq 'vnc') {
>>>> - push $local_resources->@*, "clipboard=vnc";
>>>> - }
>>>
>>> I suppose this depends on having machine version >= 10.1, or? (In any
>>> case QEMU binary version >= 10.1 but that is implied by machine
>>> version >= 10.1)
>
> Yes, it needs QEMU version >= 10.1. However, when I set the machine
> version to < 10.1
> (tested with version 6.2), the migration still works fine and the
> clipboard still functions on the other node.
> It seems that the machine version is unrelated here.
>
> I suppose it would be better to check the QEMU version using
> get_running_qemu_version, wouldn't it?
But what if the target node has an older binary version? It won't
understand the new data in the migration stream, right? Such changes to
the migration stream should always be protected by machine version AFAIK
and it smells like a bug in QEMU if it isn't protected like that in QEMU
internally.
Could you test what happens when the target is an older binary?
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-11-19 14:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-17 16:26 [pve-devel] [PATCH qemu-server/manager/docs v1 0/3] Live-Migration with VNC clipboard Markus Frank
2025-11-17 16:26 ` [pve-devel] [PATCH qemu-server v1 1/3] vga: allow live-migration with clipboard Markus Frank
2025-11-17 16:42 ` Fiona Ebner
2025-11-17 16:43 ` Fiona Ebner
2025-11-19 14:18 ` Markus Frank
2025-11-19 14:46 ` Fiona Ebner [this message]
2025-11-17 16:26 ` [pve-devel] [PATCH manager v1 2/3] ui: display: remove 'vncMigration' hint Markus Frank
2025-11-17 16:26 ` [pve-devel] [PATCH docs v1 3/3] clipboard: remove 'live-migration not possible' note Markus Frank
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=3085cf3f-da2f-45a2-a8bb-25a0ca78345e@proxmox.com \
--to=f.ebner@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