From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>,
Markus Frank <m.frank@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v2 1/3] vga: allow live-migration with clipboard
Date: Fri, 9 Jan 2026 14:19:43 +0100 [thread overview]
Message-ID: <a223c392-7de3-48ce-8b91-97bc8ca1b105@proxmox.com> (raw)
In-Reply-To: <ddf6dd16-8c9e-4221-8ccf-bce6d862273c@proxmox.com>
Am 08.01.26 um 4:20 PM schrieb Dominik Csapak:
> 2 high level notes (but not blocker):
>
> * would it maybe make sense to pull the 'get_current_qemu_machine' out
> so other parts of the api/code can reuse that?
> i guess we'll maybe have more of such checks in the future, and having
> the version already available at e.g. the top level of the api call
> could make sense. This can ofc also be done when we actually need it
Can easily be done when another user shows up.
> * afaics the checks in QemuMigrate and the api are identical, would
> it make sense to factor them out, so they don't accidentally
> diverge? (Are there maybe even more places where we check this?)
I didn't see any other places and the check is very unlikely to change
in the future and two times two lines is really not much, so I applied
it as-is with your R-B, thanks!
> Aside from these (minor) changes consider this:
>
> Reviewed-by: Dominik Csapak <d.csapak@proxmox.com>
_______________________________________________
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:[~2026-01-09 13:20 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 [this message]
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
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=a223c392-7de3-48ce-8b91-97bc8ca1b105@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.