#libvirt — Public Fediverse posts

So it begins...

I'd never thought a small ARM machine for ~600€ could be a good deal... that was before the RAMPocalypse...

The Minisforum MS-R1 comes with 64GB LPDDR5 ECC RAM.
Thankfully I still had a spare KingSpec XG7000 2TB m.2 NVME SSD

The CIX P1 CP8180 CPU is very new and Kernel upstreaming started in ernest with 2.6.19 but mainline is far from useable and the Debian Bookworm image that Minisforum provides is... a bit old.

However Ubuntu has a working Image
of 26.06 LTS that I used to install my machine with.

Working 10Gbit Ethernet and Wifi is nice.

Chimera Linux sits happily in a QEMU/KVM running on the same machine.

Next step: get the needed bits into Chimera but not while it's so hot around here.

#screenshot #minisforumMsR1 #ubuntu #chimeralinux #libvirt #virtmanager #kdeplasma #aarch64 #arm64 #cixP1 #cixCp8180

Iată o postare optimizată pentru Mastodon despre noul stack HWE de virtualizare pentru Ubuntu 26.04 LTS, direct în limba română și fără menționarea vreunei surse:

🖥️ Ubuntu 26.04 LTS primește un stack opțional HWE pentru virtualizare!

Canonical extinde conceptul de Hardware Enablement (HWE) – folosit până acum în special pentru kernel – și către tehnologiile de virtualizare. Administratorii de sistem pot acum accesa cele mai noi versiuni ale pachetelor de virtualizare direct pe sistemele Ubuntu 26.04 LTS, fără a renunța la stabilitatea oferită de o versiune cu suport pe termen lung.

✨ Principalele detalii despre HWE-ul de virtualizare:

📦 Componente modernizate în mod continuu:
• Include pachetele dedicate qemu-hwe, libvirt-hwe, edk2-hwe (firmware OVMF) și seabios-hwe.
• Aceste pachete vor primi actualizări dinamic la fiecare 6 luni, preluând versiunile din lansările interimare Ubuntu.

🔐 Sincronizare cu tehnologiile moderne de Confidențialitate (AMD SEV-SNP & Intel TDX):
• Facilitează adoptarea rapidă a noilor funcționalități hardware pentru Confidential Computing, AI confidențial și izolare avansată a mașinilor virtuale.

⚙️ Complet opțional și sigur:
• Instalările standard vor păstra versiunile implicite de virtualizare. Activarea se face la alegerea administratorului.
• Canonical oferă instrumentul ubuntu_virt_helper pentru a gestiona întregul stack ca un ansamblu unificat, prevenind neconcordanțele de versiuni între QEMU, libvirt și firmware.

🚀 Soluția ideală pentru centre de date și Cloud:
• Elimină dilema de a alege între o versiune interimară cu pachete noi și o versiune LTS stabilă – oferind acum ce este mai bun din ambele lumi.

O evoluție excelentă pentru infrastructura enterprise pe Linux! 🚀

#Ubuntu #Ubuntu2604 #Virtualization #QEMU #libvirt #KVM #SysAdmin #OpenSource #CloudComputing #LinuxServer #TechNews

Iată o postare optimizată pentru Mastodon despre noul stack HWE de virtualizare pentru Ubuntu 26.04 LTS, direct în limba română și fără menționarea vreunei surse:

🖥️ Ubuntu 26.04 LTS primește un stack opțional HWE pentru virtualizare!

Canonical extinde conceptul de Hardware Enablement (HWE) – folosit până acum în special pentru kernel – și către tehnologiile de virtualizare. Administratorii de sistem pot acum accesa cele mai noi versiuni ale pachetelor de virtualizare direct pe sistemele Ubuntu 26.04 LTS, fără a renunța la stabilitatea oferită de o versiune cu suport pe termen lung.

✨ Principalele detalii despre HWE-ul de virtualizare:

📦 Componente modernizate în mod continuu:
• Include pachetele dedicate qemu-hwe, libvirt-hwe, edk2-hwe (firmware OVMF) și seabios-hwe.
• Aceste pachete vor primi actualizări dinamic la fiecare 6 luni, preluând versiunile din lansările interimare Ubuntu.

🔐 Sincronizare cu tehnologiile moderne de Confidențialitate (AMD SEV-SNP & Intel TDX):
• Facilitează adoptarea rapidă a noilor funcționalități hardware pentru Confidential Computing, AI confidențial și izolare avansată a mașinilor virtuale.

⚙️ Complet opțional și sigur:
• Instalările standard vor păstra versiunile implicite de virtualizare. Activarea se face la alegerea administratorului.
• Canonical oferă instrumentul ubuntu_virt_helper pentru a gestiona întregul stack ca un ansamblu unificat, prevenind neconcordanțele de versiuni între QEMU, libvirt și firmware.

🚀 Soluția ideală pentru centre de date și Cloud:
• Elimină dilema de a alege între o versiune interimară cu pachete noi și o versiune LTS stabilă – oferind acum ce este mai bun din ambele lumi.

O evoluție excelentă pentru infrastructura enterprise pe Linux! 🚀

#Ubuntu #Ubuntu2604 #Virtualization #QEMU #libvirt #KVM #SysAdmin #OpenSource #CloudComputing #LinuxServer #TechNews

New blog post!

Set up a stack of virtualization tools on a Void Linux host for creating and managing virtual machines (VMs):

https://www.dwarmstrong.org/void-libvirt/

#Virtualization #KVM #Qemu #Libvirt #VoidLinux #Linux

New blog post!

Set up a stack of virtualization tools on a Void Linux host for creating and managing virtual machines (VMs):

https://www.dwarmstrong.org/void-libvirt/

#Virtualization #KVM #Qemu #Libvirt #VoidLinux #Linux

Neuer Quick-Tipp im Blog: Wie sichert man eine laufende VM, ohne sie runterzufahren – und zieht danach Debian von Bookworm auf Trixie hoch?

Snapshot mit virsh, kopieren mit rsync (resume-fähig!), Overlay sauber zurückcommitten. Und dann die eigentliche Stolperfalle: der Sprung von PHP 8.2 auf 8.4 und was das für WordPress-Plugins bedeutet.

https://just-stuff.blog/vm-sichern-debian-bookworm-trixie-upgrade/

#Debian #Trixie #libvirt #virsh #WordPress #PHP #linux #blog #upgrade

Transfer 2.0, или Как я перестал бояться и полюбил миграции облачных серверов

Привет, Хабр! Меня зовут Денис, я тимлид инфраструктурной Core команды в Timeweb Cloud. Итак... представьте обычную виртуальную машину клиента. Она принимает запросы, пишет в базу, держит файловый кэш, обновляет память, что-то постоянно меняет на диске. А теперь нам нужно перевезти её с одной физической ноды на другую так, чтобы клиент не заметил переезд. Звучит просто, пока не вспоминаешь, что у виртуальной машины есть память, диски, снапшоты, сетевые настройки, разные формат хранилищ, отличающиеся модели и вендоры CPU и состояния в базе управления. Любая из этих деталей может превратить задачу типа «перенести сервер» в ручную операцию с окном обслуживания, тикетом в поддержку и нервным инженером у консоли. Мы переписали модуль миграции VDS так, чтобы эти детали стали частью алгоритма, а не частью ночной операционной инструкции. В этой статье расскажу, как мы устроили живые миграции на базе libvirt, зачем оставили rsync , почему перешли на NBD для активных дисков, как выбираем RDMA или TCP, что дают SYNC_WRITES , ZEROCOPY , DETECT_ZEROES , AUTO_CONVERGE и другие флаги, и почему всё это важно не только инженерам, но и бизнесу. Кодовые фрагменты взяты из реального модуля управляющего трансферами. Они немного сокращены и упрощены для статьи, но отражают настоящую логику. В целом материал будет полезен как сетевым инженерам, так и пользователям, для понимания всех внутренних процессов — что и как устроено и почему работает так, как работает.

https://habr.com/ru/companies/timeweb/articles/1045384/

#kvm #timeweb_статьи #nbd #qemu #libvirt #live_migration #rdma #itинфраструктура #облачные_сервисы

Опыт разработки российской платформы виртуализации с нуля: libvirt, cgroups v2 и почему это никому не нужно

Виртуализация в России — тема горячая. VMware ушёл, Hyper‑V под вопросом, Proxmox — открытый, но не «суверенный». Я задался вопросом: а можно ли написать платформу управления KVM с нуля, с полным контролем ресурсов через cgroups v2, без единой строки GPL‑кода? Спойлер: да . Встречайте Eskvisor — мой проект, переросший в зарегистрированную в Роспатенте программу для ЭВМ. Под капотом — архитектура, грабли с cgroups, и почему полностью суверенный проект был мертворожденным.

https://habr.com/ru/articles/1046175/

#российское_по #импортозамещение_по #производительность_вм #виртуальные_машины #libvirt #cgroups_v2 #python #системное_администрирование

For whom it may concern. If you like this, don't be shy, click that 👍 button. tiny.cc/qemu-ga-how2 #gnome #boxes #libvirt #qemu #Virsh (more clicks = more chances)

GNOME Boxes: Linux host, Windo...

For whom it may concern. If you like this, don't be shy, click that 👍 button. https://tiny.cc/qemu-ga-how2 #gnome #boxes #libvirt #qemu #Virsh (more clicks = more chances)

For whom it may concern. If you like this, don't be shy, click that 👍 button. https://tiny.cc/qemu-ga-how2 #gnome #boxes #libvirt #qemu #Virsh (more clicks = more chances)

Heute fragte mich ein Freund, warum ich kein #PROXMOX sondern plain #QEMU/KVM und #libvirt nutze oder "antue". Nun zum einen nutze ich #Ansible als Orchestrierungswerkzeug, zum anderen steht mein Server (zwei physische CPUs) bei mir im Keller und darauf laufen 38 VMs.
Wozu sollte ich da mir da #VME antun? Das läuft seit Jahren ohne großen Probleme seit #CentOS 5, 6, 7, 8, Stream und nunmehr #Archlinux out oft the box, Lizenzkostengedöns.

Just an fyi when you're updating from 25.11 to 26.05, are using #libvirt and have been too lazy to properly setup your TPM (e.g. because you're using it for the other OS on a dual boot system)

Then it won't start after updating to 26.05 anymore thanks to some change in the systemd this gem here now shows up in the logs....

(virt-secret-init-encryption.service is a dependency of the libvirtd.service unit)

Anyone know how to configure the TPM so that it works for both OSes?

#NixOS #Nix

Just an fyi when you're updating from 25.11 to 26.05, are using #libvirt and have been too lazy to properly setup your TPM (e.g. because you're using it for the other OS on a dual boot system)

Then it won't start after updating to 26.05 anymore thanks to some change in the systemd this gem here now shows up in the logs....

(virt-secret-init-encryption.service is a dependency of the libvirtd.service unit)

Anyone know how to configure the TPM so that it works for both OSes?

#NixOS #Nix

@kimmosurakka @Ciantic So #libvirt is innocent here. This is how systemd escapes device path - a hyphen means a slash, so the actual hyphen needs to be escaped. See systemd-escape(1)

@kimmosurakka @Ciantic So #libvirt is innocent here. This is how systemd escapes device path - a hyphen means a slash, so the actual hyphen needs to be escaped. See systemd-escape(1)

@kimmosurakka @Ciantic Probably #libvirt is being overly cautious.

@kimmosurakka @Ciantic Probably #libvirt is being overly cautious.

My favorite hobby is my #homelab. It’s where I continuously improve my Unix administration and networking skills. It took me basically all weekend but I have my home lab completely isolated and virtualized on an 8th gen i7 Dell OptiPlex 7060 with 32GB of RAM. I also have a 14TB Iron Wolf HD

The hardest part was setting up the virtual network. I’d never done that kind of thing manually. I’d just used whatever default network that #libvirt created for me. This was hard and did require googling and reading #manpages. The problem with the wizard that creates networks is there’s no option for both DNAT and SNAT.

I learned a lot and got it working perfectly despite the garbage #verizon CR1000A router and its notorious bug. Yeah, you can’t add static routes. So I’m in a double NAT situation. Turns out this is okay because it effectively isolates the homelab. All I had to do was add static routing on my laptop and desktop.

Nobody else will be able to access my homelab unless they know its network and gateway addresses, much less how to configure a static route. It’s basic but works.

My favorite hobby is my #homelab. It’s where I continuously improve my Unix administration and networking skills. It took me basically all weekend but I have my home lab completely isolated and virtualized on an 8th gen i7 Dell OptiPlex 7060 with 32GB of RAM. I also have a 14TB Iron Wolf HD

The hardest part was setting up the virtual network. I’d never done that kind of thing manually. I’d just used whatever default network that #libvirt created for me. This was hard and did require googling and reading #manpages. The problem with the wizard that creates networks is there’s no option for both DNAT and SNAT.

I learned a lot and got it working perfectly despite the garbage #verizon CR1000A router and its notorious bug. Yeah, you can’t add static routes. So I’m in a double NAT situation. Turns out this is okay because it effectively isolates the homelab. All I had to do was add static routing on my laptop and desktop.

Nobody else will be able to access my homelab unless they know its network and gateway addresses, much less how to configure a static route. It’s basic but works.

I think I've worked out what was wrong with my VMs on Fedora 44.

Looks like the firewall rules that Docker sets up do not play well with the ones libvirtd adds.

Forcing Docker to use nftables rather than iptables/firewalld appears to fix things

https://github.com/moby/moby/issues/52612

https://bugzilla.redhat.com/show_bug.cgi?id=2466836

#Fedora #Fedora44 #Docker #libvirt

I think I've worked out what was wrong with my VMs on Fedora 44.

Looks like the firewall rules that Docker sets up do not play well with the ones libvirtd adds.

Forcing Docker to use nftables rather than iptables/firewalld appears to fix things

https://github.com/moby/moby/issues/52612

https://bugzilla.redhat.com/show_bug.cgi?id=2466836

#Fedora #Fedora44 #Docker #libvirt

Anybody else seeing network problems with Boxes/Libvirt VMs on Fedora 44?

I imported an existing disk image and tried to create a new from a Ubuntu ISO and neither get NAT network access.

If so please add any details from here:

https://bugzilla.redhat.com/show_bug.cgi?id=2466836

#Fedora #libvirt

Anybody else seeing network problems with Boxes/Libvirt VMs on Fedora 44?

I imported an existing disk image and tried to create a new from a Ubuntu ISO and neither get NAT network access.

If so please add any details from here:

https://bugzilla.redhat.com/show_bug.cgi?id=2466836

#Fedora #libvirt

I've imported a VM disk image into Fedora 44 boxes (I forgot to export the XML) and while it has got a IP address on the default network it doesn't appear to have access to the outside world (no NAT).

Anybody know how to enable it?

#Fedora44 #Fedora #libvirt

I've imported a VM disk image into Fedora 44 boxes (I forgot to export the XML) and while it has got a IP address on the default network it doesn't appear to have access to the outside world (no NAT).

Anybody know how to enable it?

#Fedora44 #Fedora #libvirt

PSA for anyone using #QEMU #KVM for #SingleGPUPassthrough
Guides are all over the net suggesting hooks scripts invoking pci devices, unloading/loading kernel modules, and other unnecessary things. Here's my current hook script for starting the VM:

systemctl stop display-manager

That's it. And the reverse for teardown:

systemctl start display-manager

#IOMMU groups still apply, and you need to pass the correct PCI devices to your VM, but everything else is handled automatically.

Disclaimer that this is how it works currently for my AMD card. I did have a working setup with my NVIDIA card that did unload/load kernel modules, however it seems things have come a long way since I set that up.

#virtualization #libvirt #vfio

Asking the same question here as well.

When using libvirtd/qemu+kvm what is your preferred way for sharing a folder with a huge dataset >50TB into multiple guests especially in the case where you want the VM to be network isolated.

Are you using:
* the filesystem-"device": virtiofs, virtio-9p, mtp
* the disk-device: with dir-source
* link-local network with: NFS, SMB, ...
* a different architecture entirely?

See full question: https://www.reddit.com/r/HomeServer/comments/1skp5u5/storage_pass_through_without_to_libvirtqemu_vm/

#qemu #kvm #libvirt #NixOS #Homelab

Asking the same question here as well.

When using libvirtd/qemu+kvm what is your preferred way for sharing a folder with a huge dataset >50TB into multiple guests especially in the case where you want the VM to be network isolated.

Are you using:
* the filesystem-"device": virtiofs, virtio-9p, mtp
* the disk-device: with dir-source
* link-local network with: NFS, SMB, ...
* a different architecture entirely?

See full question: https://www.reddit.com/r/HomeServer/comments/1skp5u5/storage_pass_through_without_to_libvirtqemu_vm/

#qemu #kvm #libvirt #NixOS #Homelab

Headless. Fast. Surgical. KVM is a battle-tested tool in the Architect's armory.

https://silentarchitect.org/2026/03/architects-kvm-manual.html

#kvm #qemu #hypervisor #virtualization #libvirt #virtinstall #architect

Apparently there is no way to run dhcpd that binds to individual interface and #libvirt network on the same host. The solutions are:

1. Find a dhcpd that binds to *:67 (and then only responds to configured interfaces/networks), or
2. Manage the libvirt bridge network interface manually, or
3. Hack libvirt with a custom patch, or
4. Create a separate interface with different dhcpd port, and bind the dhcpd to that interface and prot. Forward dhcp packets from the desired interface to this custom interface and port.

I found this out the hard way when I planned to replace isc-dhcp-server with kea-dhcp4-server.

Apparently the kernel errors out if different applications want to bind to UDP *:port and UDP interface:port. Multiple apps binding to UDP *:port is fine and that is why isc-dhcp-server works with libvirt.

Two apps binding to different UDP interface0:port and interface1:port are of course ok, but unfortunately libvirt generates the bridge dnsmasq config in a way that doesn't allow specifying the specific interface for binding or excluded interfaces: https://github.com/libvirt/libvirt/blob/3f3cb3ab51740c30f1016c4fe657c48a14cc8462/src/network/bridge_driver.c#L1144

Apparently there is no way to run dhcpd that binds to individual interface and #libvirt network on the same host. The solutions are:

1. Find a dhcpd that binds to *:67 (and then only responds to configured interfaces/networks), or
2. Manage the libvirt bridge network interface manually, or
3. Hack libvirt with a custom patch, or
4. Create a separate interface with different dhcpd port, and bind the dhcpd to that interface and prot. Forward dhcp packets from the desired interface to this custom interface and port.

I found this out the hard way when I planned to replace isc-dhcp-server with kea-dhcp4-server.

Apparently the kernel errors out if different applications want to bind to UDP *:port and UDP interface:port. Multiple apps binding to UDP *:port is fine and that is why isc-dhcp-server works with libvirt.

Two apps binding to different UDP interface0:port and interface1:port are of course ok, but unfortunately libvirt generates the bridge dnsmasq config in a way that doesn't allow specifying the specific interface for binding or excluded interfaces: https://github.com/libvirt/libvirt/blob/3f3cb3ab51740c30f1016c4fe657c48a14cc8462/src/network/bridge_driver.c#L1144

@bms48 what's the breakage?

#libvirt #FreeBSD

@bms48 what's the breakage?

#libvirt #FreeBSD

One Open-source Project Daily

Yosild is a single shell script that builds a full, minimal Linux distribution based on BusyBox.

https://github.com/jaromaz/yosild

#1ospd #opensource #busybox #cli #debian #distro #hyperv #kernelcompilation #kvm #libvirt #linux #linuxdistribution #operatingsystem #shell #terminal #ubuntu #virtualbox

One Open-source Project Daily

Yosild is a single shell script that builds a full, minimal Linux distribution based on BusyBox.

https://github.com/jaromaz/yosild

#1ospd #opensource #busybox #cli #debian #distro #hyperv #kernelcompilation #kvm #libvirt #linux #linuxdistribution #operatingsystem #shell #terminal #ubuntu #virtualbox

Just discovered libvirt ssh proxy with is working with systemd-ssh-generator to transfer ssh through vsock. So you can simply
$ virt-install --vsock cid.auto=yes --cloud-init user-data...

And then ssh with
$ ssh qemu:system/myvm

no need to predict or discover the IP address (or even to have a network interface)

#linux #libvirt

In my (short) dad time this morning, I've tried to install mgmt [1] to run a distributed hello world on my main machine running on Ubuntu LTS. The built-in binaries depend on augeas which was easy to fix. But also libvirt which is surprisingly old on Ubuntu compared to Debian (latest). I tried to build it myself but I couldn't install nex (the lexer). I then built the binary using Docker thanks to the quick start guide.

I first started to run mgmt in standalone mode. It's nice to see etcd embedded in the binary (at least for testing). Then I tried to deploy multi mgmt nodes with a standalone etcd using docker-compose. I've lost a lot of time trying to override the command because I didn't remember the expected syntax.

I was trying to make etcd listen to all interfaces so mgmt could connect when my daughter showed up.

[1] https://github.com/purpleidea/mgmt (@purpleidea)

#mgmt #homelab #selfhosting #etcd #docker #libvirt #ubuntu #debian

In my (short) dad time this morning, I've tried to install mgmt [1] to run a distributed hello world on my main machine running on Ubuntu LTS. The built-in binaries depend on augeas which was easy to fix. But also libvirt which is surprisingly old on Ubuntu compared to Debian (latest). I tried to build it myself but I couldn't install nex (the lexer). I then built the binary using Docker thanks to the quick start guide.

I first started to run mgmt in standalone mode. It's nice to see etcd embedded in the binary (at least for testing). Then I tried to deploy multi mgmt nodes with a standalone etcd using docker-compose. I've lost a lot of time trying to override the command because I didn't remember the expected syntax.

I was trying to make etcd listen to all interfaces so mgmt could connect when my daughter showed up.

[1] https://github.com/purpleidea/mgmt (@purpleidea)

#mgmt #homelab #selfhosting #etcd #docker #libvirt #ubuntu #debian

Updated: Resolve Libvirt Error Unable to Find EFI Firmware

- Fix redirect links

https://www.adamsdesk.com/posts/resolve-libvirt-error-unable-find-efi-firmware/

#blog #VirtualMachine #libvirt #QEMU #tech #technology

Updated: Resolve Libvirt Error Unable to Find EFI Firmware

- Fix redirect links

https://www.adamsdesk.com/posts/resolve-libvirt-error-unable-find-efi-firmware/

#blog #VirtualMachine #libvirt #QEMU #tech #technology

I just caught Reddit just spreading the wrong-ass information. People are saying virt-manager is faster than GNOME's Boxes app. They are literally based on the same backend, what the fuck.

#Linux #Libvirt

I just caught Reddit just spreading the wrong-ass information. People are saying virt-manager is faster than GNOME's Boxes app. They are literally based on the same backend, what the fuck.

#Linux #Libvirt

I just posted to my blog -- "libvirt network forwarding inconsistencies": In an INCUS container on a KVM guest, ping commands are successful when executed on the container, but not when the are executed from the host on the other end -- Read more here: https://www.dfoley.ie/blog/libvirt-network-forwarding-inconsistencies -- #linux #libvirt #incus #POSSE

I just posted to my blog -- "libvirt network forwarding inconsistencies": In an INCUS container on a KVM guest, ping commands are successful when executed on the container, but not when the are executed from the host on the other end -- Read more here: https://www.dfoley.ie/blog/libvirt-network-forwarding-inconsistencies -- #linux #libvirt #incus #POSSE

To those who still have a dedicated #Microsoft #Windows machine solely for configuring niche peripherals, no more need for moral anxiety, they get detected using a Windoze virtual machine with QEMU/KVM (requires at least a system with partial TPM 2.0 support): https://www.arscyni.cc/file/software.html#windoze:~:text=Microslop%20Windoze%20virtual%20machine

It takes slightly more attention to set it up than Oracle VirtualBox, but it runs ten times faster.

#Microslop #Windoze #EVGA #UnleashRGB #QEMU #KVM #libvirt

To those who still have a dedicated #Microsoft #Windows machine solely for configuring niche peripherals, no more need for moral anxiety, they get detected using a Windoze virtual machine with QEMU/KVM (requires at least a system with partial TPM 2.0 support): https://www.arscyni.cc/file/software.html#windoze:~:text=Microslop%20Windoze%20virtual%20machine

It takes slightly more attention to set it up than Oracle VirtualBox, but it runs ten times faster.

#Microslop #Windoze #EVGA #UnleashRGB #QEMU #KVM #libvirt

RE: https://furry.engineer/@Flaky/116059368890193901

lmao, Chris Titus Tech had an update to Looking Glass and now he can't access his Windows VM.

This is why vGPUs are important!

#VFIO #libvirt #KVM

Finally got my VM hosts updated to the latest AlpineLinux release. Browsing Ceph RBD pools is still broken in `libvirt`… no idea why but one RBD pool works fine, the other refuses to start. (They are configured identically apart from the name of the pool being connected to.)

It tells me "An error occurred, but the cause is unknown". No logs. I asked on `libvirt-users` mailing list: no answer. It's a mystery.

But… if I hand-configure the XML (usually by taking the `dumpxml` output from another VM and hand-editing), I can link to RBD volumes just fine and it just works, so whatever.

The other gotcha was VM types becoming unavailable. A lot of my VMs were `pc-i440fx-3.1` or `pc-q35-3.1` machines. Moving from `pc-q35-3.1` to `pc-q35-10.1` was painless, but going from i440FX-based VMs to Q35 took a bit of hand-massaging the XML: remove PCI IDE/SATA/USB controllers then change the `pci-root` node to `pcie-root`.

Everything is now running `pc-q35-10.1`; so that should kick that can far down the road.

#HomeServer #AlpineLinux #Ceph #libvirt

Finally got my VM hosts updated to the latest AlpineLinux release. Browsing Ceph RBD pools is still broken in `libvirt`… no idea why but one RBD pool works fine, the other refuses to start. (They are configured identically apart from the name of the pool being connected to.)

It tells me "An error occurred, but the cause is unknown". No logs. I asked on `libvirt-users` mailing list: no answer. It's a mystery.

But… if I hand-configure the XML (usually by taking the `dumpxml` output from another VM and hand-editing), I can link to RBD volumes just fine and it just works, so whatever.

The other gotcha was VM types becoming unavailable. A lot of my VMs were `pc-i440fx-3.1` or `pc-q35-3.1` machines. Moving from `pc-q35-3.1` to `pc-q35-10.1` was painless, but going from i440FX-based VMs to Q35 took a bit of hand-massaging the XML: remove PCI IDE/SATA/USB controllers then change the `pci-root` node to `pcie-root`.

Everything is now running `pc-q35-10.1`; so that should kick that can far down the road.

#HomeServer #AlpineLinux #Ceph #libvirt

Man the terraform libvirt provider has matured so much. It still seems like a struggle to get bridge networking setup as expected. Something tells that’s strange is even attaching a dom interface to a nat network it won’t pickup an IP.

Creating a domain with `virt-install` seems to work as expected. The domain xml that appears to be relevant is all the same.

Time to dig back into this today.

https://github.com/dmacvicar/terraform-provider-libvirt if you’re curious

#terraform #libvirt

Some udev rules later and the Palm is syncing again in #debian and #libvirt

Alright, using #talosLinux with #terraform and #libvirt to build out all the #kubernetes infra to run the #selfHosted bits.

So I have 2 5950x with 64gb of ram and 4tb of storage. Then a 3950x with 1tb and 32g, and finally some small older boxes.

My desktop w the 5950 used to be a gaming machine but the steam deck has 100% replaced that functionality.

Eventually I may just run talos natively on either of the larger boxes but libvirt is a much nicer api.

I want to share management of existing #LXC #containers (that I handle with the command line tools) with other people who prefer to use GUIs… (oh, preferences…)

I'd rather not have to "convert" or "migrate" of whatever, but just have the GUI tools manage existing containers without screwing them up…

As I understand, at least #Proxmox will want to create them by itself so it's a no-go.

Anyone experiences with #libvirt / #virtManager can tell me if it's the same or not?

(more Linux news in original post)

Synex Server: A New Debian Based Linux Distro With Native ZFS Installation Support:
https://www.phoronix.com/news/Synex-Debian-With-ZFS

Fedora Games Lab Approved To Switch To KDE Plasma, Become A Better Linux Gaming Showcase:
https://www.phoronix.com/news/Fedora-Games-Lab-Overhaul-2026

Goverlay for managing tools like MangoHud gets a major new release and it's finally on Flathub:
https://www.gamingonlinux.com/2026/01/goverlay-for-managing-tools-like-mangohud-gets-a-major-new-release-and-its-finally-on-flathub/

Proton Experimental brings updates for MonoGame, Rockstar Launcher and more:
https://www.gamingonlinux.com/2026/01/proton-experimental-brings-updates-for-monogame-rockstar-launcher-and-more/

Upcoming exFAT Linux Driver Patch Can Boost Sequential Read Performance By ~10%:
https://www.phoronix.com/news/exFAT-Faster-Seq-Reads-10p

Patches Positioned Ahead Of Linux 7.0 Cycle For Easy Custom Boot Logo In Place Of Tux:
https://www.phoronix.com/news/Linux-7.0-Custom-Boot-Logo

libvirt 12.0 Released - Bhyve ARM64 Support & Other Improvements For The BSD Hypervisor:
https://www.phoronix.com/news/libvirt-12.0

GRUB 2.14 Bootloader Released With EROFS Support, Shim Loader Protocol:
https://www.phoronix.com/news/GRUB-2.14-Released

D7VK version 1.2 brings more Direct3D 6 improvements and a little Direct3D 5 too:
https://www.gamingonlinux.com/2026/01/d7vk-version-1-2-brings-more-direct3d-6-improvements-and-a-little-direct3d-5-too/

Wine 11.0 Brings Ntsync Support, Complete WoW64 + Other Changes:
https://www.omgubuntu.co.uk/2026/01/wine-11-0-released

Hangover 11.0 Released: Wine + FEX/Box64 Pairing For Windows x86 Apps On ARM64 Linux:
https://www.phoronix.com/news/Hangover-11.0-Released

Linux 6.19-rc5 Brings Fix For Newer NVIDIA GPUs, Logitech HID++ For Anywhere 3S & Fixes:
https://www.phoronix.com/news/Linux-6.19-rc5-Released

First .NET 10 Servicing Update Now Available in Ubuntu 24.04 LTS:
https://www.omgubuntu.co.uk/2026/01/dotnet-10-0-1-update-ubuntu-24-04-lts

Bcachefs Ships Latest User-Space Utilities With bcachefs-tools 1.35:
https://www.phoronix.com/news/bcachefs-tools-1.35

Even more AMD ray tracing performance improvements heading to Mesa on Linux:
https://www.gamingonlinux.com/2026/01/even-more-amd-ray-tracing-performance-improvements-heading-to-mesa-on-linux/

Auto-CPUFreq 3.0 Released To Help You Extend Laptop Battery Life On Linux:
https://www.phoronix.com/news/Auto-CPUFreq-3.0

LLMinus Working On AI/LLM-Powered Merge Conflict Resolution For The Linux Kernel:
https://www.phoronix.com/news/LLMinus-RFC-v2

(FOSS news in comments)

#WeeklyNews #News #Linux #LinuxNews #Synex #FedoraGamesLab #Goverlay #Proton #exFAT #LinuxKernel #Libvirt #GRUB #D7VK #Wine #Hangover #Bcachefs #Mesa #AMD #AutoCPUFreq #Auto_CPUFREQ #FosseryTech