From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [pve-devel] [PATCH qemu-server 3/3] dbus-vmstate: guard more errors in qemu_del_dbus_vmstate()
Date: Wed, 17 Dec 2025 14:17:12 +0100 [thread overview]
Message-ID: <20251217131724.118681-4-f.ebner@proxmox.com> (raw)
In-Reply-To: <20251217131724.118681-1-f.ebner@proxmox.com>
Before commit "systemd: vmid.scope: add orderings to fix dbus-vmstate
cleanup (regression)", an issue with hard errors during cleanup of the
dbus-vmstate surfaced if the dbus.service was already not running. In
particular, the Net::DBus->system() call would fail when the
dbus.service is not running. Guard errors there and for the
get_bus_object() call, like other errors in qemu_del_dbus_vmstate()
already are guarded. Do not honor the 'quiet' option for these and
log failures in any case, because not having a working system DBus
is a more fundamental failure than the other failure scenarios in the
function and should still be recorded.
Signed-off-by: Fiona Ebner <f.ebner@proxmox.com>
---
src/PVE/QemuServer/DBusVMState.pm | 15 +++++++++++++--
1 file changed, 13 insertions(+), 2 deletions(-)
diff --git a/src/PVE/QemuServer/DBusVMState.pm b/src/PVE/QemuServer/DBusVMState.pm
index 480d9f70..3b5fe301 100644
--- a/src/PVE/QemuServer/DBusVMState.pm
+++ b/src/PVE/QemuServer/DBusVMState.pm
@@ -82,8 +82,19 @@ sub qemu_del_dbus_vmstate {
my ($vmid, %params) = @_;
my $num_entries = undef;
- my $dbus = Net::DBus->system();
- my $dbus_obj = $dbus->get_bus_object();
+ my $dbus = eval { Net::DBus->system(); };
+ if (my $err = $@) {
+ # log fundamental error even if $params{quiet} is set
+ syslog('warn', "failed to connect to DBus system bus: $err");
+ return undef;
+ }
+
+ my $dbus_obj = eval { $dbus->get_bus_object(); };
+ if (my $err = $@) {
+ # log fundamental error even if $params{quiet} is set
+ syslog('warn', "failed to get DBus bus object: $err");
+ return undef;
+ }
my $owners = eval { $dbus_obj->ListQueuedOwners('org.qemu.VMState1') };
if (my $err = $@) {
--
2.47.3
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2025-12-17 13:17 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-17 13:17 [pve-devel] [PATCH-SERIES common/qemu-server 0/3] fix #7092: systemd: vmid.scope: add orderings to fix dbus-vmstate cleanup (regression) Fiona Ebner
2025-12-17 13:17 ` [pve-devel] [PATCH common 1/3] systemd: enter scope: allow specifying 'Before' and 'After' properties Fiona Ebner
2025-12-17 13:17 ` [pve-devel] [PATCH qemu-server 2/3] systemd: vmid.scope: add orderings to fix dbus-vmstate cleanup (regression) Fiona Ebner
2025-12-17 13:17 ` Fiona Ebner [this message]
2025-12-17 14:05 ` [pve-devel] [PATCH-SERIES common/qemu-server 0/3] fix #7092: " Maximiliano Sandoval
2025-12-17 14:16 ` [pve-devel] applied-series: " Fabian Grünbichler
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=20251217131724.118681-4-f.ebner@proxmox.com \
--to=f.ebner@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