Hide Forgot
Description of problem: On a Server with GUI install with all the virt add-on's selected, virt-manager is unable to connect to any hypervisors with the error "verify that the libvirtd' daemon is running". 'libvirtd.service' was already enabled, but 'libvirt-guests.service', 'virt-who.service', 'virtlockd.socket' were disabled so I enabled them. Restarting 'libvirtd.service' resulted in "Process /usr.sbin/libvirtd was killed by signal 6 (SIGABRT) -abrt. Version-Release number of selected component (if applicable): How reproducible: On my system I can repo this easily. Steps to Reproduce: 1. Install 'Server with GUI' and select all the virt add-on's. 2. Open virt-manager.. my system is unable to connect to any hypervisors and the error message says to verify libvirtd is running. 3. I verified libvirtd is running.. [root@localhost ~]# systemctl list-unit-files | grep virt libvirt-guests.service disabled libvirtd.service enabled virt-who.service disabled virtlockd.service static virtlockd.socket disabled enable - 'libvirt-guests.service', 'virt-who.service', 'virtlockd.socket' [root@localhost ~]# systemctl list-unit-files | grep virt libvirt-guests.service enabled libvirtd.service enabled virt-who.service enabled virtlockd.service static virtlockd.socket enabled [root@localhost ~]# systemctl restart libvirtd.service Actual results: Restarting 'libvirtd.service' resulted in "Process /usr.sbin/libvirtd was killed by signal 6 (SIGABRT) -abrt. Expected results: On this same hardware running RHEL 6, I have no problems running virt-manager and vm's. I expect the same functionality with RHEL 7. Additional info: I seem to have lost my messages file but I do have a coredump which I will attach.
Created attachment 821919 [details] coredump
The coredump was generated by libvirt-1.1.1-8.el7. Relevant backtrace: #0 0x00007f2356561999 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #1 0x00007f23565630a8 in __GI_abort () at abort.c:90 #2 0x00007f23565a2147 in __libc_message (do_abort=do_abort@entry=2, fmt=0x7f23566aa888 "type=\"fast\" count=\"%zu\" size=\"%zu\"/>\n<total type=\"rest\" count=\"%zu\" size=\"%zu\"/>\n<system type=\"current\" size=\"%zu\"/>\n<system type=\"max\" size=\"%zu\"/>\n", fmt@entry=0x7f23566aa968 "*** Error in `%s': %s: 0x%s ***\n") at ../sysdeps/unix/sysv/linux/libc_fatal.c:196 #3 0x00007f23565a7f47 in malloc_printerr (action=<optimized out>, str=0x7f23566aa8b0 "tal type=\"rest\" count=\"%zu\" size=\"%zu\"/>\n<system type=\"current\" size=\"%zu\"/>\n<system type=\"max\" size=\"%zu\"/>\n", ptr=<optimized out>) at malloc.c:4972 #4 0x00007f2356f237b7 in selabel_open (backend=942, opts=0xa11, nopts=6) at label.c:166 ^^ these may be innacurate because I only have the correct debuginfo installed for libvirt #5 0x00007f235934bf13 in virSecurityManagerDispose (obj=0x7f2342fd2801) at security/security_manager.c:236 #6 0x00007f23591f96eb in virObjectUnref (anyobj=anyobj@entry=0x7f233c2e30c0) at util/virobject.c:262 #7 0x00007f235934c07c in virSecurityManagerNewDriver (drv=0x7f235962fde0 <virSecurityDriverSELinux>, virtDriver=virtDriver@entry=0x7f2342fd28b3 "LXC", allowDiskFormatProbing=<optimized out>, defaultConfined=<optimized out>, requireConfined=<optimized out>) at security/security_manager.c:99 #8 0x00007f235934c235 in virSecurityManagerNew (name=<optimized out>, virtDriver=virtDriver@entry=0x7f2342fd28b3 "LXC", allowDiskFormatProbing=allowDiskFormatProbing@entry=false, defaultConfined=<optimized out>, requireConfined=<optimized out>) at security/security_manager.c:186 This looks similar to bug 1014029. Is your /etc/selinux/targeted/contexts/lxc_contexts missing quotes around the context strings, as described in https://bugzilla.redhat.com/show_bug.cgi?id=1014029#c13? (Note that 'enabled' in 'systemctl list-unit-files' output does not verify if libvirtd is running, only that it should be run at system startup. Use 'systemctl status libvirtd' instead.)
Hi,Scott. when i go through this bug ,I can't reproduce this issue, pls help to have a look is there something wrong with my reproduce steps,Thanks. Version-Release number of selected component (if applicable): kernel-3.10.0-54.el7.x86_64 libvirt-1.1.1-12.el7.x86_64 qemu-kvm-1.5.3-19.el7.x86_64 steps: 1.Install 'Server with GUI' and select all the virt add-on's. 2.Check the status of 'libvirt-guests.service', 'virt-who.service', 'virtlockd.socket' [root@localhost ~]# systemctl list-unit-files | grep virt libvirt-guests.service disabled libvirtd.service enabled virt-who.service disabled virtlockd.service static virtlockd.socket disabled 3.enable - 'libvirt-guests.service', 'virt-who.service', 'virtlockd.socket' [root@localhost~]systemctl enable libvirt-guests.service [root@localhost~]systemctl enable virt-who.service [root@localhost~]systemctl enable virtlockd.socket [root@localhost ~]# systemctl list-unit-files | grep virt libvirt-guests.service enabled libvirtd.service enabled virt-who.service enabled virtlockd.service static virtlockd.socket enabled [root@localhost ~]# systemctl restart libvirtd.service 4.#service libvirtd status Redirecting to /bin/systemctl status libvirtd.service libvirtd.service - Virtualization daemon Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled) Active: active (running) since Mon 2013-12-02 18:12:19 CST; 8min ago Main PID: 19654 (libvirtd) CGroup: /system.slice/libvirtd.service ├─ 2742 /sbin/dnsmasq --conf-file=/var/lib/libvirt/dnsmasq/default... └─19654 /usr/sbin/libvirtd Dec 02 18:12:19 localhost.localdomain systemd[1]: Starting Virtualization dae... Dec 02 18:12:19 localhost.localdomain systemd[1]: Started Virtualization daemon. Dec 02 18:12:22 localhost.localdomain dnsmasq[2742]: read /etc/hosts - 2 addr... Dec 02 18:12:22 localhost.localdomain dnsmasq[2742]: read /var/lib/libvirt/dn... Dec 02 18:12:22 localhost.localdomain dnsmasq-dhcp[2742]: read /var/lib/libvi... Hint: Some lines were ellipsized, use -l to show in full. #virt-manager Open virt-manager and my system is able to connect to the hypervisor.
The reporter doesn't have the system available anymore, closing as a duplicate per comment 3. *** This bug has been marked as a duplicate of bug 1014029 ***