Hi The only thing you can do is to manually set the VNC port (or disable ir), which It is not very convenient. We are considering a solution as the one you propose (VNC table with ports in use) in your email as part of http://dev.opennebula.org/issues/2980
Cheers Ruben On Thu, Jul 17, 2014 at 9:36 AM, Ondrej Hamada <ondrej.ham...@acision.com> wrote: > Hi guys, > we are recently having problems with VNC port conflict. Our recent VM > IDs are arroung number 100000, we keep creating quite a lot of new VMs > and terminating the old ones. But some of the old ones are kept for long > term purposes. Time to time our VMs failed on creation because their > designated VNC port is already used. We have probably met the corner > case as described in http://dev.opennebula.org/issues/2045 > > My question is - is there any way to fix it except disabling VNC? Have > you ever considered keeping a table of reserved VNC ports per host in > OpenNebula's db? > > Thank you in advance > > Ondra > > ________________________________ > This e-mail and any attachment is for authorised use by the intended > recipient(s) only. It may contain proprietary material, confidential > information and/or be subject to legal privilege. It should not be copied, > disclosed to, retained or used by, any other party. If you are not an > intended recipient then please promptly delete this e-mail and any > attachment and all copies and inform the sender. Thank you for > understanding. > _______________________________________________ > Users mailing list > Users@lists.opennebula.org > http://lists.opennebula.org/listinfo.cgi/users-opennebula.org > -- -- Ruben S. Montero, PhD Project co-Lead and Chief Architect OpenNebula - Flexible Enterprise Cloud Made Simple www.OpenNebula.org | rsmont...@opennebula.org | @OpenNebula
_______________________________________________ Users mailing list Users@lists.opennebula.org http://lists.opennebula.org/listinfo.cgi/users-opennebula.org
