public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Fiona Ebner <f.ebner@proxmox.com>
To: "Hannes Dürr" <h.duerr@proxmox.com>,
	"Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 qemu-server] fix #4957: add vendor and product information passthrough for SCSI-Disks
Date: Thu, 9 Nov 2023 09:34:55 +0100	[thread overview]
Message-ID: <3690eb2d-731c-4868-8ca4-f77715b00559@proxmox.com> (raw)
In-Reply-To: <c9061bc3-963e-4502-846b-4ad54673cf60@proxmox.com>

Am 08.11.23 um 15:28 schrieb Hannes Dürr:
>>
>> Can we do the check before creating the drive instead? We know if it's a
>> CD or pass-through and the path or if it's iscsi ahead of time and that
>> should be enough for the check, or what am I missing?
> I don't think its possible to check in advance as the config can still
> contain a not properly formed path like:
> 'local-lvm:5', which will be formed to the real path when creating the
> disk or am I mistaken
You can just teach the get_scsi_devicetype() helper to recognize the
special syntax and compare by storage type in that case (can/should be
it's own patch ;)). At a glance, 'iscsidirect' and 'zfs' are the ones
using an "iscsi://" path, but please double check. Of course there could
be a third-party plugin using "iscsi://" too, but this is just an early
check and only applies to VMs with machine version < 4.1 anyways. These
cases should be very rare and it'll just fail later so no big deal. The
benefit of having the check earlier for all other cases is enough to
justify that IMHO.




      parent reply	other threads:[~2023-11-09  8:35 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-08  8:51 Hannes Duerr
2023-11-08 10:04 ` Fiona Ebner
2023-11-08 14:28   ` Hannes Dürr
2023-11-08 14:43     ` Thomas Lamprecht
2023-11-09  8:34     ` Fiona Ebner [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=3690eb2d-731c-4868-8ca4-f77715b00559@proxmox.com \
    --to=f.ebner@proxmox.com \
    --cc=h.duerr@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