Bug 1807919 - libvirt-guest fails to start on boot
Summary: libvirt-guest fails to start on boot
Alias: None
Product: Fedora
Classification: Fedora
Component: libvirt
Version: 31
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Libvirt Maintainers
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2020-02-27 13:21 UTC by Vadim Raskhozhev
Modified: 2020-11-24 17:37 UTC (History)
9 users (show)

Fixed In Version:
Doc Type: ---
Doc Text:
Clone Of:
Last Closed: 2020-11-24 17:37:16 UTC
Type: Bug

Attachments (Terms of Use)

Description Vadim Raskhozhev 2020-02-27 13:21:47 UTC
Description of problem: libvirt-guest fails to start on boot. `journalctl -b -u libvirt-guests.service` gives "error: internal error: Failed to start QEMU binary /usr/bin/qemu-system-x86_64 for probing: qemu-system-x86_64: cannot create PID file: Failed to write pid file" for each VM it tries to start

Version-Release number of selected component (if applicable): libvirt-client-5.6.0-5.fc31.x86_64

How reproducible: always

Steps to Reproduce:
1. Enable libvirt-guests.service
2. Start a VM with libvirt
3. Reboot

Actual results:
└► virsh list
 Id   Name       State

└► systemctl status libvirt-guests.service 
● libvirt-guests.service - Suspend/Resume Running libvirt Guests
   Loaded: loaded (/usr/lib/systemd/system/libvirt-guests.service; enabled; vendor preset: disabled)
   Active: failed (Result: exit-code) since Thu 2020-02-27 15:01:07 MSK; 1h 14min ago
     Docs: man:libvirtd(8)
  Process: 1481 ExecStart=/usr/libexec/libvirt-guests.sh start (code=exited, status=1/FAILURE)
 Main PID: 1481 (code=exited, status=1/FAILURE)

Expected results: a running VM

Additional info:
└► sestatus 
SELinux status:                 disabled

(just in case)

Comment 1 Ben Cotton 2020-11-03 16:24:37 UTC
This message is a reminder that Fedora 31 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 31 on 2020-11-24.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '31'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 31 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 2 Ben Cotton 2020-11-24 17:37:16 UTC
Fedora 31 changed to end-of-life (EOL) status on 2020-11-24. Fedora 31 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

Note You need to log in before you can comment on or make changes to this bug.