all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Filip Schauer <f.schauer@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v3 qemu-server] Prevent starting a 32-bit VM using a 64-bit OVMF BIOS
Date: Wed, 13 Dec 2023 18:00:16 +0100	[thread overview]
Message-ID: <84fbc31a-e0d4-40ae-866e-5428d77c45cb@proxmox.com> (raw)
In-Reply-To: <71e00bdc-335e-45ba-bc61-60ca3817d6c4@proxmox.com>

Patch v5 is available:

https://lists.proxmox.com/pipermail/pve-devel/2023-December/061079.html

On 12/12/2023 12:12, Fiona Ebner wrote:
> Am 12.12.23 um 11:58 schrieb Filip Schauer:
>> Instead of starting a VM with a 32-bit CPU type and a 64-bit OVMF image,
>> throw an error before starting the VM telling the user that OVMF is not
>> supported on 32-bit CPU types.
>>
>> Signed-off-by: Filip Schauer <f.schauer@proxmox.com>
>> ---
>> Changes since v2:
>> * Simplify the check whether a 32-bit CPU type is used in combination
>>    with OVMF
>>
> Yes, it's much nicer than extending the EFI-related functions with new
> parameters :)
>
>>   PVE/QemuServer.pm | 13 +++++++++++++
>>   1 file changed, 13 insertions(+)
>>
>> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
>> index 2063e66..b25a3cd 100644
>> --- a/PVE/QemuServer.pm
>> +++ b/PVE/QemuServer.pm
>> @@ -3570,6 +3570,16 @@ my sub print_ovmf_drive_commandlines {
>>       return ("if=pflash,unit=0,format=raw,readonly=on,file=$ovmf_code", $var_drive_str);
>>   }
>>   
>> +my @cputypes_32bit = (
>> +    '486',
>> +    'pentium',
>> +    'pentium2',
>> +    'pentium3',
>> +    'coreduo',
>> +    'athlon',
>> +    'kvm32',
>> +    'qemu32',
>> +);
> I'd like to put this list in CPUConfig.pm and have a small helper
> function there. The QemuServer.pm module already has way too many
> functions and variables ;) And since it's only used for lookup, maybe
> using a hash is better?
>
> A short comment in the commit message about how you got the list would
> be nice too (I just checked for absence of CPUID_EXT2_LM in
> target/i386/cpu.c to verify your list).
>
>>   sub config_to_command {
>>       my ($storecfg, $vmid, $conf, $defaults, $forcemachine, $forcecpu,
>>           $pbs_backing) = @_;
>> @@ -3689,6 +3699,9 @@ sub config_to_command {
>>       }
>>   
>>       if ($conf->{bios} && $conf->{bios} eq 'ovmf') {
>> +	die "OVMF (UEFI) BIOS is not supported on 32-bit CPU types\n"
>> +	    if ($conf->{cpu} && first {$_ eq $conf->{cpu}} @cputypes_32bit);
> Style nit: usually we don't have parentheses for post-if




      reply	other threads:[~2023-12-13 17:00 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-12 10:58 Filip Schauer
2023-12-12 11:12 ` Fiona Ebner
2023-12-13 17:00   ` Filip Schauer [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=84fbc31a-e0d4-40ae-866e-5428d77c45cb@proxmox.com \
    --to=f.schauer@proxmox.com \
    --cc=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 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