libvirt
wayland-explorer
libvirt | wayland-explorer | |
---|---|---|
12 | 25 | |
- | 181 | |
- | - | |
- | 7.8 | |
- | 3 days ago | |
TypeScript | ||
- | MIT License |
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)
wayland-explorer
-
PCSX2 Disables Wayland Support
Wayland is good until you hit the corner cases that they decided to abandon, without leaving any alternatives. We can always have extra protocol that can be optionally enabled, but good luck with standardizing that. It feels as if Wayland people are abusing their committee to keep Wayland as-is, instead of extending it. The protocol dashboard[1] doesn't look exactly good.
[1]: https://wayland.app/protocols/
-
Inter-process Communication between two programs on Linux.
Wayland is itself an IPC system (that uses UNIX domain sockets). I would make a custom Wayland protocol (if there isn't already an appropriate one available, look here: https://wayland.app/protocols/). You can define the protocol in XML and generate the boilerplate code in C using wayland-scanner. I assume smithay also has an equivalent of wayland-scanner.
-
The reality of Wayland input methods in 2022
https://wayland.app/protocols/ and https://wayland.freedesktop.org/docs/html/ are just API references.
-
Swingland: Recreating Java Swing for Wayland
Given I will be using most of the Wayland protocol to achieve anything (it's minimal) and Wayland is well specified then the 'start at the bottom and build up' design pattern fits. Wayland has a wire protocol based on a Unix socket, and usefully Java has supported Unix sockets since release 16, so I can write everything in Java to (de)serialise messages. This gets me going quickly, providing positive feedback that I'm on the right track..
-
Red Hat considers Xorg “deprecated” and will remove it in the next RHEL
The core is bare-bones, there are numerous standard protocols since, and many other are in standardization. Here is a site to review their state: https://wayland.app/protocols/
-
Unix philosophy and compositor development
There is some lock-in in some places where tools adopt a protocol that is only implemented by wlroots compositors, or only implemented by KDE, etc, but I suspect this will improve over time as protocols stabilise ( and you can browse the available protocols here: https://wayland.app/protocols/ )
- Wayland Explorer
-
X12
This link comes up in literally every Wayland thread and it is even more bullshit now than it was in 2013 when it was first posted (and it was bullshit then too). It is titled "the real story" but it is quite the opposite.
A few key points:
1) he laughs at how X has a bunch of extensions. https://wayland.app/protocols/ hypocrites much. In 2013, since it was completely unusable, it probably didn't have many. But turns out real world use leads to "useless" features being reimplemented.
2) he complains about how X.org has broad hardware compatibility. As if that's a bad thing. Meanwhile wayland, even now it still doesn't work reliably on half the graphics chips on the market.
3) It complains that certain X features are not fully network transparent. True, but most are and you can detect at runtime and gracefully degrade. Wayland "fixes" this by just dropping the whole feature.
4) it flat-out lies saying the X server does nothing yet it is so much hard to maintain code. The core X protocol provides backward compatibility and is rock solid (and really easy to impelment from scratch btw, someone did it in Javascript for a tutorial for crying out loud). Meanwhile the Wayland compositor keeps accumulating everything because of point 1. Need a screenshot? Add it it the compositor. Need a hotkey? Add it to the compositor. Need drag and drop? Add it to the compositor. Need a notification icon? Add it to the compositor. In X, all those are peer to peer. Graphics are actually a relatively small part of a graphical user interface, something Wayland is still slow to learn.
5) He complains that certain applications are written inefficiently with blocking calls which is inefficient over a network connection. Wayland's calls are ALL blocking and just has no network connection.
6) Complains that X may draw things unnecessarily. Indeed... but there's an extension to disable that. Easy fix. Wayland even uses the same drivers!
- A better way to read Wayland documentation
-
Is it placebo or is X11 more stable than Wayland
So that brings me to Wayland Protocols!. In X11 land, X11 defines a lot of behaviors for you. There is no such definition in Wayland-land by design - this is to give compositors a lot more freedom and flexibility in how they function. It also means that it required time for protocols to develop to cover all of the things that we would need in a desktop window compositor to bring it up to snuff for desktop usage. These protocols evolved through the past 4-5 years of everybody seeing it's shortcomings on a Desktop system compared to a mobile phone based UI. With the latest fractional scaling protocol we have more or less finally "closed the gap" between Wayland and Xorg on the desktop - it's just a matter of compositors implementing full support for all of the protocols people want.
What are some alternatives?
CloverBootloader - Bootloader for macOS, Windows and Linux in UEFI and in legacy mode
Pion WebRTC - Pure Go implementation of the WebRTC API
ubuntu-asahi - Native Ubuntu installations for Apple silicon hardware
kondo - Cleans dependencies and build artifacts from your projects.
swtpm - Libtpms-based TPM emulator with socket, character device, and Linux CUSE interface.
tera - A template engine for Rust based on Jinja2/Django
sbctl - :computer: :lock: :key: Secure Boot key manager
gnome-gesture-improvements - Touchpad gesture improvements for GNOME on Wayland/X11
BootDuet - Boot sector program for booting Intel's EDK Developer's UEFI Emulation (DUET) from hard disk with LBA.
Zip Foundation - Effortless ZIP Handling in Swift
Moby - The Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
rupy - HTTP App. Server and JSON DB - Shared Parallel (Atomic) & Distributed