I’ve just started using KVM here.
SLES docs advise for using the vhost-net module as it’s more efficient. So as root user I did “modprobe vhost-net”, then confirmed with “lsmod | grep vhost”. But after rebooting module is no longer loaded. Is there a way to make it persistent after reboot/shutdown?
I’m not currently using “vhost-net”.
For automatic loading of a module, try
- I tried getting help for lsmod command, but “lsmod --help” only gave a message “usage: lsmod”, and echo $? gave 1, which meant it was an error. This was made as normal user. Does this have consequences for the OS? How can fix?
You should be able to use:
- When first opening virt-manager I saw a grayed-out entry “QEMU/KVM: not connected”; if selecting it there’s the option to “connect”. But connect to what? There are still no VMs whatsoever yet!
It connects to “libvirtd”, which should be running as a service. Installing KVM sets that up. Once I connect, I see a list of virtual machines.
- Is there a more graphical way to open virtual machine manager other than having to open terminal and type “virt-manager”?
I did it by typing “virt” into the menu search of my desktop.
I also installed “ovmf” (well, “ovmf”, “ovmf-tools”, “qemu-ovmf-x86_64”). That gives me the possibility of a UEFI virtual machine.
First virtual install – fedora26 (I had already downloaded the iso). I’ve since deleted that, but I learned something from doing it.
Second virtual install - openSUSE 42.3. I’m normally a KDE person, so I installed Gnome. This was from the iso, already on my system. On screen 5 of setup, there’s a box where I could specify that I wanted extra configuration. That gave me a choice where I could select UEFI. So I did. That virtual machine is running well (except currently not running). Running Yast on that virtual machine, I noticed that it wanted to install “spice-vdagent”. So I allowed that to install. And it’s great. I can now do copy/paste between the main machine and that 42.3 virtual machine.
Third virtual install – Solus. That was a fail. I tried using UEFI. But it seems that the UEFI choice for KVM is locked into secure-boot, and Solus does not do secure-boot.
I redid without UEFI. And that worked. But as soon as I clicked on something with my mouse, the virtual machine captured the mouse. I later discovered that the manual I am reading (“Virtualization Guide - openSUSE 42.3” a pdf file that I downloaded) explains how to deal with that. So now it’s fixed, and Solus no longer captures the mouse. The way that I initially escaped from the captured mouse was to shutdown the virtual machine.
Final installl (for now) – another install of fedora26, this time with UEFI. Since fedora does support secure-boot, I expected that to work, and it did.
I would like to try UEFI without secure-boot. But it looks as if that will require a complicated command line method to specify which virtual firmware file to use.
In any case, I recommend that you try creating a few virtual machines. You can delete them later. Treat it as a learning experience. Maybe start with openSUSE 42.3.
My prior practice was bare metal installs (i.e. direct to computer). I’ll probably still prefer that, but using KVM adds additional choices.