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

TIL how to configure #libvirt and #qemu #kvm to disable nested virtualization on a guest, while keeping it enabled on the host:

<cpu ....>
<feature policy='disable' name='svm'/>
<feature policy='disable' name='vmx'/>
</cpu>

(SVM is for AMD processors and VMX is for Intel processors)

(I know it works because /proc/cpuinfo doesn't have the svm or vmx flags, and Windows greys out the Hyper-V hypervisor feature so you can't install it.)

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?

Virtualization on linux. Setup KVM, QUEMU and libvirt on your server at home.

#libvirt #virtualization #v12n #linux
https://writeaheadlog.net/libvirt/