public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
	Filip Schauer <f.schauer@proxmox.com>
Subject: [pve-devel] partially-applied-series: [PATCH-SERIES v8 qemu-server, common] Prevent starting a 32-bit VM using a 64-bit OVMF BIOS
Date: Fri, 8 Mar 2024 14:34:42 +0100	[thread overview]
Message-ID: <4d1317fa-a802-4d81-9f15-632d48b9008f@proxmox.com> (raw)
In-Reply-To: <20240221143317.134090-1-f.schauer@proxmox.com>

Am 21/02/2024 um 15:33 schrieb Filip Schauer:
> This patch series prevents starting a 32-bit VM using a 64-bit OVMF BIOS
> and makes the default value for 'kvm' during CPU hotplug consistent with
> the rest of the code. This is a breaking change for VMs with a different
> CPU architecture running on an x86_64 host.
> 
> Changes since v7:
> * Rename is_native to is_native_arch to be more explicit
> * Move get_default_cpu_type from Helpers to CPUConfig
> * Default to host architecture when no $arch is given to get_cpu_bitness
> * die with a message on hotplug of non x86_64 CPUs in print_cpu_device
> 
> Changes since v6:
> * Skip the CPU bitness check if $forcecpu is set
> * Take custom CPU types into account
> * Add a helper for getting the default CPU type
> * Unify the default value for 'kvm'
> * Move is_native from PVE::QemuServer to PVE::Tools
> 
> Changes since v5:
> * Refactor get_cpu_bitness to die instead of returning undef
> * Pass cputype instead of the entire vm config to get_cpu_bitness
> 
> Changes since v4:
> * Remove parentheses around post-if in get_cpu_bitness
> 
> Changes since v3:
> * Move the cputypes_32bit list from QemuServer.pm to CPUConfig.pm
> * Turn cputypes_32bit into a hash for lookup
> * Create a helper get_cpu_bitness function in CPUConfig.pm
> * Describe how the list of 32-bit CPU types was obtained
> 
> common:
> 
> Filip Schauer (1):
>   tools: add is_native_arch to compare the CPU architecture
> 
>  src/PVE/Tools.pm | 6 ++++++
>  1 file changed, 6 insertions(+)
> 
> qemu-server:
> 
> Filip Schauer (5):
>   cpu config: Add helper to get the default CPU type
>   Prevent starting a 32-bit VM using a 64-bit OVMF BIOS
>   Move is_native from PVE::QemuServer to PVE::Tools
>   Unify the default value for 'kvm'
>   cpu config: die on hotplug of non x86_64 CPUs
> 
>  PVE/QemuServer.pm           | 23 +++++++------
>  PVE/QemuServer/CPUConfig.pm | 64 ++++++++++++++++++++++++++++++++-----
>  2 files changed, 67 insertions(+), 20 deletions(-)
> 


applied patch 1 to 4, with the updated commit message for the 4th one, thanks!

Patch 5 has still some issues, see reply there.




      parent reply	other threads:[~2024-03-08 13:34 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-02-21 14:33 [pve-devel] " Filip Schauer
2024-02-21 14:33 ` [pve-devel] [PATCH common 1/1] tools: add is_native_arch to compare the CPU architecture Filip Schauer
2024-02-21 14:33 ` [pve-devel] [PATCH qemu-server 1/5] cpu config: add helper to get the default CPU type Filip Schauer
2024-02-21 14:33 ` [pve-devel] [PATCH qemu-server 2/5] prevent starting a 32-bit VM using a 64-bit OVMF BIOS Filip Schauer
2024-02-21 14:33 ` [pve-devel] [PATCH qemu-server 3/5] Move is_native from PVE::QemuServer to PVE::Tools Filip Schauer
2024-02-21 14:33 ` [pve-devel] [PATCH qemu-server 4/5] Unify the default value for 'kvm' Filip Schauer
2024-02-23 11:54   ` Filip Schauer
2024-02-21 14:33 ` [pve-devel] [PATCH qemu-server 5/5] cpu config: die on hotplug of non x86_64 CPUs Filip Schauer
2024-03-08 13:34   ` Thomas Lamprecht
2024-03-08 13:53     ` Fiona Ebner
2024-03-11 10:13       ` Filip Schauer
2024-03-08 13:34 ` 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=4d1317fa-a802-4d81-9f15-632d48b9008f@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=f.schauer@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