Package: systemd Version: 215-17+deb8u2 Severity: normal File: systemd-machined
Dear Maintainer, when trying to re-start a guest machine (doing virsh shutdown to use new library files in the qemu process), startup via "virsh start <machine>" failed: error: Failed to start domain <machine> error: error from service: CreateMachine: Activation of org.freedesktop.machine1 timed out The host in question is up for around 40 days. It seems as if libvirt needs some dbus connection and systemd-machined for guest startup. Restarting systemd-machined via "service systemd-machined restart" cleared the situation. So obviously, some sort of communication between systemd and dbus was lost unnoticed - maybe by recent library upgrades and daemon restarts by needrestart? Maybe some restart dependency is broken? Yours sincerely Matthias Merz -- Package-specific info: -- System Information: Debian Release: 8.2 APT prefers stable-updates APT policy: (500, 'stable-updates'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 3.16.0-4-amd64 (SMP w/48 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) Versions of packages systemd depends on: ii acl 2.2.52-2 ii adduser 3.113+nmu3 ii initscripts 2.88dsf-59 ii libacl1 2.2.52-2 ii libaudit1 1:2.4-1+b1 ii libblkid1 2.25.2-6 ii libc6 2.19-18+deb8u1 ii libcap2 1:2.24-8 ii libcap2-bin 1:2.24-8 ii libcryptsetup4 2:1.6.6-5 ii libgcrypt20 1.6.3-2 ii libkmod2 18-3 ii liblzma5 5.1.1alpha+20120614-2+b3 ii libpam0g 1.1.8-3.1 ii libselinux1 2.3-2 ii libsystemd0 215-17+deb8u2 ii mount 2.25.2-6 ii sysv-rc 2.88dsf-59 ii udev 215-17+deb8u2 ii util-linux 2.25.2-6 Versions of packages systemd recommends: ii dbus 1.8.20-0+deb8u1 ii libpam-systemd 215-17+deb8u2 Versions of packages systemd suggests: pn systemd-ui <none> -- Configuration Files: /etc/systemd/system.conf changed: [Manager] ShowStatus=yes -- no debconf information
