Install KDE Plasma on SparkyLinux GameOver 08/11 2020

At the time of writing KDE Plasma install  on any SparkyLinux 2020.09 might be committed via GDM3 installation right after KDE Plasma ( the last one via tasksel or CLI ) due to after system reboot GDM seems to be the only one DM on Sparky detecting previously installed KDE.

Roll forward Sparky Linux up to current repositories state.

1. Run taskel installing 

* Debian Desktop environment

* KDE Plasma

2. Run

$ sudo apt install gdm3 -y

During installation set gdm3 as default DM . This is the only one DM detecting presence of previously installed KDE Plasma in meantime. Reboot and select option "plasma" via clicking on gear in right down corner of login screen 

Another screenshot

Setting up graphical login into KDE Plasma via SDDM on CentOS 8.2

# dnf install https://dl.fedoraproject.org/pub/epel/epel-release-latest-8.noarch.rpm
# dnf --enablerepo=epel,PowerTools group \
  -y install "KDE Plasma Workspaces" "base-x"

# sudo systemctl set-default graphical.target
# sudo systemctl enable sddm

# reboot

Simple Desktop Display Manager (SDDM) is a display manager (a graphical login program and session manager) for the X11 and Wayland windowing systems. SDDM was written from scratch in C++ and supports theming via QML. Languages used: C++ Developer: KDE.

 

Setting up KVM Hypervisor on SparkyLinux 2020.9 rolled forward up to 11/08/2020 (VENV)

UPDATE 11/08/2020  

   Sparky 2020.09 (UEFI mode)  rolled forward all the way through up to the time of writing behaves same way on bare metal .

END UPDATE

Due to Libvirt version 6.8.0 there is no more any problems with deployment KVM Guests on EXT4 file system, compare with http://lxer.com/module/newswire/view/290245/index.html

 Deploy SparkyLinux 2020.9 ( rolled forward up to 11/08/2020 ) as KVM guest on F33 Server as follows

VM has been deployed in legal BIOS mode on EXT4 filesystems

Issue with Btrfs in Libvirt 6.6.0 has been fixed in Libvirt 6.7.0 release.

Bug fixes : Fix logic in setting COW flag on btrfs

When COW is not explicitly requested to be disabled or enabled, then libvirt should do nothing on non-BTRFS file systems.

See for details http://lxer.com/module/forums/t/36708/

There is no any more any problems with deployment KVM L2 Guests on EXT4 FS 

Install KVM

 $ sudo apt install qemu-kvm  libvirt-daemon bridge-utils \
         virtinst libvirt-daemon-system -y
 $ sudo apt install libguestfs-tools libosinfo-bin \
       qemu-system virt-manager -y
 $  sudo modprobe vhost_net 
 $  lsmod | grep vhost
 $  echo vhost_net | sudo tee -a /etc/modules
 $  sudo reboot

 Install Web Cockpit Console

 $  sudo apt install install cockpit cockpit-machines
 $  sudo apt install cockpit cockpit-machines
 $  sudo systemctl start cockpit.socket
 $  sudo systemctl enable cockpit.socket

 Tuning firewall
 $  sudo apt install firewalld
 $  sudo firewall-cmd --add-service=cockpit --permanent
 $  sudo firewall-cmd --reload