Bug #1757
novnc console sometimes bound to wrong vnc port with xen
Status: | Closed | Start date: | 02/06/2013 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | Javi Fontan | % Done: | 0% | |
Category: | Sunstone | |||
Target version: | Release 4.4 | |||
Resolution: | fixed | Pull request: | ||
Affected Versions: | OpenNebula 3.8 |
Description
Hi,
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
(location 4)
(location 0.0.0.0:6014)
Looking at xend.log file, I could find the following parameters were used to deploy the VM :
vnc=1
vnclisten=0.0.0.0
vncdisplay=113
vncunused=1
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.
Regards,
Laurent
Associated revisions
bug #1757: add vncunused to xen deployment
History
#1 Updated by Ruben S. Montero over 7 years ago
- Category changed from Core & System to Sunstone
- Status changed from New to Pending
- Assignee set to Javi Fontan
- Target version set to Release 4.4
#2 Updated by Javi Fontan over 7 years ago
Thanks!
We are adding this parameter to xen deployment file when a port is specified.
#3 Updated by Javi Fontan over 7 years ago
- Status changed from Pending to Closed
- Resolution set to fixed