Federa 35 Server default editor
by Peter Boy
In Fedora 34 the default editor was nano, for Workstation and also for Server. In my latest default F35 Server installation I noticed vim-default-editor was installed.
Did some good soul take pity and bring vim back to us or did something go wrong with my installation?
Best
Peter
2 months, 2 weeks
First experiences with beta candidate 1.2
by Peter Boy
I did some testing with beta-1.1 candidate
Installation
Went fine. /etc/resolv.conf a link again, no SELinux ACV messages with first boot any more.
Cockpit
The „Applications“ menu item still doesn’t list any installable applications
The list of installed applications doesn’t contain cockpit-filesharing update. Question is: is that expected or a bug?
@Matthew: When you select File Sharing you get a message "Failed to load NFS services. Is NFS installed or enabled?" (NFS) and "Samba must be configured to include registry. Add `include = registry` to the [global] section of /etc/samba/smb.conf“ (Samba)
Is that intended behaviour or should the rpm install do those adaptations?
And we are still missing localisation for cockpit-filesharing update
Virtualization
Installs flawlessly. The combo of qemu-kvm-core, libvirt, and virt-install now installs 104 packages on a fresh install, instead of 165 with beta 1.1 candidate. Either we will miss something or someone did a great job in housekeeping.
Split name resolution doesn’t work for the libvirt internal network. I’ve to inspect that issue further. Possibly the configuration is still deficient (and not any of the apps).
postgresql
installed flawless
Best
Peter
1 year, 1 month
Just a reminder: Next IRC meeting is April, 6 !
by Peter Boy
Just a reminder:
TODAY there will be NO Server WG IRC meeting! Next regular meeting is April 6, 2022 !
The March has 5 „Wednesdays“ instead of 4 as most months have. Therefore, the gap between our „third Wednesday meeting“ March and „first Wednesday meeting“ April is *3 weeks* this time, instead of the usual 2 weeks.
So everything quite regular, nothing aberrant or missing.
Meet you Wednesday, April 6 - 17:00 UTC
Peter
1 year, 2 months
Updated documentation about installing a virtual machine from Cloud
image in Fedora Server
by Peter Boy
I just updated the article
"Creating a virtual machine using a distribution’s Cloud base image – the example of CentOS“
in staging. It’s basically ready for publication and hence for reviewing, also accidentally still tagged as work in progress. I just want to test the provided configuration script with the latest Fedora Beta candidate.
So, it would be nice if someone would pick it up for commenting and/or reviewing. I would like to remind that reviewing always resulted in a noticeable improvement and is not just a „nice to have“!
Best
Peter
1 year, 2 months
Virtualization libvirt installation problems and errors
by Peter Boy
While testing F36, I ran into a problem installing virtualization support on Fedora Server. Until now we installed qemu-kvm, libvirt, virt-install, and additionally cockpit-machines. That combo installs about 338 packages, at least 200 packages graphical desktop related (X11, wayland, gtk3, even poppler pdf renderer, see [1]). This breaks Fedora Servers fundamental headless core concept and installs lots of unusable and thus locally uncontrolled/unmaintained software.
== In this respect, a correction is urgently needed. ==
=== qemu-kvm ===
The cause of the problem is the use of package QEMU-kvm, which is aimed - hitherto unnoticed - at installation on a graphical desktop and therefore completely correctly assumes the appropriate packages. This in turn relies on the @virtualization group, which is the only public group supporting virtualization installation and is described accordingly in the Fedora documentation (without mentioning the graphical bias).
In principle, the solution is quite simple. The qemu-kvm developers were wise enough to create a qemu-kvm-core group at the same time, which omits all graphical references and allows for an excellent installation on Fedora Server.
=== libvirt ===
Unfortunately, the maintainers of libvirt are far from this wisdom and insist that the libvirt package still relies on qemu-kvm, thus installing all the packages that QEMU-kvm-core omits again anyway. An analogous libvirt-core does not exist. Instead, Daniel Berrange refers to the list of individually available single packages, from which one (i.e. server WG) should please compile and test a suitable mix and watch the libvirt development steps to see if changes to the mix are required (see bug report by Martin Pitt [2]).
== So we need to find a way to reliably determine a working set of libvirt packages for Fedora Server (or change the tool set). ==
Maybe we can find support in Debian/Ubuntu, whose libvirt maintainers have solved the problem, at least according to my first impression.
=== Group virtualization-headless ===
An initial approach to a solution could be the group ==@virtualization-headless==. This is a hidden group (see 'dnf group list -v hidden') that currently does pretty much the same as @virtualization, unfortunately. We could contact the owner and modify the group as required (or create a new group @virtualization-server). We could use that as a means to organize a suitable libvirt mix.
=== Cockpit-machines ===
As a further consequence, the cockpit-machines module is currently effectively unusable. It also has QEMU-kvm defined as a dependency. Even if we fix the libvirt problem with a suitable mix, cockpit-machines would currently undo this effort. Martin Pitt is on the way to fix it, see [3]. But we have to find a solution for F36.
I’ll tag this issue for our next meeting. Any suggestions much appreciated.
[1] https://lists.fedoraproject.org/archives/list/server@lists.fedoraproject....
[2] https://bugzilla.redhat.com/show_bug.cgi?id=2063670
[3] https://github.com/cockpit-project/cockpituous/pull/473
1 year, 2 months
