Hi,
i'm using CloudStack 3.0.2 (as per last official release) and XenServer
6.0.2-53456p (xenenterprise).
After installing some of these hotfixes:
[root@x4 ~]# xe patch-list | grep XS6
name-label ( RO): XS602E002
name-label ( RO): XS602E005
name-label ( RO): XS602E006
name-label ( RO): XS602E003
name-label ( RO): XS602E001
name-label ( RO): XS602E008
name-label ( RO): XS602E009
name-label ( RO): XS602E004
name-label ( RO): XS602E007
VNC terminal get's binded to 127.0.0.1 or localhost instead of binding
to 0.0.0.0, which in turn means, that newly created (restarted?) virtual
instances can not be accessed with WEB proxy console, because connection
to hipervisor host is refused.
[root@x4 ~]# netstat -apltn | grep vnc
tcp 0 0 127.0.0.1:9504 0.0.0.0:*
LISTEN 11695/vncterm
tcp 0 0 127.0.0.1:9505 0.0.0.0:*
LISTEN 12269/vncterm
tcp 0 0 127.0.0.1:5901 0.0.0.0:*
LISTEN 8128/vncterm
tcp 0 0 0.0.0.0:5902 0.0.0.0:* LISTEN
28166/vncterm
tcp 0 0 127.0.0.1:5903 0.0.0.0:*
LISTEN 11251/vncterm
tcp 0 0 127.0.0.1:5904 0.0.0.0:*
LISTEN 11695/vncterm
tcp 0 0 127.0.0.1:5905 0.0.0.0:*
LISTEN 12269/vncterm
tcp 0 0 127.0.0.1:9501 0.0.0.0:*
LISTEN 8128/vncterm
tcp 0 0 0.0.0.0:9502 0.0.0.0:* LISTEN
28166/vncterm
tcp 0 0 127.0.0.1:9503 0.0.0.0:*
LISTEN 11251/vncterm
#####
How can i make newly created (restarted?) virtual instances to bind to
0.0.0.0 again?
#####
We've had a lot of other problems after the upgrade(s), most of them
solved bo manually copying files from cloudstack management server to
hipervisors. Like: NFSSR.py to fix storage template problems. This
problem might be related to files:
/opt/xensource/libexec/vncterm-wrapper or qemu-dm-wrapper but i don't
want to screw around with these on production system myself.
Please advise. Thank you.
Regards,
France
