public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Noel Ullreich <n.ullreich@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH qemu-server v2] fix #4378: standardized error for ovmf files
Date: Fri, 13 Jan 2023 11:20:05 +0100	[thread overview]
Message-ID: <20230113102005.4atiwq4jx3pdw2bg@fwblub> (raw)
In-Reply-To: <20230112105702.26599-1-n.ullreich@proxmox.com>

On Thu, Jan 12, 2023 at 11:57:02AM +0100, Noel Ullreich wrote:
> The error messages for missing OVMF_CODE and OVMF_VARS files were
> inconsistent as well as the error for the missing base var file not
> telling you the expected path.
> 
> Signed-off-by: Noel Ullreich <n.ullreich@proxmox.com>
> ---
>  changes from v1:
>  * rebased to account for move from sub config_to_command to sub
>    print_ovmf_drive_commandlines
>  * left out check for existing EFI vars image in sub config_to_command
>    since it was redundant
> 
>  PVE/QemuServer.pm | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
> 
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index d94fe5a..cfdd2b2 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -3522,7 +3522,7 @@ my sub print_ovmf_drive_commandlines {
>      my $d = $conf->{efidisk0} ? parse_drive('efidisk0', $conf->{efidisk0}) : undef;
>  
>      my ($ovmf_code, $ovmf_vars) = get_ovmf_files($arch, $d, $q35);
> -    die "uefi base image '$ovmf_code' not found\n" if ! -f $ovmf_code;
> +    die "EFI base image '$ovmf_code' not found\n" if ! -f $ovmf_code;

I agree with Thomas' v1 reply that these checks can just happen once
directly in `get_ovmf_files` for both files, even if we don't always
fetch both paths, since in practice you either need both or none
available anyway, and under normal circumstances they won't be missing
anyway.

Can you please move them?

>  
>      my $var_drive_str = "if=pflash,unit=1,id=drive-efidisk0";
>      if ($d) {
> @@ -8070,7 +8070,7 @@ sub get_efivars_size {
>      $efidisk //= $conf->{efidisk0} ? parse_drive('efidisk0', $conf->{efidisk0}) : undef;
>      my $smm = PVE::QemuServer::Machine::machine_type_is_q35($conf);
>      my (undef, $ovmf_vars) = get_ovmf_files($arch, $efidisk, $smm);
> -    die "uefi vars image '$ovmf_vars' not found\n" if ! -f $ovmf_vars;
> +    die "EFI vars image '$ovmf_vars' not found\n" if ! -f $ovmf_vars;
>      return -s $ovmf_vars;
>  }
>  
> @@ -8098,7 +8098,7 @@ sub create_efidisk($$$$$$$) {
>      my ($storecfg, $storeid, $vmid, $fmt, $arch, $efidisk, $smm) = @_;
>  
>      my (undef, $ovmf_vars) = get_ovmf_files($arch, $efidisk, $smm);
> -    die "EFI vars default image not found\n" if ! -f $ovmf_vars;
> +    die "EFI vars default image '$ovmf_vars' not found\n" if ! -f $ovmf_vars;
>  
>      my $vars_size_b = -s $ovmf_vars;
>      my $vars_size = PVE::Tools::convert_size($vars_size_b, 'b' => 'kb');
> -- 
> 2.30.2




      reply	other threads:[~2023-01-13 10:20 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-12 10:57 Noel Ullreich
2023-01-13 10:20 ` Wolfgang Bumiller [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=20230113102005.4atiwq4jx3pdw2bg@fwblub \
    --to=w.bumiller@proxmox.com \
    --cc=n.ullreich@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