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>,
	"Hannes Dürr" <h.duerr@proxmox.com>,
	"Fiona Ebner" <f.ebner@proxmox.com>
Subject: Re: [pve-devel] [PATCH v2 qemu-server] fix #4957: add vendor and product information passthrough for SCSI-Disks
Date: Wed, 8 Nov 2023 15:43:48 +0100	[thread overview]
Message-ID: <b6e7360c-3d4f-449d-bb73-464d7df3fdec@proxmox.com> (raw)
In-Reply-To: <c9061bc3-963e-4502-846b-4ad54673cf60@proxmox.com>

Am 08/11/2023 um 15:28 schrieb Hannes Dürr:
> On 11/8/23 11:04, Fiona Ebner wrote:
>> Am 08.11.23 um 09:51 schrieb Hannes Duerr:
>>> +			if ($opt =~ m/scsi/) {
>>> +			    PVE::QemuServer::check_scsi_feature_compatibility($opt, $created_opts, $conf, $storecfg, $param);
>>
>> Style nit: line too long (100 characters is our limit)
>>
>> Note that $created_opts was already merged into $conf two lines above.
>> I'd rather not introduce new usage of that variable.
>>
>> 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 ?

But all information is still there? I.e., the disk's bus, like scsi, and if any
vendor or product properties are set. So you can still parse that value and check
validity.

>>> +			}
>>> +		    }
>>>   		    if (!$conf->{boot}) {
>>>   			my $devs = PVE::QemuServer::get_default_bootdevices($conf);
>>>   			$conf->{boot} = PVE::QemuServer::print_bootorder($devs);

>> (...)
> what does that mean ?

That fiona snipped (trimmed) some context due to it not being relevant for
the reveiw, like in quotes, albeit they more often use brackets there, like
"[...] lorem ipsum"





  reply	other threads:[~2023-11-08 14:43 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 [this message]
2023-11-09  8:34     ` Fiona Ebner

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=b6e7360c-3d4f-449d-bb73-464d7df3fdec@proxmox.com \
    --to=t.lamprecht@proxmox.com \
    --cc=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