kvm: It's no longer required to have VNC listen in 0.0.0.0
authorWido den Hollander <wido@widodh.nl>
Mon, 3 Feb 2014 11:37:17 +0000 (12:37 +0100)
committerWido den Hollander <wido@widodh.nl>
Mon, 3 Feb 2014 11:37:17 +0000 (12:37 +0100)
commit4f17c0bf02bfe292972bf631387c1e37c5e9995d
tree81dd6bb061693f2ec31de7540485ecb866853a4a
parent4ae5cb519cc2aa6ea806461a6972a1108a070384
kvm: It's no longer required to have VNC listen in 0.0.0.0

In both the master and 4.3 branch there is a patch which sets
the VNC address to the private IP of the hypervisor and during
migration this will be changed to the private IP of the destination
hypervisor.

Binding VNC on 0.0.0.0 is a potential security issue with the hypervisors
also have a public IP address and the VNC ports are not firewalled.
en-US/hypervisor-host-install-libvirt.xml