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

[Fiona Ebner <f.ebner@proxmox.com>]

On Tue, 15 Sep 2026 16:32:34 +0200, 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.
> 
> [...]

Applied, thanks! In commit 2/3, I changed the calls for parse_drive()
and drive_is_cdrom() to not call the imported versions via QemuServer,
but the ones from the Drive module directly. I also pushed an UI
follow-up to make the warnings visible upon edit already:
https://lore.proxmox.com/pve-devel/20260921111843.133598-1-f.ebner@proxmox.com/T/

[1/3] drive: add helper to detect VirtIO driver ISOs with known issues
      commit: 881fd37d17157982765c6c8fa3265eff57f84de9
[2/3] partially fix #7801: api: warn about problematic VirtIO driver ISOs
      commit: 80ae2f0a354ad164269a1987fc483f492d28f022
[3/3] partially fix #7801: vm start: warn about problematic VirtIO ISOs
      commit: f34b8f9f2a9eb89b237561ed1aff7a76a7e06774