Re: [PATCH qemu-server 0/3] fix #7801: warn about problematic VirtIO ISOs

[Jonas Theisen <j.theisen@proxmox.com>]

On 9/15/26 16:32, Nicolas Frey wrote:
> This series fixes #7801 by implementing backend-only checks for VirtIO
> ISOs with known issues. When a user starts, creates, or updates a VM,
> the system scans for problematic VirtIO filenames and logs a warning in
> the task log if a known issue is detected.
>
> This approach supersedes the earlier UI patches [0], following feedback
> to implement the check in the backend. Since the backend check already
> alerts users via task log warnings (an equally effective and less intrusive
> solution) the separate API call and UI patches became unnecessary.
>
> Thanks Dominik and Maximilano for the feedback on the last revision
>
> [0] https://lore.proxmox.com/all/20260826074935.78437-1-n.frey@proxmox.com/
>
> <snip>

Tested the patches on current qemu-server v9.2.9.

Works as intended.
Only workflow that feels a little bit weird to me is when creating
a Windows VM with an affected ISO version and using "Start after Create"
This causes two directly consecutive tasks with warnings but i also
do not have a better idea on how to avoid this.

Tested (Web UI):
  * Existing Windows VM with affected ISO => Warning
  * Existing Windows VM with unaffected ISO => No Warning
  * New VM with affected ISO => Warning on create and start

Tested-by: Jonas Theisen <j.theisen@proxmox.com>