Hide Forgot
Created attachment 1202419 [details] "top" view of spinning processes Description of problem: Libvirtd and systemd 100% cpu, for 5 minutes (no sign of stopping). Version-Release number of selected component (if applicable): libvirt-daemon-1.3.3.2-1.fc24.x86_64 libvirt-daemon-kvm-1.3.3.2-1.fc24.x86_64 libvirt-client-1.3.3.2-1.fc24.x86_64 systemd-229-13.fc24.x86_64 4.7.3-200.fc24.x86_64 kernel How reproducible: Once so far Steps to Reproduce: 1. In virt-menager open an existing (rhel6, stopped) VM by doubleclick 2. In the VM window, click on the "run" gadget 3. Listen to laptop fan Actual results: VM did not apparently start. "top" on the host shows libvirtd and systemd processes at 100% of a core, continuously. Expected results: VM runs. Additional info: Tail end of host /var/log/messages: Sep 19 10:40:34 lap audit: VIRT_RESOURCE pid=1235 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:virtd_t:s0-s0:c0.c1023 msg='virt=kvm resrc=net reason=open vm="rhel6.3" uuid=f3f415d5-51ba-4578-8525-48aa1f9a9ae6 net=52:54:00:10:ec:33 path="/dev/vhost-net" rdev=0A:EE exe="/usr/sbin/libvirtd" hostname=? addr=? terminal=? res=success' Sep 19 10:40:34 lap dbus-daemon[1097]: [system] Activating via systemd: service name='org.freedesktop.machine1' unit='dbus-org.freedesktop.machine1.service' Sep 19 10:40:34 lap systemd: Created slice Virtual Machine and Container Slice. Sep 19 10:40:34 lap systemd: Starting Virtual Machine and Container Registration Service... Sep 19 10:40:34 lap dbus-daemon[1097]: [system] Successfully activated service 'org.freedesktop.machine1' Sep 19 10:40:34 lap systemd: Started Virtual Machine and Container Registration Service. Sep 19 10:40:34 lap audit: SERVICE_START pid=1 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:init_t:s0 msg='unit=systemd-machined comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success' Sep 19 10:40:34 lap systemd-machined: New machine qemu-1-rhel6.3. Sep 19 10:40:34 lap systemd: Started Virtual Machine qemu-1-rhel6.3. Sep 19 10:40:34 lap systemd: iscsi.service: Unit cannot be reloaded because it is inactive. A "kill -9" applied to the libvirtd process turns it to zombie... but does _NOT_ stop it (or the systemd process, pid 1) eating cpu.
[jgh@lap ~]$ sudo reboot Failed to start reboot.target: Connection timed out See system logs and 'systemctl status reboot.target' for details. [jgh@lap ~]$ sudo systemctl status reboot.target Failed to get properties: Connection timed out [jgh@lap ~]$
After a hard power-cycle, the symptom did not repeat.
Sorry for the lack of response, but since it sounds like this was a one off issue, I'm just closing it. Please reopen if this reproduces again