From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH qemu-server] bump version to 9.2.12
Date: Fri, 16 Oct 2026 01:37:25 +0200 [thread overview]
Message-ID: <20261015233726.3828211-1-t.lamprecht@proxmox.com> (raw)
Signed-off-by: Thomas Lamprecht <t.lamprecht@proxmox.com>
---
debian/changelog | 23 +++++++++++++++++++++++
1 file changed, 23 insertions(+)
diff --git a/debian/changelog b/debian/changelog
index c705f8db..272ae816 100644
--- a/debian/changelog
+++ b/debian/changelog
@@ -1,3 +1,26 @@
+qemu-server (9.2.12) trixie; urgency=medium
+
+ * partially fix #4012: migrate: name the snapshots that still reference a
+ local ISO image when refusing to migrate, as such a reference is not
+ visible in the current VM configuration.
+
+ * fix #8071, #8092: volume snapshot delete: use the currently attached drive
+ configuration when removing a snapshot of a running VM on storage with
+ snapshot-as-volume-chain. If the disk was re-attached on a different bus or
+ its options changed since the snapshot was taken, the removal failed and
+ left the VM locked.
+
+ * memory: fix custom NUMA nodes bound to multiple host node ranges, such as
+ 'hostnodes=1;3'. Such VMs failed to start, and some lists starting with
+ host node 0 silently bound the guest memory to other host nodes than
+ configured.
+
+ * fix #6907: memory: allow binding custom NUMA nodes to host nodes 10 and
+ higher when hugepages are enabled. These were rejected with a misleading
+ 'more than 1 hostnode value' error.
+
+ -- Proxmox Support Team <support@proxmox.com> Fri, 16 Oct 2026 01:03:40 +0200
+
qemu-server (9.2.11) trixie; urgency=medium
* hotplug pending: improve handling of machine type, only querying it when
--
2.47.3
reply other threads:[~2026-10-15 23:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20261015233726.3828211-1-t.lamprecht@proxmox.com \
--to=t.lamprecht@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