public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager] 8to9: adapt to changed signature of get_vm_machine()
Date: Wed, 21 Oct 2026 13:29:01 +0200	[thread overview]
Message-ID: <f22ad923-5e71-4f87-9f14-56f36b2e120b@proxmox.com> (raw)
In-Reply-To: <4680ba6c-fd9e-47b3-b3b7-cc4ee97fca14@proxmox.com>

Am 23.09.26 um 11:06 AM schrieb Fiona Ebner:
> Am 29.01.26 um 2:25 PM schrieb Fiona Ebner:
>> The signature change in qemu-server does not lead to any breakage,
>> because the function still looks at $conf->{arch}. Still, it should be
>> adapted.
>>
>> Reported-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
>> Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
>> ---
>>
>> Dependency bump for qemu-server needed!
> 
> Ping. Still applies and the bump is already covered now :)
> 

Ping. Could somebody give me a review here?

>>
>>  PVE/CLI/pve8to9.pm | 7 ++-----
>>  1 file changed, 2 insertions(+), 5 deletions(-)
>>
>> diff --git a/PVE/CLI/pve8to9.pm b/PVE/CLI/pve8to9.pm
>> index 0c4b2343..662ee943 100644
>> --- a/PVE/CLI/pve8to9.pm
>> +++ b/PVE/CLI/pve8to9.pm
>> @@ -931,7 +931,7 @@ my sub check_qemu_machine_versions {
>>          my $conf = PVE::QemuConfig->load_config($vmid);
>>  
>>          # first, actually configured machine version
>> -        my $machine_type = PVE::QemuServer::Machine::get_vm_machine($conf, undef, $conf->{arch});
>> +        my $machine_type = PVE::QemuServer::Machine::get_vm_machine($conf);
>>          if (
>>              PVE::QemuServer::Machine::extract_version($machine_type) # no version means latest
>>              && !PVE::QemuServer::Machine::is_machine_version_at_least($machine_type, @baseline)
>> @@ -942,9 +942,7 @@ my sub check_qemu_machine_versions {
>>          # second, if hibernated, running machine version
>>          if ($conf->{vmstate}) {
>>              my $machine_type = PVE::QemuServer::Machine::get_vm_machine(
>> -                $conf,
>> -                $conf->{runningmachine},
>> -                $conf->{arch},
>> +                $conf, $conf->{runningmachine},
>>              );
>>              if (
>>                  PVE::QemuServer::Machine::extract_version($machine_type) # no version means latest
>> @@ -964,7 +962,6 @@ my sub check_qemu_machine_versions {
>>                  my $machine_type = PVE::QemuServer::Machine::get_vm_machine(
>>                      $snap_conf,
>>                      $snap_conf->{runningmachine},
>> -                    $snap_conf->{arch},
>>                  );
>>                  if ( # no version means latest
>>                      PVE::QemuServer::Machine::extract_version($machine_type)




  reply	other threads:[~2026-10-21 11:29 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-29 13:26 [PATCH manager] 8to9: adapt to changed signature of get_vm_machine() Fiona Ebner
2026-09-23  9:05 ` Fiona Ebner
2026-10-21 11:29   ` Fiona Ebner [this message]
2026-10-21 12:15     ` 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=f22ad923-5e71-4f87-9f14-56f36b2e120b@proxmox.com \
    --to=f.ebner@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