From: Maximiliano Sandoval <m.sandoval@proxmox.com>
To: "Nicolas Frey" <n.frey@proxmox.com>
Cc: pve-devel@lists.proxmox.com
Subject: Re: [PATCH manager v2 0/4] fix #7801: ui: warn about problematic virtio versions on iso select
Date: Fri, 11 Sep 2026 10:02:04 +0200 [thread overview]
Message-ID: <s8old98gqrn.fsf@toolbox> (raw)
In-Reply-To: <DKZJ47ZJ83JN.33HBKI0L6KHMM@proxmox.com> (Nicolas Frey's message of "Thu, 27 Aug 2026 08:57:29 +0200")
"Nicolas Frey" <n.frey@proxmox.com> writes:
> On Thu Aug 27, 2026 at 8:14 AM CEST, Dominik Csapak wrote:
>> high level question: could it make sense to have this
>> warning also on the backend, e.g. in the start task?
>>
>> that way a user only using the cli/api would also see it, not
>> only the ui users.
>>
>> if that makes sense, we might want to keep a list
>> of versions on the backend and expose it via the api
>> for the gui?
>
> I think both of these points make sense to implement, I can add it in the
> next revision
>
>>
>> on the backend we could even match the sha256 sum or something like
>> that (if that's not too much of a performance hit on start) to
>> check if it's really the right version
>>
>
> while I guess this is a better heuristic to check against instead of
> just relying on the filename, I think unless performing the sha256
> sum once and caching it, it would be too much of an unnecessary
> performance hit.
>
> [snip]
>From my experience in support, I do not remember seeing a case where the
filename was not the same as the one from the downloads at
https://fedorapeople.org.
On the same topic, a big percentage of tickets have to devolve into
asking customers to downgrade drivers because they have a version with
issues. Multiple customers have genuine non-driver related issues, but
we cannot start debugging those until they downgrade the drivers to
0.1.271 which takes a couple of rountrips/days.
--
Maximiliano
prev parent reply other threads:[~2026-09-11 8:02 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-26 7:49 [PATCH manager v2 0/4] fix #7801: ui: warn about problematic virtio versions on iso select Nicolas Frey
2026-08-26 7:49 ` [PATCH pve-manager v2 1/4] ui: iso selector: add option to warn about virtio versions with issues Nicolas Frey
2026-08-26 11:44 ` Fiona Ebner
2026-08-26 13:28 ` Nicolas Frey
2026-08-26 7:49 ` [PATCH pve-manager v2 2/4] ui: cd edit: add `warnVirtio` option to pass to iso selector Nicolas Frey
2026-08-26 7:49 ` [PATCH pve-manager v2 3/4] partially fix #7801: ui: ospanel: warn about problematic virtio versions Nicolas Frey
2026-08-26 7:49 ` [PATCH pve-manager v2 4/4] partially fix #7801: ui: hardware view: " Nicolas Frey
2026-08-26 11:44 ` Fiona Ebner
2026-08-26 13:38 ` Nicolas Frey
2026-08-26 14:09 ` Fiona Ebner
2026-08-27 6:14 ` [PATCH manager v2 0/4] fix #7801: ui: warn about problematic virtio versions on iso select Dominik Csapak
2026-08-27 6:57 ` Nicolas Frey
2026-09-11 8:02 ` Maximiliano Sandoval [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=s8old98gqrn.fsf@toolbox \
--to=m.sandoval@proxmox.com \
--cc=n.frey@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