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.
qemu
-
QEMU AioContext removal and how it was done
https://gitlab.com/qemu-project/qemu/-/blob/master/hw/scsi/s...
QEMU's IOThreads allow the user to configure the threads and get something similar to thread per core architecture. But if 1 thread becomes a bottleneck, then some form of thread synchronization is needed again even with thread per core architecture. Some problems can be parallelized and they work well with thread per core.
-
Why are Apple Silicon VMs so different?
Add `ENV ERL_FLAGS="+JPperf true"` to your Dockerfile and it will build just fine cross platform. The flag just changes some things during build time and won’t affect runtime performance.
[1] https://gitlab.com/qemu-project/qemu/-/issues/1034
-
RISC-V Vector benchmark results
> I don't know how rdcycle works on qemu.
That's a good question! I had to look it up myself ...
Obviously qemu TCG isn't a cycle-accurate emulation. Using RDCYCLE / reading the corresponding CSR eventually calls https://gitlab.com/qemu-project/qemu/-/blob/69680740eafa1838... which calls cpu_get_host_ticks is basically an arch-independent wrapper around RDTSC.
So it just measures the time taken to run using RDTSC. Which I guess is what you would want (maybe?). It would measure the time taken to emulate the vector instruction in host instructions.
> This benchmark is more meant for developers to figure out how to vectorize algorithms effectively, as in which instructions to choose.
Absolutely, I'm not saying the qemu results would say anything very deep, but they're kind of interesting from the point of view of either optimizing qemu or if you have to use qemu because the hardware you want isn't available / isn't cheap enough.
-
The IMPOSSIBLE RISCV HACK: Vector Extension 0.7.1-draft w/ current Linux kernel! – René Rebe
I see the commits that started switch support from RVV 071 to 100 start here, https://gitlab.com/qemu-project/qemu/-/commit/9ec6622db30df1c00d863c1ffc33341f9e0a534d
-
I booted Linux 292,612 times
>> https://gitlab.com/qemu-project/qemu/-/issues/1696 ]
> Can I please just get the detail in mail instead of having to go look at random websites?
Maybe it's me but if I did boot boot linux 292.612 times to find a bug, you might as well click a link to a repository of a major open source project on a major git hosting service.
Is it really that weird to ask people online to check a website? Maybe I don't know the etiquette of these mail lists so this is a geniune question.
-
Rise: Accelerate the Development of Open Source Software for RISC-V
Capstone is used[1] by QEMU as disassembly engine in debug logs and in monitor mode debugger, by the way, so it's in the scope of the RISE effort.
[1] https://gitlab.com/qemu-project/qemu/-/blob/master/disas/cap...
-
Intel Arc 750 Crashes Host + Display Cable Workaround not needed anymore (Windows)
A user on the qemu bugtracker found a way to get the Intel Arc working across resets without crashing the host: Just don't passthrough the audio device of the GPU and everything works!
- Qemu 7.2.2: command line syntax in libvirt domain changed
- Anyone know if there's a way to disable ReBar on only one GPU?
-
[RFT] Allow QEMU to expose static REBAR capability
[1]https://gitlab.com/qemu-project/qemu/-/commit/3412d8ec9810b819f8b79e8e0c6b87217c876e32 [2]https://gitlab.com/alex.williamson/qemu/-/commit/9a6d1822a2bd55f5dee1aec1b6529ae57949d5ba.patch
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)
What are some alternatives?
gcc
CloverBootloader - Bootloader for macOS, Windows and Linux in UEFI and in legacy mode
riscv-binutils-gdb - RISC-V backports for binutils-gdb. Development is done upstream at the FSF.
ubuntu-asahi - Native Ubuntu installations for Apple silicon hardware
nbdkit
swtpm - Libtpms-based TPM emulator with socket, character device, and Linux CUSE interface.
safeclib - safec libc extension with all C11 Annex K functions
sbctl - :computer: :lock: :key: Secure Boot key manager
lzbench - lzbench is an in-memory benchmark of open-source LZ77/LZSS/LZMA compressors
BootDuet - Boot sector program for booting Intel's EDK Developer's UEFI Emulation (DUET) from hard disk with LBA.
CLK - A latency-hating emulator of: the Acorn Electron and Archimedes, Amstrad CPC, Apple II/II+/IIe and early Macintosh, Atari 2600 and ST, ColecoVision, Enterprise 64/128, Commodore Vic-20 and Amiga, MSX 1/2, Oric 1/Atmos, early PC compatibles, Sega Master System, Sinclair ZX80/81 and ZX Spectrum.
wayland-explorer - Easily browse and read Wayland protocols documentation