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>,
	Stefan Sterz <s.sterz@proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server v3] cd rom handling: return a clearer error when there is no cd rom drive
Date: Mon, 19 Dec 2022 16:17:37 +0100	[thread overview]
Message-ID: <8af727e1-b008-0142-eab1-031026a9c4d8@proxmox.com> (raw)
In-Reply-To: <20221219122343.288855-1-s.sterz@proxmox.com>

On 19/12/2022 13:23, Stefan Sterz wrote:
> when a vm is configured to use a physical cd rom drive but there is no
> such drive a cryptic "uninitialized value" error is thrown. this is
> due to `$path` not being defined in `sub
> print_drive_commandline_full` in this case. warn that no cd rom drive
> is available instead.
> 
> note that the error was basically cosmetic as the vm would start just
> fine.
> 
> forum thread: https://forum.proxmox.com/threads/119592/
> 
> Signed-off-by: Stefan Sterz <s.sterz@proxmox.com>
> ---
> changes from v2 (thanks @ Fiona Ebner):
> 
> * added newline to message
> * cache the fact that no drive is available so we warn only once
> * adjusted error message again
> 
> changes from v1: 
> 
> * make the error message more concise. 
> * use shorter forum link for better formatting in commit message 
>   (thanks @ Fiona Ebner).
> 
>  PVE/QemuServer.pm | 5 ++++-
>  1 file changed, 4 insertions(+), 1 deletion(-)
> 
> diff --git a/PVE/QemuServer.pm b/PVE/QemuServer.pm
> index dd6ea3e..11626cf 100644
> --- a/PVE/QemuServer.pm
> +++ b/PVE/QemuServer.pm
> @@ -1287,11 +1287,14 @@ sub option_exists {
>  my $cdrom_path;
>  sub get_cdrom_path {
>  
> -    return  $cdrom_path if $cdrom_path;
> +    return  $cdrom_path if defined($cdrom_path);
>  
>      return $cdrom_path = "/dev/cdrom" if -l "/dev/cdrom";
>      return $cdrom_path = "/dev/cdrom1" if -l "/dev/cdrom1";
>      return $cdrom_path = "/dev/cdrom2" if -l "/dev/cdrom2";
> +
> +    warn "no physical CD-ROM available\n";

why not use `log_warn` so that it shows up in the task worker log
prominently (and handles the trailing newline itself)?

also maybe end the sentence with "available for auto-selection" ?

> +    return $cdrom_path = '';

I know you did not start this, but I really do not like returning the result of
an assignment in dynamically-"typed" languages like perl, it's totally unclear
what side effects could be for most; anyhow can be addressed independent of
this patch.

>  }
>  
>  sub get_iso_path {





      reply	other threads:[~2022-12-19 15:18 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-19 12:23 Stefan Sterz
2022-12-19 15:17 ` 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=8af727e1-b008-0142-eab1-031026a9c4d8@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=pve-devel@lists.proxmox.com \
    --cc=s.sterz@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