Skip to content
Permalink
Browse files
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.
  • Loading branch information
wido committed Feb 3, 2014
1 parent 4ae5cb5 commit 4f17c0bf02bfe292972bf631387c1e37c5e9995d
Showing 1 changed file with 0 additions and 5 deletions.
@@ -46,11 +46,6 @@
<para>so it looks like:</para>
<programlisting>libvirtd_opts="-d -l"</programlisting>
</listitem>
<listitem>
<para>In order to have the VNC Console work we have to make sure it will bind on 0.0.0.0. We do this by editing <filename>/etc/libvirt/qemu.conf</filename></para>
<para>Make sure this parameter is set:</para>
<programlisting>vnc_listen = "0.0.0.0"</programlisting>
</listitem>
<listitem>
<para>Restart libvirt</para>
<para>In RHEL or CentOS:</para>

0 comments on commit 4f17c0b

Please sign in to comment.