Error: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected

okwfrend · March 13, 2026, 9:33am

After updating my system and rebooting, my QEMU/KVM virtual machines won’t start when I try to launch them with virt-manager or virsh.

On virt-manager I get the error when trying to start a VM:

Error starting domain: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected

Traceback (most recent call last):
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 67, in cb_wrapper
    callback(asyncjob, *args, **kwargs)
    ~~~~~~~~^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/asyncjob.py", line 101, in tmpcb
    callback(*args, **kwargs)
    ~~~~~~~~^^^^^^^^^^^^^^^^^
  File "/usr/share/virt-manager/virtManager/object/libvirtobject.py", line 57, in newfn
    ret = fn(self, *args, **kwargs)
  File "/usr/share/virt-manager/virtManager/object/domain.py", line 1459, in startup
    self._backend.create()
    ~~~~~~~~~~~~~~~~~~~~^^
  File "/usr/lib64/python3.13/site-packages/libvirt.py", line 1395, in create
    raise libvirtError('virDomainCreate() failed')
libvirt.libvirtError: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected

pc:/home/user # cat /etc/os-release
                                                                                                                                                           NAME="openSUSE Tumbleweed"                                                                                                                                                                    # VERSION="20260310"                                                                                                                                                                          ID="opensuse-tumbleweed"
ID_LIKE="opensuse suse"
VERSION_ID="20260310"
PRETTY_NAME="openSUSE Tumbleweed"
ANSI_COLOR="0;32"
# CPE 2.3 format, boo#1217921
CPE_NAME="cpe:2.3:o:opensuse:tumbleweed:20260310:*:*:*:*:*:*:*"
#CPE 2.2 format
#CPE_NAME="cpe:/o:opensuse:tumbleweed:20260310"
BUG_REPORT_URL="https://bugzilla.opensuse.org"
SUPPORT_URL="https://bugs.opensuse.org"
HOME_URL="https://www.opensuse.org"
DOCUMENTATION_URL="https://en.opensuse.org/Portal:Tumbleweed"
LOGO="distributor-logo-Tumbleweed"
pc:/home/user # sestatus
SELinux status:                 enabled
SELinuxfs mount:                /sys/fs/selinux
SELinux root directory:         /etc/selinux
Loaded policy name:             targeted
Current mode:                   enforcing
Mode from config file:          enforcing
Policy MLS status:              enabled
Policy deny_unknown status:     allowed
Memory protection checking:     actual (secure)
Max kernel policy version:      35

pc:/home/user # journalctl -xe
....
Mar 13 09:16:40 pc systemd[1]: Started Network Manager Script Dispatcher Service.
░░ Subject: A start job for unit NetworkManager-dispatcher.service has finished successfully
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit NetworkManager-dispatcher.service has finished successfully.
░░
░░ The job identifier is 7472.
Mar 13 09:16:40 pc NetworkManager[1861]: <info>  [1773393400.4716] device (vnet8): state change: ip-check -> secondaries (reason 'none', managed-type: 'external')
Mar 13 09:16:40 pc NetworkManager[1861]: <info>  [1773393400.4717] device (vnet8): state change: secondaries -> activated (reason 'none', managed-type: 'external')
Mar 13 09:16:40 pc NetworkManager[1861]: <info>  [1773393400.4719] device (vnet8): Activation: successful, device activated.
Mar 13 09:16:40 pc dns-dnsmasq.sh[66086]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
Mar 13 09:16:40 pc systemd-machined[66071]: Failed to bind to varlink socket /run/systemd/resolve.hook/io.systemd.Machine: Permission denied
Mar 13 09:16:40 pc systemd-machined[66071]: Failed to fully start up daemon: Permission denied
Mar 13 09:16:40 pc virtqemud[2257]: GDBus.Error:org.freedesktop.DBus.Error.NoReply: Remote peer disconnected
Mar 13 09:16:40 pc systemd[1]: systemd-machined.service: Main process exited, code=exited, status=1/FAILURE
░░ Subject: Unit process exited
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ An ExecStart= process belonging to unit systemd-machined.service has exited.
░░
░░ The process' exit code is 'exited' and its exit status is 1.
Mar 13 09:16:40 pc systemd[1]: systemd-machined.service: Failed with result 'exit-code'.
░░ Subject: Unit failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ The unit systemd-machined.service has entered the 'failed' state with result 'exit-code'.
Mar 13 09:16:40 pc systemd[1]: Failed to start Virtual Machine and Container Registration Service.
░░ Subject: A start job for unit systemd-machined.service has failed
░░ Defined-By: systemd
░░ Support: https://lists.freedesktop.org/mailman/listinfo/systemd-devel
░░
░░ A start job for unit systemd-machined.service has finished with a failure.
░░
░░The job identifier is 7327 and the job result is failed.
...

okwfrend · March 13, 2026, 9:56am

I found the issue is probably related to SELinux since disabling SELinux with: # setenforce 0, starting the VM and enabling it again with # setenforce 1 seems to solve the problem until reboot

dcurtisfra · March 13, 2026, 11:13am

@okwfrend:

Welcome to the openSUSE Forums.

The issue you experienced is possibly due to the Tumbleweed SELinux Policy which unfortunately prevented the Virtual Machine and Container Registration Service from starting:

Here’s the affected lines from my systemd Journal this morning – before I applied the Tumbleweed snapshot which was released today –

Mär 13 08:46:14 systemd-machined[1247]: Failed to bind to varlink socket /run/systemd/resolve.hook/io.systemd.Machine: Permission denied
Mär 13 08:46:14 systemd-machined[1247]: Failed to fully start up daemon: Permission denied
Mär 13 08:46:14 systemd[1]: systemd-machined.service: Main process exited, code=exited, status=1/FAILURE
Mär 13 08:46:14 systemd[1]: systemd-machined.service: Failed with result 'exit-code'.
Mär 13 08:46:14 systemd[1]: Failed to start Virtual Machine and Container Registration Service.

With the Tumbleweed snapshot “20260311” the following change was made to the “selinux-policy” package:

* Allow virtlogd_t dac_override for virtlock (bsc#1253389)

– which seems to have fixed the issue – systemd Journal entries after the reboot aft applying today’s snapshot:

Mär 13 10:56:57 systemd[1]: Created slice Virtual Machine and Container Slice.
Mär 13 10:56:58 systemd[1]: Virtual Machine and Container Storage (Compatibility) skipped, unmet condition check ConditionPathExists=/var/lib/machines.raw
Mär 13 10:57:00 systemd[1]: Listening on Virtual Machine and Container Registration Service Socket.
Mär 13 10:57:00 systemd[1]: Starting Virtual Machine and Container Registration Service...
Mär 13 10:57:00 systemd[1]: Started Virtual Machine and Container Registration Service.

okwfrend · March 13, 2026, 7:06pm

Thanks

Updating my system with zypper update fixed the issue permanently. I should’ve updated my system completely first to see if that would solve the problem before asking for help here.

I really appreciate it!

myswtest · March 13, 2026, 8:31pm

If using TW, you do “updates” with

#  zypper dup

… not “update”

system · March 20, 2026, 8:32pm

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.