Showing headlines posted by dba477

Please be advised, that in particular case install rpmextract results presence bsdtar on the system and extraction of rpms is supported via CLI $ bsdtar -xf *.rpm . The rest of deployment procedure keeps to be the same as on previous versions of Manjaro linux. So the commands which bring you to successful deployment of Windows 11 KVM Guest should be . .

Mentioned procedure on Fedora 39 Server requires only verification of presence packages edk2-ovmf swtpm swtpm-tools on the system. You are not supposed to experience any problems during deployment Win11 KVM in security mode (virt-manager's setup)

We start as usual ( no convertion is required on openSUSE ) $ sudo rpm -iv virtio-win-0.1.229-1.noarch.rpm . Second step looks a bit strange. I would expect this dependencies to be resolved automatically up on install of package swtpm

Setup Cockpit Web Console on openSUSE 15.5 Leap requires activation an additional repo mentioned first in the post, which by some reasons wasn't activated during standard installation procedure by default. Now proceed as follows . . .

Debian network installer appears to be extremely stable and flexible no matter of version Debian GNU/Linux to be deployed in particular case. I also have to admit that problem with LVM confiruration still persist for the most recent versions of Calamares Installer (3.2.6X), affecting ability for flexible LVM configurations of such distros as SparkyLinux 2023.10 and Manjaro Linux 23.0/5.

Looks like it's hard to associate LVM group with physical volumes created by Gparted when running LMDE 6 installation vs GUI provided by classical Debian Network installer. Either I am missing some technical skills or LMDE 6 just cannot provide standard functionality of Debian Network Installer has been known for a while. Say Debian 10/11/12 at least as far as to my knowledge .

Looks like the only surprising step appeared to be was manual linux bridge configuration via nmcli vs utilizing Cockpit Web Console on almost all Linux free flavors like Fedora,Debian,Manjaro and etc. Original disk layout for openSUSE (L1 Guest) been configured . . .

Ubuntu Server installation is pretty straightforward , then connect via ssh to server instance and install Gnome 45 desktop environment via command $ sudo apt install ubuntu-gnome-desktop. Reboot Ubuntu Server's instance and log into newly installed Gnome 45 environment. Now you are ready to proceed with KVM setup on Ubuntu 23.10

Actually, there is no need to wait for proposed in https://pagure.io/fesco/issue/3066 option by "sgallagh" - "To be clear, my suggestion about providing the WebUI as an experimental option was intended for Final". Load from live image Fedora-Workstation-Live-x86_64-39-20230922.n.0.iso into KVM Guest and shut down Installer afterwards. Keep staying in Fedora39 Live environment and issue . . .

No signs of Anaconda Installer behavior in the screenshots below might be noticed in the Fedora 39 development branch up until 09/16/23. Actually, I've followed link suggested in final rows of article https://www.debugpoint.com/fedora-39-features/ . In particular , the iso image Fedora-Workstation-Live-x86_64-Rawhide-20230916.n.0.iso has been used for virt-manager

Cockpit Client provides a graphical interface to your servers, containers, and virtual machines. Connections are made over SSH, using the SSH configuration of the local user (including aliases, known hosts, key files, hardware tokens, etc).

Sequence of snapshots down here demostrates F39WKS KVM Guest setup via Fedora-39-20230827.n.0 (netinst-everything boot ISO image).

Setup on Ubuntu 22.04.3 is a bit more complicated then on Fedora 38. So I've just put a sequence of all the necessary directives together. I also believe that the same schema would work on Debian BookWorm as well .

Cockpit Client provides a graphical interface to your servers, containers, and virtual machines. Connections are made over SSH, using the SSH configuration of the local user (including aliases, known hosts, key files, hardware tokens, etc). The server needs to have Cockpit installed, but the Cockpit webserver doesn't need to be enabled, and no extra ports need to be opened.

The Python Steering Council has announced its intent to accept PEP 703 (Making the Global Interpreter Lock Optional in CPython), with initial support possibly showing up in the 3.13 release. There are still some details to work out, though.

Upgrade kernel on Manjaro instance up to 6.4.6 via Manjaro Settings Manager and reboot instance. Then issue $ sudo pacman -Syu virtualbox .This command will report you - There are 12 providers available for VIRTUALBOX-HOST-MODULES: Repository extra . If you select option 10 then linux64-virtualbox-host-modules would be installed on your Manjaro 22.1 instance .

On Manjaro Linux we intend to convert virtio-win-0_1_229-1_noarch.rpm to Arch format and install corresponding Arch package as pre-installation step on KVM Hypervisor's Manajaro Linux Host.

Upgrade kernel on Sparky Linux 2023.07 up to 6.4.4-sparky8 via Synaptic Manager . Then atcivate Debian 12 repo per https://linuxiac.com/virtualbox-7-0-10-released/ and proceed as follows . . .

Coming three months after VirtualBox 7.0.8, the new release adds initial support for the Linux 6.4 kernel series for both guests and hosts, initial support for the upcoming Linux 6.5 kernel series only for hosts. Proceed as follows per official Oracle's instructions

Acivate on system following repo $ sudo dnf copr enable jforbes/kernel-stabilization and upgrade system via $ sudo dnf update -y . Make sure that kernel 6.4.2-201 has been installed:

[boris@ServerFedora38 ~]$ rpm -qa | grep kernel | grep "6.4.2" => kernel-devel-6.4.2-201.fc38.x86_64 kernel-devel-matched-6.4.2-201.fc38.x86_64 kernel-6.4.2-201.fc38.x86_64 . . . Now setup rpmfusion . . . .