libvirt
Moby
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
libvirt
-
C++ Exit-Time Destructors
Only in trivial cases. The problem is when another part of the program holds a function pointer (eg callback) into the library which has been unloaded.
libvirt has long been linked with -Wl,nodelete to avoid this:
https://gitlab.com/libvirt/libvirt/-/commit/8e44e5593eb9b89f...
-
Using baremetal Asahi Linux (Ubuntu) on M1 Mac Minis for homelab
So, next I setup cockpit and cockpit-machines, which works to create VMs (via cockpit-machines) but they use tcg/qemu i.e. emulation and no KVM based h/w acceleration - my test VMs were very slow! I figured out while qemu+KVM works on command line, it doesn't work and the culprit was libvirt! After discussing with the good folks on #asahi channel and with tobhe (Ubuntu-Asahi creator), I gathered enough evidence to conclude libvirtd doesn't know the "right" qemu commands to exec and logged my findings to the libvirt project https://gitlab.com/libvirt/libvirt/-/issues/365 (which can probably use some of the community noise, to expedite the fix).
-
linux to linux vms... gpu accel?
Nvidia 510 introduced a regression you can see the relevant issues here and here
- Qemu 7.2.2: command line syntax in libvirt domain changed
-
Red Hat considers Xorg “deprecated” and will remove it in the next RHEL
The work to split into multiple daemons started a few years ago.
https://gitlab.com/libvirt/libvirt/-/blob/9b8bb536ff999fa61e...
- Docker v23.0.2 released -- AppArmor issue fixed?
-
Guest Has Not Initialized the display (yet)
There have been a few complaints online in the Arch and Gitlab forums regarding this issue. https://gitlab.com/libvirt/libvirt/-/issues/410
-
How to fix onboard Intel Bluetooth Error Code 10 on Windows guest
The issue stems from a change in libvirt. Libvirt is responsible for parsing all your VM's XML and turning it into a QEMU command. Somewhere between libvirt version 6.6 and version 6.9, there was a slight change in the way USB devices are passed to QEMU, and obviously libvirt followed suit. As a result, some USB passthrough configurations, such as the MacOS one in the thread, as well as the onboard bluetooth for windows suffered errors.
-
Libvirt 8.2 - <qemu:deviceOverride>
It's a bug, fix is upstream: https://gitlab.com/libvirt/libvirt/-/commit/04736179b283f55f62616a20a1ec95c665aab8ca
- Fedora Guest On KDE + Wayland have poor performance with virtio (virgl + spice)
Moby
- An open framework to assemble specialized container systems
-
Release Radar • March 2024 Edition
Having been featured in our February 2023, and January 2024 Release Radars, Moby is the original Linux Container runtime. This new version adds a bunch of changes to the Docker CLI and Moby itself with additional features. There's bug fixes and enhancements, with the main thing for users to be on the look out for containers that were created using Docker Engine 25.0.0. These containers might have duplicate MAC addresses, and thus must be recreated. The same goes for those containers created with Moby 25.0+ and with user defined MAC addresses. Read up on all these changes in the release notes.
-
Choosing a Name for Your Computer
Formlabs does this as well for their 3d printers, my earliest encounter of this was when Docker started getting popular: https://github.com/moby/moby/blob/master/pkg/namesgenerator/...
- Docker Inc. refuses to patch HIGH vulnerabilities in Docker
-
Do not install Docker Desktop on GNU/Linux systems
Try to use moby instead since that is the engine in Docker.
https://github.com/moby/moby
-
Exploring Podman: A More Secure Docker Alternative
> Podman is designed to help with this by providing stronger default security settings compared to Docker. Features like rootless containers, user namespaces, and seccomp profiles, while available in Docker, aren't enabled by default and often require extra setup.
Seccomp has been enabled by default since 2015: https://github.com/moby/moby/pull/18780
It is true that Rootless isn't enabled by default but its "extra setup" can be done with a single command (`dockerd-rootless-setuptool.sh install`)
- Moby: Block io_uring_* syscalls in default profile
- Io_uring will be blocked by default on Docker
-
OpenZFS 2.2: Block Cloning, Linux Containers, BLAKE3
Perhaps.
Thing is, https://github.com/moby/moby/blob/670bc0a46c4ca03b75f1e72f73... is using https://github.com/mistifyio/go-zfs which features code like `out, err := zfsOutput("get", "-H", key, d.Name)` (Source: https://github.com/mistifyio/go-zfs/blob/master/zfs.go#L315) to get a single zfs property.
Somebody chose to use a library as abstraction that looks good but is implemented as a MVP (nothing wrong with that). "In the future, we hope to work directly with libzfs" should have raised an alarm somewhere, though.
What are some alternatives?
CloverBootloader - Bootloader for macOS, Windows and Linux in UEFI and in legacy mode
podman - Podman: A tool for managing OCI containers and pods.
ubuntu-asahi - Native Ubuntu installations for Apple silicon hardware
containerd - An open and reliable container runtime
swtpm - Libtpms-based TPM emulator with socket, character device, and Linux CUSE interface.
nerdctl - contaiNERD CTL - Docker-compatible CLI for containerd, with support for Compose, Rootless, eStargz, OCIcrypt, IPFS, ...
sbctl - :computer: :lock: :key: Secure Boot key manager
docker-openwrt - OpenWrt running in Docker
BootDuet - Boot sector program for booting Intel's EDK Developer's UEFI Emulation (DUET) from hard disk with LBA.
ofelia - A docker job scheduler (aka. crontab for docker)
wayland-explorer - Easily browse and read Wayland protocols documentation
k3d - Little helper to run CNCF's k3s in Docker