From: Nicolas Frey <n.frey@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server 3/3] partially fix #7801: vm start: warn about problematic VirtIO ISOs
Date: Tue, 15 Sep 2026 16:32:37 +0200 [thread overview]
Message-ID: <20260915143237.1033142-4-n.frey@proxmox.com> (raw)
In-Reply-To: <20260915143237.1033142-1-n.frey@proxmox.com>
An ISO can end up in a CD-ROM drive without passing through the
configuration API, e.g. by restoring a backup or by editing the
configuration file directly.
checking on start covers these cases too and puts the warning in the
task log right next to the boot that might be affected by the known
issue.
Signed-off-by: Nicolas Frey <n.frey@proxmox.com>
---
src/PVE/QemuServer.pm | 2 ++
1 file changed, 2 insertions(+)
diff --git a/src/PVE/QemuServer.pm b/src/PVE/QemuServer.pm
index 759f7db2..0ed75cd7 100644
--- a/src/PVE/QemuServer.pm
+++ b/src/PVE/QemuServer.pm
@@ -5627,6 +5627,8 @@ sub vm_start_nolock {
check_efi_vars($storecfg, $vmid, $conf) if $conf->{bios} && $conf->{bios} eq 'ovmf';
+ PVE::QemuServer::Drive::warn_about_virtio_win_issues_in_config($conf);
+
# Note that for certain cases like templates, the configuration is minimized, so need to ensure
# the rest of the function here uses the same configuration that was used to build the command
($cmd, $spice_port, my $pci_devices, $conf) = config_to_command(
--
2.47.3
next prev parent reply other threads:[~2026-09-15 14:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-15 14:32 [PATCH qemu-server 0/3] fix #7801: warn about problematic VirtIO ISOs Nicolas Frey
2026-09-15 14:32 ` [PATCH qemu-server 1/3] drive: add helper to detect VirtIO driver ISOs with known issues Nicolas Frey
2026-09-16 10:16 ` Maximiliano Sandoval
2026-09-16 10:23 ` Maximiliano Sandoval
2026-09-15 14:32 ` [PATCH qemu-server 2/3] partially fix #7801: api: warn about problematic VirtIO driver ISOs Nicolas Frey
2026-09-15 14:32 ` Nicolas Frey [this message]
2026-09-16 10:21 ` [PATCH qemu-server 0/3] fix #7801: warn about problematic VirtIO ISOs Maximiliano Sandoval
2026-09-16 10:26 ` Maximiliano Sandoval
2026-09-17 13:17 ` Jonas Theisen
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=20260915143237.1033142-4-n.frey@proxmox.com \
--to=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.