On Thu, Nov 19, 2009 at 06:24:55PM +0200, Dan Kenigsberg wrote: > we've experience cases where waiting 30 seconds for a qemu monitor to > finish was not enough (slow and busy server with slow storage). that was > with managing qemu processes directly, btw, not with libvirt. however > those case where not common. how about making the timeout configurable > on-site? I think I'd rather we just increased the default timeout here if we know it is not sufficient. A local admin isn't really in a position to know what an appropriate timeout would be. NB, this particular timeout is fairly harmless - no state has been changed at the point this occurrs, so any app getting a timeout here can easily just re-try the same command immediately & again and again if desired. Daniel. -- |: Red Hat, Engineering, London -o- http://people.redhat.com/berrange/ :| |: http://libvirt.org -o- http://virt-manager.org -o- http://ovirt.org :| |: http://autobuild.org -o- http://search.cpan.org/~danberr/ :| |: GnuPG: 7D3B9505 -o- F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :| -- Libvir-list mailing list Libvir-list@xxxxxxxxxx https://www.redhat.com/mailman/listinfo/libvir-list