From: Fiona Ebner <f.ebner@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server 4/8] machine: correctly select pve machine version for non pinned windows guests
Date: Thu, 6 Mar 2025 14:10:00 +0100 [thread overview]
Message-ID: <ecd1b69e-f381-4703-a1a2-2185f6e72500@proxmox.com> (raw)
In-Reply-To: <20250306104459.1272297-5-d.csapak@proxmox.com>
Am 06.03.25 um 11:44 schrieb Dominik Csapak:
> when we don't have a specific machine version on a windows guest, we use
> the creation meta info to pin the machine version. Currently we always
> append the pve machine version from the current installed kvm version,
> which is not necessarily the version we pinned the guest to.
>
> Instead, use either the info from the creation meta info if it exists,
> or use 'pve0'.
>
> For non-windows machines, we used the current QEMU machine version so we
> should use the pve machine version from that too.
>
> Signed-off-by: Dominik Csapak <d.csapak@proxmox.com>
> ---
> PVE/QemuServer/Machine.pm | 13 +++++++++----
> 1 file changed, 9 insertions(+), 4 deletions(-)
>
> diff --git a/PVE/QemuServer/Machine.pm b/PVE/QemuServer/Machine.pm
> index f1acde8f..e3da8e21 100644
> --- a/PVE/QemuServer/Machine.pm
> +++ b/PVE/QemuServer/Machine.pm
> @@ -237,14 +237,19 @@ sub get_vm_machine {
> if (PVE::QemuServer::Helpers::min_version($meta->{'creation-qemu'}, 9, 1)) {
> # need only major.minor
> ($base_version) = ($meta->{'creation-qemu'} =~ m/^(\d+.\d+)/);
> + # append pve machine version if we have one
> + if (my $pvever = $meta->{'creation-pve-machine'}) {
> + $base_version .= "+pve$pvever"
Since this is only the fallback handling for the rare edge case where no
explicit machine version is set for a Windows guest, not sure if it's
even worth doing this. I.e. can we just avoid the additional meta
property and always use pve0 here? Did you intend any other use for the
creation-pve-machine?
Further below we already have:
> # for version-pinned machines that do not include a pve-version (e.g.
> # pc-q35-4.1), we assume 0 to keep them stable in case we bump
> $machine .= '+pve0';
so let's just follow this here too?
> + }
> }
> }
> $machine = windows_get_pinned_machine_version($machine, $base_version, $kvmversion);
> + } else{
> + $arch //= 'x86_64';
> + $machine ||= default_machine_for_arch($arch);
> + my $pvever = get_pve_version($kvmversion);
> + $machine .= "+pve$pvever";
> }
> - $arch //= 'x86_64';
> - $machine ||= default_machine_for_arch($arch);
> - my $pvever = get_pve_version($kvmversion);
> - $machine .= "+pve$pvever";
> }
>
> if ($machine !~ m/\+pve\d+?(?:\.pxe)?$/) {
_______________________________________________
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-03-06 13:10 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-06 10:44 [pve-devel] [PATCH qemu-server 0/8] disable S3/S4 power states by default Dominik Csapak
2025-03-06 10:44 ` [pve-devel] [RFC PATCH qemu-server 1/8] tests: cfg2cmd: pin QEMU version Dominik Csapak
2025-03-06 12:00 ` Fiona Ebner
2025-03-06 12:07 ` Dominik Csapak
2025-03-06 12:43 ` Fiona Ebner
2025-03-06 10:44 ` [pve-devel] [PATCH qemu-server 2/8] config to command: add one '-global' option for each flag Dominik Csapak
2025-03-06 12:13 ` Fiona Ebner
2025-03-06 12:15 ` Dominik Csapak
2025-03-06 12:55 ` Fiona Ebner
2025-03-07 9:54 ` Dominik Csapak
2025-03-07 10:00 ` Fiona Ebner
2025-03-07 10:05 ` Dominik Csapak
2025-03-07 10:14 ` Fiona Ebner
2025-03-06 10:44 ` [pve-devel] [PATCH qemu-server 3/8] meta info: also add current pve-machine version Dominik Csapak
2025-03-06 10:44 ` [pve-devel] [PATCH qemu-server 4/8] machine: correctly select pve machine version for non pinned windows guests Dominik Csapak
2025-03-06 13:10 ` Fiona Ebner [this message]
2025-03-06 13:36 ` Dominik Csapak
2025-03-06 14:10 ` Fiona Ebner
2025-03-06 14:14 ` Fiona Ebner
2025-03-06 14:15 ` Dominik Csapak
2025-03-06 14:20 ` Fiona Ebner
2025-03-07 9:55 ` Dominik Csapak
2025-03-06 10:44 ` [pve-devel] [PATCH qemu-server 5/8] machine: incorporate pve machine version when pinning " Dominik Csapak
2025-03-06 14:32 ` Fiona Ebner
2025-03-07 9:58 ` Dominik Csapak
2025-03-07 10:06 ` Fiona Ebner
2025-03-06 10:44 ` [pve-devel] [PATCH qemu-server 6/8] machine: add S3/S4 power state properties Dominik Csapak
2025-03-06 14:52 ` Fiona Ebner
2025-03-07 10:02 ` Dominik Csapak
2025-03-07 10:10 ` Fiona Ebner
2025-03-06 10:44 ` [pve-devel] [PATCH qemu-server 7/8] machine: bump pve machine version and reverse the s3/s4 defaults Dominik Csapak
2025-03-06 15:04 ` Fiona Ebner
2025-03-06 10:44 ` [pve-devel] [PATCH qemu-server 8/8] tests: cfg2cmd: add test for windows machine pinning from meta info Dominik Csapak
2025-03-06 15:10 ` Fiona Ebner
2025-03-07 14:46 ` [pve-devel] [PATCH qemu-server 0/8] disable S3/S4 power states by default Dominik Csapak
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=ecd1b69e-f381-4703-a1a2-2185f6e72500@proxmox.com \
--to=f.ebner@proxmox.com \
--cc=d.csapak@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.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal