From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com, Erik Fastermann <e.fastermann@proxmox.com>
Subject: applied: [PATCH qemu-server v2] remote migration: validate custom CPU configs
Date: Tue, 7 Jul 2026 22:31:37 +0200 [thread overview]
Message-ID: <178345629656.4018398.12618109865568428426.b4-ty@b4> (raw)
In-Reply-To: <20260701135229.225599-1-e.fastermann@proxmox.com>
On Wed, 01 Jul 2026 15:52:29 +0200, Erik Fastermann wrote:
> Previously, a remote migration would fail with a cryptic error message
> if a custom CPU model was selected that did not exist on the target
> server. Furthermore, no validation was performed to ensure that the
> custom CPU definitions matched between the source and target.
>
> Fix this by comparing the CPU configurations before initiating the
> migration and aborting early if they do not match.
>
> [...]
Applied, thanks!
[1/1] remote migration: validate custom CPU configs
https://git.proxmox.com/?p=qemu-server.git;a=commitdiff;h=7f57a7c46cbd73abc41dd855ffa503d4e7d57cb2
prev parent reply other threads:[~2026-07-07 20:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-07-01 13:52 [PATCH qemu-server v2] remote migration: validate custom CPU configs Erik Fastermann
2026-07-06 14:01 ` Dominik Csapak
2026-07-07 20:31 ` Thomas Lamprecht [this message]
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=178345629656.4018398.12618109865568428426.b4-ty@b4 \
--to=t.lamprecht@proxmox.com \
--cc=e.fastermann@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