libvirt VS ubuntu-asahi

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...

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).

Nvidia 510 introduced a regression you can see the relevant issues here and here

The work to split into multiple daemons started a few years ago.

https://gitlab.com/libvirt/libvirt/-/blob/9b8bb536ff999fa61e...

There have been a few complaints online in the Arch and Gitlab forums regarding this issue. https://gitlab.com/libvirt/libvirt/-/issues/410

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.

It's a bug, fix is upstream: https://gitlab.com/libvirt/libvirt/-/commit/04736179b283f55f62616a20a1ec95c665aab8ca

I used an Asahi Linux distro (Ubuntu Server 22.04LTS) - https://github.com/UbuntuAsahi/ubuntu-asahi as Ubuntu is a supported distro and KVM host in Apache #CloudStack. I want to explore if this can be used as a viable KVM/virtualisation host. After initial install, I had to manually setup openssh and bridge-utils on it. Initial impressions - I was amazed, I knew the new Apple silicon chips are fast (tried on Mac OS) but on Linux on them is really "really" fast while consuming only 5-6W idle and about 20W for full "server" workloads (CPU) and it was very quiet and cool.

I got displaylink dock working with a MacBook M1 on Ubuntu 22.10. Finally 3 screens, we can start consider it as a working station. Thanks to the Asahi Devs and Ubuntu-asahi scripts.

You can install Ubuntu natively via this link: https://github.com/tobhe/ubuntu-asahi

No, the minimal option is Arch Linux without a desktop environment (GUI). Asahi aims to put Linux in general (maybe Ubuntu one day) on the Apple silicon Macs. While there is way to install Ubuntu, it's not supported by the Asahi team. Here it is: https://github.com/tobhe/ubuntu-asahi

On the Alternative Distros wiki page there's a link to a project that let's you install Ubuntu on Asahi Linux. However, I perfer KDE over GNOME, so is there a way to install Kubuntu instead of plain Ubuntu?

Never really seen anybody on the internet write a guide to install Ubuntu on apple silicon based macs, so I’ve decided to come out the public and publish a guide on how to install Ubuntu on apple silicon based macs. First and foremost, go to this GitHub page: https://github.com/tobhe/ubuntu-asahi and run these scripts in the macOS terminal: curl -sL https://tobhe.de/ubuntu/install > install.sh # Download less install.sh # Review sh install.sh # Run

https://github.com/tobhe/ubuntu-asahi is working quite well for me on an M1 Air.