Fedora Account System
Red Hat Associate
Red Hat Customer
Description of problem: virtqemud.service doesn't start virtlogd.socket. Since fedora 35, a switch was made from libvirtd to virtqemud. The bug is probably caused by missing "Requires=virtlogd.socket" in virtqemud's service file. Without virtlogd.socket running, some APIs, like "virsh start" return an error: can't connect to virtlogd: Failed to connect socket to '/run/libvirt/virtlogd-sock': No such file or directory Version-Release number of selected component (if applicable): libvirt version: 7.6.0 OS: Fedora 35 How reproducible: always Steps to Reproduce: 1. create a VM 2. start the VM Actual results: Failed to connect socket to '/run/libvirt/virtlogd-sock': No such file or directory Expected results: VM is started Additional info:
FEDORA-2021-8582f4495e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2021-8582f4495e
FEDORA-2021-8582f4495e has been pushed to the Fedora 35 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2021-8582f4495e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2021-8582f4495e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2021-8582f4495e has been pushed to the Fedora 35 stable repository. If problem still persists, please make note of it in this bug report.