To enable vncproxy in your cloud, in addition to running
one or both of the proxies and nova-consoleauth, you need to
configure the following options in
nova.conf on your compute hosts.
[no]vnc_enabled- Defaults to enabled. If this option is disabled your instances will launch without VNC support.vncserver_listen- Defaults to127.0.0.1. This is the address that vncservers will bind, and should be overridden in production deployments as a private address. Applies to libvirt only. For multi-host libvirt deployments this should be set to a host management IP on the same network as the proxies.![[Note]](../common/images/admon/note.png)
Note If you intend to support live migration, you cannot specify a specific IP address for
vncserver_listen, because that IP address will not exist on the destination host. The result is that live migration will fail and the following error will appear in thelibvirtd.logfile in the destination host:error: qemuMonitorIORead:513 : Unable to read from monitor: Connection reset by peer
If you wish to support live migration in your deployment, you must specify a value of
0.0.0.0forvncserver_listen.vncserver_proxyclient_address- Defaults to127.0.0.1. This is the address of the compute host that nova will instruct proxies to use when connecting to instance vncservers. For all-in-one XenServer domU deployments this can be set to 169.254.0.1. For multi-host XenServer domU deployments this can be set to a dom0 management ip on the same network as the proxies. For multi-host libvirt deployments this can be set to a host management IP on the same network as the proxies.novncproxy_base_url=[base url for client connections]- This is the public base URL to which clients will connect. "?token=abc" will be added to this URL for the purposes of auth. When using the system as described in this document, an appropriate value is "http://$SERVICE_HOST:6080/vnc_auto.html" whereSERVICE_HOSTis a public hostname.xvpvncproxy_base_url=[base url for client connections] - This is the public base URL to which clients will connect. "?token=abc" will be added to this URL for the purposes of auth. When using the system as described in this document, an appropriate value is "http://$SERVICE_HOST:6081/console" where SERVICE_HOST is a public hostname.
