From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [IPv6:2a01:7e0:0:424::9]) by lore.proxmox.com (Postfix) with ESMTPS id 02D1F1FF13A for ; Wed, 24 Jun 2026 10:42:36 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id D920D1243B; Wed, 24 Jun 2026 10:42:35 +0200 (CEST) From: Maximiliano Sandoval To: pve-devel@lists.proxmox.com Subject: [PATCH qemu-server 2/2] vm start: log qemu version when starting a VM Date: Wed, 24 Jun 2026 10:40:45 +0200 Message-ID: <20260624084201.168436-2-m.sandoval@proxmox.com> X-Mailer: git-send-email 2.47.3 In-Reply-To: <20260624084201.168436-1-m.sandoval@proxmox.com> References: <20260624084201.168436-1-m.sandoval@proxmox.com> MIME-Version: 1.0 Content-Transfer-Encoding: 8bit X-Bm-Milter-Handled: 55990f41-d878-4baa-be0a-ee34c49e34d2 X-Bm-Transport-Timestamp: 1782290509169 X-SPAM-LEVEL: Spam detection results: 0 AWL 0.125 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [qemuserver.pm] Message-ID-Hash: LFNSPP3CYIK5FUHM7GQD7QDSXBGJ3TDS X-Message-ID-Hash: LFNSPP3CYIK5FUHM7GQD7QDSXBGJ3TDS X-MailFrom: m.sandoval@proxmox.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; loop; banned-address; emergency; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header X-Mailman-Version: 3.3.10 Precedence: list List-Id: Proxmox VE development discussion List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: Previously, having the system journal and task logs from a boot was not enough to determine which qemu version is installed nor the running QEMU version of a VM. This is addressed by logging pve-qemu-kvm's package version when starting the VM. The package version is obtained with the 'query-version' qmp command. Signed-off-by: Maximiliano Sandoval --- Notes: sample output in the journal: Jun 24 10:39:14 pve-148 qm[26137]: VM 100 started with PID 26166 using pve-qemu-kvm_11.0.0-4. src/PVE/QemuServer.pm | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/src/PVE/QemuServer.pm b/src/PVE/QemuServer.pm index 55e9f520..d6576a41 100644 --- a/src/PVE/QemuServer.pm +++ b/src/PVE/QemuServer.pm @@ -5839,7 +5839,8 @@ sub vm_start_nolock { eval { PVE::QemuServer::PCI::reserve_pci_usage($pci_reserve_list, $vmid, undef, $pid) }; warn $@ if $@; - syslog("info", "VM $vmid started with PID $pid."); + my $pgk_version = get_package_version($vmid); + syslog("info", "VM $vmid started with PID $pid using $pgk_version."); PVE::QemuServer::RunState::create_cleanup_flag($vmid); @@ -8054,6 +8055,12 @@ sub get_running_qemu_version { return "$res->{qemu}->{major}.$res->{qemu}->{minor}"; } +sub get_package_version { + my ($vmid) = @_; + my $res = mon_cmd($vmid, "query-version"); + return $res->{package}; +} + sub qemu_use_old_bios_files { my ($machine_type) = @_; -- 2.47.3