[jira] [Created] (CLOUDSTACK-8297) vnc listen address

["Alex Roshchin (JIRA)" <ji...@apache.org>]

Alex Roshchin created CLOUDSTACK-8297:
-----------------------------------------

             Summary: vnc listen address
                 Key: CLOUDSTACK-8297
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-8297
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
          Components: KVM
    Affects Versions: 4.4.2
         Environment: Ubuntu 14.04 LTS 64bit
            Reporter: Alex Roshchin


We have a multiple network interfaces on the hypervisor nodes and after starting VM qemu process binds VNC to the specific IP address but not to the 0.0.0.0 or the one I need. As I know this is not bug it is not listening on 0.0.0.0, but with a multiple network interfaces it's not suitable as qemu binds to the random IP without an option to specify bind address.

For example, we have the following IP/interfaces on hypervisor node:

eth0 172.16.2.101
eth0:2 172.16.3.102
eth2 192.168.2.101
eth2:2 192.168.3.102

After starting VM qemu listening for VNC on 192.168.3.102:3: 

ps ax|grep qemu
...
qemu-system-x86_64 ..... -vnc 192.168.3.102:3,password

So, it listenening only on 192.168.3.102, but this is not I need as in my config 192.168.3.102 is used for another purposes but not for the cloudstack.

If I'll remove this IP alias, restart cloudstack-agent and stop and run same VM again then it will bind to another IP address.

This is a problem for those who have multiple IP interfaces/aliases and not all of them is used for CloudStack.

I think it is necessary to have an option to specify an IP address VNC should listet to.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)