Our great sponsors
-
-
-
SurveyJS
Open-Source JSON Form Builder to Create Dynamic Forms Right in Your App. With SurveyJS form UI libraries, you can build and style forms in a fully-integrated drag & drop form builder, render them in your JS app, and store form submission data in any backend, inc. PHP, ASP.NET Core, and Node.js.
-
-
cloud-hypervisor
A Virtual Machine Monitor for modern Cloud workloads. Features include CPU, memory and device hotplug, support for running Windows and Linux guests, device offload with vhost-user and a minimal compact footprint. Written in Rust with a strong focus on security.
Phyllome OS itself only officially supports GNOME Shell for the host. But by tweaking its main recipe, replacing gnome-shell with @^kde-desktop-environment (and some other tweaks), a user could actually deploy KDE on the host computer, and still enjoy some virtualization-related tweaks.
As of now, the virtual machine GUI is just [Virtual Machine Manager](https://virt-manager.org/), already packaged for many Linux distro, but with [tweaked defaults](https://github.com/PhyllomeOS/phyllomeos/blob/main/post/configure-vmm-and-desktop.sh).
I have looked into Cockpit. I agree that it is probably the best way forward to manage virtual machines (Kimchi seems nice too).
A taxing overhead would probably arise if a user relies on a complex file-system inside a VM (for instance, ZFS on the host, and BTRFS inside a VM, which is the default for Fedora installation now). The general idea is to keep the top layer as clean and simple as possible, and to not only make a few clear assumptions about the default kind of virtual machine model Phyllome OS will support : as of now, I have settled on a Q35 chipset with EFI (but the virt chipset, from the Cloud Hypervisor project, will ideally replace the Q35 chipset), virtio-devices (and their vhost counterparts, which are running on their own, outside the virtual machine monitor, and are more performant and secured as far as I understand), VFIO, etc.