Install KVM&Libvirt on SparkyLinux2020.08

Deployment of simple SparkyLinux2020.08 configuration on bare metal is supposed to be performed with "btrfs" file-systems for "/boot" and "/" .Otherwise virt-manager will report failure of deploying any guest due to /var/lib/libvirt/images/ "folder" , which for Libvirt 6.6.0 && Qemu 5.1.0, should already belong to "btrfs" formatted file-system at least at the time of writing of this post.

Another sample of original partitioning (Calamaris on SparkyLinux)

Install KVM

$ sudo apt install qemu-kvm  \
         libvirt-daemon bridge-utils \
         virtinst libvirt-daemon-system -y

$ sudo apt install virt-top libosinfo-bin \
       qemu-system virt-manager -y


$ sudo modprobe vhost_net
$ lsmod | grep vhost
$ echo vhost_net | sudo tee -a /etc/modules
$ sudo reboot

$ echo vhost_net | sudo tee -a /etc/modules
$ sudo reboot

Following below is verification deployment os SparkyLinux 2020.08 as KVM
guest in environment shown right above
 

   Installed Sparky Guest does automatically rolling forward to the most recent status of it's repos

  Access via Web Cockpit Console

 

Test Day:2020-08-17 Kernel 5.8 on Fedora 32

Install koji
$ sudo dnf install koji -y

Build kernel via koji
$ koji download-build --arch=x86_64 kernel-5.8.2-300.fc32 && sudo dnf update kernel*

[boris@ServerFedora32 ~]$ ls -l  *.rpm
-rw-rw-r--. 1 boris boris    52776 Aug 21 16:08 kernel-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris 34945992 Aug 21 16:10 kernel-core-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris    52884 Aug 21 16:08 kernel-debug-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris 36848900 Aug 21 16:09 kernel-debug-core-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris 14038096 Aug 21 16:10 kernel-debug-devel-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris 31850344 Aug 21 16:08 kernel-debug-modules-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris  2188616 Aug 21 16:08 kernel-debug-modules-extra-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris   171972 Aug 21 16:08 kernel-debug-modules-internal-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris 13943992 Aug 21 16:10 kernel-devel-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris 31182616 Aug 21 16:09 kernel-modules-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris  2110908 Aug 21 16:08 kernel-modules-extra-5.8.2-300.fc32.x86_64.rpm
-rw-rw-r--. 1 boris boris   162120 Aug 21 16:08 kernel-modules-internal-5.8.2-300.fc32.x86_64.rpm
.  .  .  .  .   .  .  .  .  .  .
=================================================================
 Package                        Architecture     Version                     Repository              Size
=================================================================
Installing:
 kernel                         x86_64           5.8.2-300.fc32              @commandline            52 k
 kernel-modules                 x86_64           5.8.2-300.fc32       @commandline            30 M
 kernel-modules-extra           x86_64           5.8.2-300.fc32   @commandline           2.0 M
Installing dependencies:
 kernel-core                    x86_64           5.8.2-300.fc32              @commandline            33 M
Transaction Summary
==================================================================
Install  4 Packages

Total size: 65 M
Installed size: 105 M
Is this ok [y/N]: y
Downloading Packages:
Running transaction check
Transaction check succeeded.
Running transaction test
Transaction test succeeded.
Running transaction
  Preparing        :                                                                                  1/1 
  Installing       : kernel-core-5.8.2-300.fc32.x86_64                                                1/4 
  Running scriptlet: kernel-core-5.8.2-300.fc32.x86_64                                                1/4 
  Installing       : kernel-modules-5.8.2-300.fc32.x86_64                                             2/4 
  Running scriptlet: kernel-modules-5.8.2-300.fc32.x86_64                                             2/4 
  Installing       : kernel-5.8.2-300.fc32.x86_64                                                     3/4 
  Installing       : kernel-modules-extra-5.8.2-300.fc32.x86_64                                       4/4 
  Running scriptlet: kernel-modules-extra-5.8.2-300.fc32.x86_64                                       4/4 
  Running scriptlet: kernel-core-5.8.2-300.fc32.x86_64                                                4/4 
  Running scriptlet: kernel-modules-extra-5.8.2-300.fc32.x86_64                                       4/4 
  Verifying        : kernel-5.8.2-300.fc32.x86_64                                                     1/4 
  Verifying        : kernel-core-5.8.2-300.fc32.x86_64                                                2/4 
  Verifying        : kernel-modules-5.8.2-300.fc32.x86_64                                             3/4 
  Verifying        : kernel-modules-extra-5.8.2-300.fc32.x86_64                                       4/4 

Installed:
  kernel-5.8.2-300.fc32.x86_64                     kernel-core-5.8.2-300.fc32.x86_64                     
  kernel-modules-5.8.2-300.fc32.x86_64             kernel-modules-extra-5.8.2-300.fc32.x86_64            

Complete!
Reboot into new kernel

[boris@ServerFedora32 ~]$ hostnamectl
   Static hostname: ServerFedora32.localdomain
         Icon name: computer-desktop
           Chassis: desktop
        Machine ID: 5596dcdb82ee450494fd8d062605cd6a
           Boot ID: dfa47fc6014f4c1b8ef6b04048bcd1e8
  Operating System: Fedora 32 (Server Edition)
       CPE OS Name: cpe:/o:fedoraproject:fedora:32
            Kernel: Linux 5.8.2-300.fc32.x86_64
      Architecture: x86-64

Per QA:Testcase kernel regressionQA:Testcase kernel regression

*****************************
Setting up testing environment
*****************************
$ sudo dnf install gcc git python3-fedora
$ git clone https://pagure.io/kernel-tests.git
$ sudo dnf install make libtirpc libtirpc-devel policycoreutils-python-utils
$ sudo semanage boolean -m --on selinuxuser_execheap
$ cd kernel-tests
$ cp config.example .config
$ vi .config
*********************************
Starting testing scripts themselves
*********************************
$ sudo ./runtests.sh
$ sudo ./runtests.sh -t performance

Testing done logs have been generated
$ cd logs
$ ls -l
vi kernel-test-1598018939.log.txt
vi kernel-test-1598019040.log.txt
$ sudo semanage boolean -m --off selinuxuser_execheap
===========================================================
Date: Fri 21 Aug 2020 05:08:59 PM MSK
Test set: default
Kernel: 5.8.2-300.fc32.x86_64
Release: Fedora release 32 (Thirty Two)
Result: PASS
Failed Tests: None
Warned Tests: None
============================================================
Date: Fri 21 Aug 2020 05:10:40 PM MSK
Test set: performance
Kernel: 5.8.2-300.fc32.x86_64
Release: Fedora release 32 (Thirty Two)
Result: PASS
Failed Tests: None
Warned Tests: None
============================================================

Attempt to switch MSI X570 A PRO to Legacy BIOS ( just for fun )

***********************
UPDATE on 13/09/2020
***********************

MSI X570 A-PRO BIOS Setup to enable KVM:-

===================================
Go to 
OS MODE =>CPU Features=>SVM=>Enabled (was Disabled). 

It would eliminate "killing KVM by BIOS"in dmesg LOG . 
$ dmesg| grep kvm

[ 4.376968] kvm: Nested Virtualization enabled

[ 4.376978] SVM: kvm: Nested Paging enabled

I sincerely apologize for wrong pinging. Ryzen 5 3600 is OK. MSI X570 A-PRO Setup is hard to analyze

***********************
UPDATE on 15/08/2020
***********************
   Obviously I've turned everything back to UEFI
   I have to notice that either one of options
     1. UEFI
     2. LEGACY+UEFI
     3. LEGACY BIOS
DOESN'T create device /dev/kvm and I still have to care about
UEFI support for KVM guests

I also have to notice that even Ryzen 7 3700X (5 3600 just worse)  shows up pretty pure performance during deployment KVM guests. Looks like I am spoiled by Intel.
***************
END UPDATE
***************  
Officially  only options LEGACY+UEFI and UEFI were available. To install Server F32 on SSD Drive I selected CD-DVD device as boot able. Afterwards everything went fine and system was installed  in pure Legacy BIOS Mode on SSD. Problem has raised up a bit latter after testing via pressing "F11"  I was able to make sure that SSD drive is a primary boot able device and decided to make this configuration static. But any drive from nice line of small pictures
"Boot Priority" gave me a wrong drive.  SSD seemed to be gone  from  "Boot Priority" line.

Three steps which allowed me to set up SSD Drive as primary boot able are shown below
1. Select OS Setting "Boot" menu.

   
Scroll it down to invisible options following up the visible list

Click on first line "Hard Disk Drives BBS priorities". BBS stands for "Bios Boot priority", to get into final selection supposed to bring you to success. Of course, if setting up "Legacy BIOS" in meantime might be associated with word "success".

Select SSD Drive from all options available and press "Enter"  followed by "F10". I believe that this exercise might be a bit more straight forward ( even Legacy BIOS is almost dead ).  
That's why I also believe that board's prices difference between ASUS and MSI is quite reasonable. Just around $100 and $200.