Red Hat Summit23.2. Remote management over TLS and SSL
You can manage virtual machines using TLS and SSL. TLS and SSL provides greater scalability but is more complicated than ssh (see Section 23.1, “Remote management with SSH”). TLS and SSL is the same technology used by web browsers for secure connections. The
libvirt management connection opens a TCP port for incoming connections, which is securely encrypted and authenticated based on x509 certificates. In addition the VNC console for each guest virtual machine will be setup to use TLS with x509 certificate authentication.
This method does not require shell accounts on the remote machines being managed. However, extra firewall rules are needed to access the management service or VNC console. Certificate revocation lists can revoke users' access.
Steps to setup TLS/SSL access for virt-manager
The following short guide assuming you are starting from scratch and you do not have any TLS/SSL certificate knowledge. If you are lucky enough to have a certificate management server you can probably skip the first steps.
-
libvirtserver setup - For more information on creating certificates, see the libvirt website, http://libvirt.org/remote.html.
- Xen VNC Server
- The Xen VNC server can have TLS enabled by editing the configuration file,
/etc/xen/xend-config.sxp. Remove the commenting on the(vnc-tls 1)configuration parameter in the configuration file.The/etc/xen/vncdirectory needs the following 3 files:This provides encryption of the data channel. It might be appropriate to require that clients present their own x509 certificate as a form of authentication. To enable this remove the commenting on theca-cert.pem- The CA certificateserver-cert.pem- The Server certificate signed by the CAserver-key.pem- The server private key
(vnc-x509-verify 1)parameter. -
virt-managerandvirshclient setup - The setup for clients is slightly inconsistent at this time. To enable the
libvirtmanagement API over TLS, the CA and client certificates must be placed in/etc/pki. For details on this consult http://libvirt.org/remote.htmlIn thevirt-manageruser interface, use the '' transport mechanism option when connecting to a host.Forvirsh, the URI has the following format:qemu://hostname.guestname/systemfor KVM.xen://hostname.guestname/for Xen.
To enable SSL and TLS for VNC, it is necessary to put the certificate authority and client certificates into
$HOME/.pki, that is the following three files:
- CA or
ca-cert.pem- The CA certificate. libvirt-vncorclientcert.pem- The client certificate signed by the CA.libvirt-vncorclientkey.pem- The client private key.
'%20d='M201.5%20305.5c-13.8%200-24.9-11.1-24.9-24.6%200-13.8%2011.1-24.9%2024.9-24.9%2013.6%200%2024.6%2011.1%2024.6%2024.9%200%2013.6-11.1%2024.6-24.6%2024.6zM504%20256c0%20137-111%20248-248%20248S8%20393%208%20256%20119%208%20256%208s248%20111%20248%20248zm-132.3-41.2c-9.4%200-17.7%203.9-23.8%2010-22.4-15.5-52.6-25.5-86.1-26.6l17.4-78.3%2055.4%2012.5c0%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.3%2024.9-24.9s-11.1-24.9-24.9-24.9c-9.7%200-18%205.8-22.1%2013.8l-61.2-13.6c-3-.8-6.1%201.4-6.9%204.4l-19.1%2086.4c-33.2%201.4-63.1%2011.3-85.5%2026.8-6.1-6.4-14.7-10.2-24.1-10.2-34.9%200-46.3%2046.9-14.4%2062.8-1.1%205-1.7%2010.2-1.7%2015.5%200%2052.6%2059.2%2095.2%20132%2095.2%2073.1%200%20132.3-42.6%20132.3-95.2%200-5.3-.6-10.8-1.9-15.8%2031.3-16%2019.8-62.5-14.9-62.5zM302.8%20331c-18.2%2018.2-76.1%2017.9-93.6%200-2.2-2.2-6.1-2.2-8.3%200-2.5%202.5-2.5%206.4%200%208.6%2022.8%2022.8%2087.3%2022.8%20110.2%200%202.5-2.2%202.5-6.1%200-8.6-2.2-2.2-6.1-2.2-8.3%200zm7.7-75c-13.6%200-24.6%2011.1-24.6%2024.9%200%2013.6%2011.1%2024.6%2024.6%2024.6%2013.8%200%2024.9-11.1%2024.9-24.6%200-13.8-11-24.9-24.9-24.9z'/%3e%3c/svg%3e){kind=small}