![]() ![]() ![]() The virt-manager GUI dialog does not have a way to specify a non-default ssh port or the private key to use when connecting to the remote server, but this is easily done by starting virt-manager with the ‘-c’ parameter. Sudo apt-get install virt-manager Client test # a more complete install if you are doing any local KVM work Sudo apt-get install virt-manager ssh-askpass-gnome -no-install-recommends ssh -i Client, virt-manager packagesĪt the absolute minimum you need the virt-manager GUI and the utility that prompts for the ssh passphrase. This article does a good job showing how to configure SSH for public key authentication.Īfter enabling public key authentication, you should be able to ssh into the remote host using the local private key. The first requirement is that you are able to use ssh to connect to the remote KVM server using the private key for authentication. ![]() Using the ssh tunneling solution described in this article, the libvirtd service on the server side does *not* need to enable listening on TCP in “/etc/libvirt/nf”. The remote VNC display for these VMs is sent over this same ssh tunnel. In this article I will show how to use virt-manager from an Ubuntu client desktop to a server running KVM and libvirtd, with the connection being tunneled over ssh and authenticated with PKI. You just need to specify the method of communication (ssh, tls, tcp, etc). If you are running KVM on a console-only server, you still have the option to use the graphical virt-manager. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |