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:
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.