[libvirt] [PATCH 1/2] qemu: Add support for changing timeout value to open unix monitor socket

Daniel P. Berrange berrange at redhat.com
Fri Jan 24 12:56:43 UTC 2014

On Thu, Jan 23, 2014 at 07:47:54PM +0200, Pavel Fux wrote:
> there are 8 servers with 8 vms on each server. all the qcow images are on
> the nfs share on the same external server.
> we are starting all 64 vms at the same time.
> each vm is 2.5GB X 64vms = 160GB = 1280Gb
> to read all of the data on a 1Gbe interface will take 1280sec = 21.3min
> not all of the image is being read on boot so it takes only 5min

That's interesting, but it still doesn't explain the failures. QEMU will
start listening on its monitor socket before it even opens any of the
disk images. So the time it takes to read disk images on boot should have
no relevance to timeouts waiting for the monitor socket. All it does between
exec of the QEMU binary and listening for the monitor socket is to loaded
libraries QEMU is linked against and load a few misc pieces like BIOS
firmware blobs. I just can't see a reason why this would take anywhere
near 5 minutes - it should be a matter of a few seconds at worst.

|: http://berrange.com      -o-    http://www.flickr.com/photos/dberrange/ :|
|: http://libvirt.org              -o-             http://virt-manager.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: http://entangle-photo.org       -o-       http://live.gnome.org/gtk-vnc :|

More information about the libvir-list mailing list