Re: [libvirt] mass create vm errors
2015-08-03 10:01 GMT+03:00 Michal Privoznik <mprivozn(a)redhat.com>:
There has not been much movement in that particular area since
1.2.16.
There's inherent race though: by the time that libvirt detects that a
certain port is free and qemu binds to it. During this window another
process may just allocate the port which will result in the error
message you're seeing.
This is very bad thing in case of mass start , for example when node
dies i have 100-150 vm started at the same time, and sometimes they
running on single host.
Does it possible to create lock for this port when port passed to
qemu, so another process when detect new port don't use it?
One of the solutions may be to use static ports, or make sure that
other
programs don't interfere with the range that's reserved for graphical
sessions (the range can be configured too in qemu.conf).
But if i specify port
ranges in qemu.conf, how this solve my issue? as
i understand libvirt again randomly allocated port for vm...
--
Vasiliy Tolstov,
e-mail: v.tolstov(a)selfip.ru