From: "Elias Huhsovitz" <e.huhsovitz@proxmox.com>
To: "Thomas Ellmenreich" <t.ellmenreich@proxmox.com>,
<pve-devel@lists.proxmox.com>
Subject: Re: [PATCH qemu-server v2 2/3] add new classify_drive_file utility
Date: Mon, 10 Aug 2026 10:51:07 +0200 [thread overview]
Message-ID: <DKL4VZ3Y58WU.245PVUNQSEQQ7@proxmox.com> (raw)
In-Reply-To: <20260805082122.43184-3-t.ellmenreich@proxmox.com>
Good refactor.
1 small nit inline.
On Wed Aug 5, 2026 at 10:21 AM CEST, Thomas Ellmenreich wrote:
> To more easily and clearly branch off different types of drive files a
> new utility function is introduced that classifies such a drive file.
> The return options are 'none', 'cdrom', 'absolute' and 'volume'. In any
> other case the function returns 'unknown'.
>
> Signed-off-by: Thomas Ellmenreich <t.ellmenreich@proxmox.com>
> ---
> src/PVE/QemuServer.pm | 29 ++++++++++++++++++-----------
> src/PVE/QemuServer/Drive.pm | 25 +++++++++++++++++++++++++
> 2 files changed, 43 insertions(+), 11 deletions(-)
>
> diff --git a/src/PVE/QemuServer.pm b/src/PVE/QemuServer.pm
> index fdef20dc..0e998cbe 100644
[...]
> +# Tries to classify the drive file as either 'none', 'cdrom', 'absolute'
> +# or 'volume'. In all other cases it will return undef.
nit: Subroutine returns 'unknown' in default path.
Comments states that `undef` is returned.
> +sub classify_drive_file {
> + my ($volid) = @_;
> +
> + if ($volid eq 'none') {
> + return 'none';
> + } elsif ($volid eq 'cdrom') {
> + return 'cdrom';
> + } elsif ($volid =~ m|^/|) {
> + return 'absolute';
> + } elsif (PVE::Storage::parse_volume_id($volid, 1)) {
> + return 'volume';
> + }
> +
> + return 'unknown';
> +}
> +
> sub drive_is_cloudinit {
> my ($drive) = @_;
> return $drive->{file} =~ m@[:/](?:vm-\d+-)?cloudinit(?:\.$QEMU_FORMAT_RE)?$@;
> @@ -794,6 +814,11 @@ sub drive_is_cdrom {
> return $drive && $drive->{media} && ($drive->{media} eq 'cdrom');
> }
>
> +sub drive_has_absolute_path {
> + my ($drive) = @_;
> + return classify_drive_file($drive->{file}) eq "absolute";
> +}
> +
> sub parse_drive_interface {
> my ($key) = @_;
>
next prev parent reply other threads:[~2026-08-10 8:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-05 8:21 [PATCH qemu-server v2 0/3] refactor of volume_id classification Thomas Ellmenreich
2026-08-05 8:21 ` [PATCH qemu-server v2 1/3] move verify_volume_id_or_* format registrations into Drive submodule Thomas Ellmenreich
2026-08-05 8:21 ` [PATCH qemu-server v2 2/3] add new classify_drive_file utility Thomas Ellmenreich
2026-08-07 9:30 ` Max R. Carrara
2026-08-07 9:54 ` Thomas Ellmenreich
2026-08-10 8:51 ` Elias Huhsovitz [this message]
2026-08-05 8:21 ` [PATCH qemu-server v2 3/3] removed some unnecessary undef checks Thomas Ellmenreich
2026-08-07 9:33 ` Max R. Carrara
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=DKL4VZ3Y58WU.245PVUNQSEQQ7@proxmox.com \
--to=e.huhsovitz@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
--cc=t.ellmenreich@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