Re: [libvirt-users] libvirtd not accepting connections

Martin Kletzander
Sat, 03 Jun 2017 21:47:43 -0000

On Sat, Jun 03, 2017 at 05:20:47PM -0400, Michael C Cambria
wrote:
>I also tried stopping libvirtd, renaming both qemu-system-i386 and
>qemu-system-x86_64, start libvirtd.  Things get further along; dnsmasq
>log messages show up.
>
>$ sudo systemctl status libvirtd.service
>● libvirtd.service - Virtualization daemon
>    Loaded: loaded (/usr/lib/systemd/system/libvirtd.service; enabled;
>vendor preset: enabled)
>    Active: active (running) since Sat 2017-06-03 17:14:25 EDT; 7s ago
>      Docs: man:libvirtd(8)
>            http://libvirt.org
>  Main PID: 3246 (libvirtd)
>     Tasks: 21 (limit: 4915)
>    Memory: 107.4M
>       CPU: 300ms
>    CGroup: /system.slice/libvirtd.service
>            ├─3158 /usr/bin/qemu-system-i386 -S -no-user-config
>-nodefaults -nographic -M none -qmp
>unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait
>-pidfile /var/lib/libvirt/qemu/capabilities.
>            ├─3160 /usr/bin/qemu-system-i386 -S -no-user-config
>-nodefaults -nographic -M none -qmp
>unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,nowait
>-pidfile /var/lib/libvirt/qemu/capabilities.
>            ├─3246 /usr/sbin/libvirtd
>            ├─3457 /sbin/dnsmasq
>--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro
>--dhcp-script=/usr/libexec/libvirt_leaseshelper
>            └─3458 /sbin/dnsmasq
>--conf-file=/var/lib/libvirt/dnsmasq/default.conf --leasefile-ro
>--dhcp-script=/usr/libexec/libvirt_leaseshelper
>
>Jun 03 17:14:25 example.com libvirtd[3246]: Failed to probe capabilities
>for /usr/bin/qemu-kvm: internal error: Child process (LC_ALL=C
>PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin /usr/bin/qemu-k
>Jun 03 17:14:26 example.com dnsmasq[3457]: started, version 2.76
>cachesize 150
>Jun 03 17:14:26 example.com dnsmasq[3457]: compile time options: IPv6
>GNU-getopt DBus no-i18n IDN DHCP DHCPv6 no-Lua TFTP no-conntrack ipset
>auth DNSSEC loop-detect inotify
>Jun 03 17:14:26 example.com dnsmasq-dhcp[3457]: DHCP, IP range
>192.168.122.2 -- 192.168.122.254, lease time 1h
>Jun 03 17:14:26 example.com dnsmasq-dhcp[3457]: DHCP, sockets bound
>exclusively to interface virbr0
>Jun 03 17:14:26 example.com dnsmasq[3457]: reading /etc/resolv.conf
>Jun 03 17:14:26 example.com dnsmasq[3457]: using nameserver 172.16.8.1#53
>Jun 03 17:14:26 example.com dnsmasq[3457]: read /etc/hosts - 2 addresses
>Jun 03 17:14:26 example.com dnsmasq[3457]: read
>/var/lib/libvirt/dnsmasq/default.addnhosts - 0 addresses
>Jun 03 17:14:26 example.com dnsmasq-dhcp[3457]: read
>/var/lib/libvirt/dnsmasq/default.hostsfile
>
>
>$ sudo virsh list
>  Id    Name                           State
>----------------------------------------------------
>
>$
>
>As you can see, none of my vm's show up.  I'm guessing the
"qemu-kvm:
>internal error" results from renaming qemu-system-x86_64??
>

Yeah, feel free to move them back.

>Could something else (selinux?) be involved?

It should not.  Now we know it is QEMU, but becuase it is disrupting
libvirt in its initialization phase, it looks like nothing works.

You could grab a backtrace of the qemu process and try on qemu-devel
ML.  Also, if you want to make sure (or see after what command gets
stuck), you can enable debug logs for libvirt into some file and then
grep that for QEMU_MONITOR_ and you'll see.

[1] http://wiki.libvirt.org/page/DebugLogs
[2] I'm not sure about the whole thing to look for, but this is enough)