Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
DescriptionMichael S. Tsirkin
2010-05-31 15:56:20 UTC
Description of problem:
installed libvirt which installed libvirtd but
did not start it. had to reboot to get it started
Version-Release number of selected component (if applicable):
libvirt-0.8.1-7.el6.x86_64
How reproducible:
always
Steps to Reproduce:
1. yum install libvirt
2. ls -l /var/run/libvirt/libvirt-sock
3. /etc/rc.d/init.d/libvirtd start
3. yum remove libvirt
4. ls -l /var/run/libvirt/libvirt-sock
Actual results:
after install libvirtd is not running and libvirt sock does not exist
after remove libvirtd is sill running and sock is left behind
Expected results:
libvirtd should run after install, reboot should not be required
after remove, should stop libvirtd and remove the sock file, do not leave files behind
Additional info:
Pretty sure your startup suggestion would violate packaging guidelines:
http://fedoraproject.org/wiki/Packaging:SysVInitScript#Why_don.27t_we....
As for uninstall, we don't take down qemu-kvm processes when uninstalling that package, why should we stop libvirtd when uninstalling it?
We already stop the daemon during uninstall:
%preun
%if %{with_libvirtd}
if [ $1 = 0 ]; then
/sbin/service libvirtd stop 1>/dev/null 2>&1
/sbin/chkconfig --del libvirtd
fi
%endif
And I've verified that it works
# ps -axuwfw | grep libvirtd
root 6519 0.0 2.7 620236 21688 ? Sl Jun01 0:01 libvirtd --daemon
# rpm -e libvirt
warning: /etc/libvirt/qemu.conf saved as /etc/libvirt/qemu.conf.rpmsave
warning: /etc/libvirt/libvirtd.conf saved as /etc/libvirt/libvirtd.conf.rpmsave
# ps -axuwfw | grep libvirtd
As Cole says, starting the daemon upon install is forbidden by packaging rules.
Comment 4Michael S. Tsirkin
2010-06-02 11:27:05 UTC
why is /var/run/libvirt/libvirt-sock left behind then?
Is libvirtd daemon removing it on stop?
Verified this bug PASS with libvirt-0.8.1-13.el6.x86_64
- kernel-2.6.32-42.el6.x86_64
- qemu-kvm-0.12.1.2-2.90.el6.x86_64
- qemu-img-0.12.1.2-2.90.el6.x86_64
1. As Cole says, starting the daemon upon install is forbidden by packaging rules. So after new install libvirt package, the libvirtd service is stop status and /var/run/libvirt/libvirt-sock is not generated.
2. After remove libvirt package, libvirtd service is stoped, and /var/run/libvirt/libvirt-sock file is removed.
# yum remove libvirt
......
Erasing : libvirt-0.8.1-13.el6.x86_64 1/1
Removed:
libvirt.x86_64 0:0.8.1-13.el6
Complete!
# service libvirtd status
libvirtd: unrecognized service
# ls -l /var/run/libvirt/libvirt-sock
ls: cannot access /var/run/libvirt/libvirt-sock: No such file or directory
Comment 10releng-rhel@redhat.com
2010-11-11 14:48:32 UTC
Red Hat Enterprise Linux 6.0 is now available and should resolve
the problem described in this bug report. This report is therefore being closed
with a resolution of CURRENTRELEASE. You may reopen this bug report if the
solution does not work for you.