8:22 a.m.
On 06/02/2017 09:53 AM, Michael C. Cambria wrote:
On 06/02/2017 09:43 AM, Martin Kletzander wrote:
> [adding back the ML, you probably hit reply instead of reply-all, this
> way other people might help if they know more]
>
> On Fri, Jun 02, 2017 at 08:10:01AM -0400, Michael C. Cambria wrote:
>>
>> Hi,
>>
>> libvirtd never seems to get notified that there is work to do.
>> journalct
>> -f indicated that nothing was logged when connections were attempted
>> via
>> virsh.
>>
>> I also tried 'LIBVIRT_DEBUG=1 libvirtd --verbose' and once startup
>> finished, there were no more log entries even though virsh attempts
>> were
>> made.
>>
>
> That's because it gets overridden by the configuration files. This
> might be a bug, but it's not related to what's happening.
>
>> "ps ax" shows about a dozen "qemu-system-alpha" processes. I
don't
>> know
>> if it matters but I didn't expect to see this. I didn't intentionally
>> configure alpha emulations (assuming that's what it is) and certainly
>> don't want to waste resources having it running.
>>
>
> Libvirt caches the capabilities of the emulators it can find in your
> system in order not to waste resources. These processes are expected to
> go away after they reply with all libvirt asks them for. However, it
> seems like the initialization cannot be completed precisely due to the
> fact that these processes don't communicate.
>
> There might be some details about qemu-system-alpha that are different
> when compared to, e.g. qemu-system-x86 and libvirt is not (yet) adapted
> to them, but I installed that emulator and libvirt daemon runs as
> usual. It looks like a problem in QEMU. Could you, as a workaround,
> try uninstalling that qemu binary from your system and restarting the
> service?
>
With qemu-system-alpha gone, I now see qemu-system-arm. With all
qemu-system-* removed (using dnf remove) and stopping, then starting
libvirtd, I still see qemu-system-arm even though the executable doesn't
exist:
# ls -al /usr/bin | grep qemu-system
-rwxr-xr-x. 1 root root 9993416 Apr 13 21:10 qemu-system-i386
-rwxr-xr-x. 1 root root 10036032 Apr 13 21:10 qemu-system-x86_64
# 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 09:12:19 EDT; 8min ago
Docs: man:libvirtd(8)
http://libvirt.org
Main PID: 5965 (libvirtd)
Tasks: 23 (limit: 4915)
Memory: 128.2M
CPU: 411ms
CGroup: /system.slice/libvirtd.service
├─1537 /usr/bin/qemu-system-arm -S -no-user-config
-nodefaults -nographic -M none -qmp
unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,n
├─1638 /usr/bin/qemu-system-arm -S -no-user-config
-nodefaults -nographic -M none -qmp
unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,n
├─5965 /usr/sbin/libvirtd
├─5999 /usr/bin/qemu-system-i386 -S -no-user-config
-nodefaults -nographic -M none -qmp
unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,
└─6001 /usr/bin/qemu-system-i386 -S -no-user-config
-nodefaults -nographic -M none -qmp
unix:/var/lib/libvirt/qemu/capabilities.monitor.sock,server,
Jun 03 09:12:19 example.com systemd[1]: Starting Virtualization daemon...
Jun 03 09:12:19 example.com systemd[1]: Started Virtualization daemon.
> Also, what versions of libvirt and qemu do you have installed?
# LIBVIRT_DEBUG=1 libvirtd --verbose
2017-06-02 00:16:30.317+0000: 18088: info : libvirt version: 2.2.1,
package: 1.fc25 (Fedora Project, 2017-05-10-22:06:21,
buildvm-29.phx2.fedoraproject.org)
I'll check on qemu as soon as I can get to the machine. The version
should be the latest one gets via 'dnf update' on fedora 25
# /usr/sbin/libvirtd --version
/usr/sbin/libvirtd (libvirt) 2.2.1
# qemu-x86_64 --version
qemu-x86_64 version 2.7.1(qemu-2.7.1-6.fc25), Copyright (c) 2003-2016
Fabrice Bellard and the QEMU Project developers
[ gdb output deleted]