On 2016-02-18 10:43, Martin Kletzander wrote:
On Mon, Jan 18, 2016 at 05:04:44PM +0000, Justin Clift wrote:
<snip>
But last night I had the realisation that libvirtd itself might work
too
since it functions on the other BSD's. So, took a few minutes to try
it out. Without QEMU installed, libvirtd doesn't error out like the
above. That only happens when QEMU is around. So, it's related to
that
somehow. :)
Sorry for not replying for a while. Unfortunately I have no new info
about this and why it might be happening. Did you get any further?
No. My interests lie elsewhere these days (CAD/CAM, medical
automation),
so this just didn't really peak my interest enough to spend more time
on. ;)
Does it happen every single start?
Yeah, completely reliable.
One other weirdness showed up too, probably not related though.
Without
QEMU installed, when starting up libvirtd with -l enabled (for
listening),
it exists complaining about missing cert file. That in itself is not
surprising... except it happens even when TLS is disabled is in
libvirtd.conf.
According to the wiki, turning off listen_tls + turning on listen_tcp
should
stop the need for cert files:
http://wiki.libvirt.org/page/The_daemon_cannot_be_started
Does that sound like a bug too, or more like the wiki is out of date?
:)
If you have no certificate installed and you have listen_tls=0 and
listen_tcp=1, it should not be a problem.
k, that's definitely a bug then.
+ Justin
--
libvir-list mailing list
libvir-list@xxxxxxxxxx
https://www.redhat.com/mailman/listinfo/libvir-list