So the rest of the stuff works fairly easily, however due to renaming, there’s a good chance in Linux Mint 19.X, running the latest version of virt-manager of this writing (1.5.1) you might run into the error: “Error connecting to graphical console: Error opening spice console, SpiceClientGtk missing” The package needed for virt-manager/viewer to properly
In the past I have always used virt-manager from linux, often switching to X11 forwarding to natively run the app in Windows because I had always thought that VNC just didn’t work with KVM, despite seeing posts to the contrary on the interwebs. Turns out, the issue is specifically with RealVNC’s (default) settings. To connect
By default, when creating a new linux worstation, the default username will always be used if you choose to ssh to another machine, unless you wanted to use the username@server method or -l switch and add the username. However you can simply add a configuration option to your ./ssh folder which will always use specific accounts
If you’ve installed Ubuntu 16.04 (in a virtual machine in my case) recently, you’ll find that if you launch Virt-Manager (for controlling KVM hypervisors) you’ll receive an error indicating the you need to install openssh-askpass or similar for Ubuntu. Unfortunately it has a different package name in Ubuntu (as Virt-Manager is a native RedHat product).
This page will be a marker for some of the steps required to get certain projects going. Even though many of these will be assigned to specific virtual machines, wanted to have a page linked to all of them in one spot.