On 10.01.2013 14:53, Zeeshan Ali (Khattak) wrote:
On Thu, Jan 10, 2013 at 12:06 PM, Michal Privoznik <mprivozn@redhat.com> wrote:
On 09.01.2013 22:38, Zeeshan Ali (Khattak) wrote:
Hi, Too lazy to explain again so I'll just c&p conversation I had about the issue with Eric on IRC:
<zeenix> is timeouts on session libvirt (or in general) something new? <zeenix> libvirtd startup seems to now take a few seconds so Boxes UI is all empty for that amount of time <eblake> it's been around for a while; qemu.conf has settings to control how long it should take <zeenix> unless Boxes is launched before libvirtd timesout <eblake> but there is a relatively new patch that makes the libvirtd -t actually be useful for qemu:///session <zeenix> don't think i ever changed that, at least not recently <zeenix> that could be it <zeenix> i only saw it happening after i update libvirtd (after a month) <eblake> if you're seeing some delays in starting libvirtd, those are probably worth fixing <zeenix> s/update/recently updated/ <zeenix> yeah <zeenix> i'll try to write a test app <zeenix> no need, i can reproduce with virsh :)
[zeenix@z-laptop virt]$ time virsh list Id Name State ----------------------------------------------------
real 0m6.349s user 0m0.016s sys 0m0.010s [zeenix@z-laptop virt]$ time virsh list Id Name State ----------------------------------------------------
real 0m0.024s user 0m0.010s sys 0m0.011s
You can try turning debug logs on and hopefully it will let more light in. To turn them on:
$ cat ~/.config/libvirt/libvirtd.conf log_level=1 log_outputs="1:file:/tmp/libvirtd.log"
Moreover, if you could upload them somewhere then so we all can take a look.
Here you go :)
Yeah, Daniel was right; It's because we are querying capabilities: http://pastebin.com/FA6HWYrS You have too much qemus there :) Libvirt spent ~7 seconds there. Michal