novnc console sometimes bound to wrong vnc port with xen
|Assignee:||Javi Fontan||% Done:|
|Target version:||Release 4.4|
|Affected Versions:||OpenNebula 3.8|
I've had the following issue yesterday. Using novnc console, I've noticed that I was connected to the wrong vm.
WMID=113 but vnc port was actually 6014 (5900+114) instead of 6013 on the xen server.
- xm list one-113 -l | grep location
Looking at xend.log file, I could find the following parameters were used to deploy the VM :
which is mostly OK excepted vncunused=1 which tells the xen server to use the next available port starting from 5900.
vncdisplay and vncunused are opposite options. vncunused should be set to 0 when using vncdisplay.
I see no mention of vncunused parameter either in opennebula deployment files nor in source code. So vncunused=1 is kind of a default.
I've had the issue for several vms which had vncport shifted +1. I'm not sure the first cause of my problem is here, but, even if it works most of the time, this should be fixed.