sueden.social

woodsb02<a href="https://layer8.space/@platymew" class="u-url mention" rel="nofollow noopener" target="_blank">@platymew</a> I really like the idea of zvols, but I hear they significantly underperform so I am instead using a dedicated zroot/vm/haos dataset with a raw disk0.img file in it. I define it in <a href="https://fosstodon.org/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> with:<disk type='file' device='disk'> <driver name='qemu' type='raw'/> <source file='/vm/haos/disk0.img'/> <target dev='vda' bus='virtio'/> <address type='pci' domain='0x0000' bus='0x04' slot='0x00' function='0x0'/> </disk>

Multi Purr Puss :verified:When your VMs in the "default NAT" network don't get an IP, it's probably the <a href="https://layer8.space/tags/firewall" class="mention hashtag" rel="nofollow noopener" target="_blank">#firewall</a> on the <a href="https://layer8.space/tags/hypervisor" class="mention hashtag" rel="nofollow noopener" target="_blank">#hypervisor</a>.edit: <a href="https://layer8.space/tags/CachyOS" class="mention hashtag" rel="nofollow noopener" target="_blank">#CachyOS</a> (<a href="https://layer8.space/tags/Arch" class="mention hashtag" rel="nofollow noopener" target="_blank">#Arch</a> btw) doesn't seem to allow forwarding by default - copilot helped getting it fixed, without me learning the wrong thing for hours. 😉<a href="https://layer8.space/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://layer8.space/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://layer8.space/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a>

Marius (windsheep) :donor:I am moving to <a href="https://infosec.exchange/tags/Proxmox" class="mention hashtag" rel="nofollow noopener" target="_blank">#Proxmox</a> . I liked my <a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> setup, but I am too busy. I need a faster solution. All hyper-consolidation features I need are in Proxmox:1. Memory ballooning 2. Kernel Same Page Merging 3. LXC support 4. Windows guest support 5. OpenBSD guest support 6. VirtioFS with Direct IO 7. It works with <a href="https://infosec.exchange/tags/Debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> 8. Masquerade NAT to guests is possible 9. Nested virtualization for Windows works now (Hyper-V on the guest). I never managed to get that stable with libvirt 10. Integrated performance monitoring and logging 11. qcow2 support with growing imagesI would even pay for it, but you can only license it per socket.

Marius (windsheep) :donor:Total allocated VM memory: 107GB across 12 VMs Actual memory used: 50GB Memory ballooning savings: ~57GB (53% efficiency) KSM deduplication: ~1.6GB additional savings Combined optimization: 58.6GB total memory savedMemory ballooning in <a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> is the bee's knees.

Daniel S. ReichenbachDoes anyone else feel like <a href="https://mastodon.world/tags/HashiCorp" class="mention hashtag" rel="nofollow noopener" target="_blank">#HashiCorp</a> has let Vagrant silently expire?Seems like in any ops tooling with support for it, it's outdated, unusable or just a wrapper for <a href="https://mastodon.world/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> anyway.

StefanIch habe jetzt die ersten "Anfragen" 🙂 Der PC hat eine älteren Prozessor und wird nicht für ein Windows 10 auf Windows 11 unterstützt. Meine Idee: <a href="https://devlug.de/social?t=debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> als Grundsystem und <a href="https://devlug.de/social?t=windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> in einer <a href="https://devlug.de/social?t=vm" class="mention hashtag" rel="nofollow noopener" target="_blank">#VM</a>. Alle coolen Sachen auf Debian machen und Windows für den Rest. Meine Frage: Kann man Windows 11 auf deinem <a href="https://devlug.de/social?t=debian" class="mention hashtag" rel="nofollow noopener" target="_blank">#Debian</a> <a href="https://devlug.de/social?t=libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://devlug.de/social?t=kvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#kvm</a> laufen lassen? Ich müsste dann wohl ein Windows 11 Home kaufen. Ein upgrade wird dann ja nicht funktionieren. Problem: Die Kiste hat nicht so viel RAM. Aber wenn man erst mal ein paar Tage Debian verwendet hat, wird man vielleicht die VM nicht mehr starten 😉 <a href="https://devlug.de/social?t=windows" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows</a> <a href="https://devlug.de/social?t=windows10" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows10</a> <a href="https://devlug.de/social?t=windows11" class="mention hashtag" rel="nofollow noopener" target="_blank">#Windows11</a>

frdbr 🎥🌳Two interesting projects I'm keeping an eye on:✳️ Karton - A Virtual Machine manager being worked on for <a href="https://mastodon.social/tags/gsoc" class="mention hashtag" rel="nofollow noopener" target="_blank">#gsoc</a> by <a href="https://mastodon.social/@kenoi" class="u-url mention" rel="nofollow noopener" target="_blank">@kenoi</a> ✳️ Kretro - A new <a href="https://mastodon.social/tags/libretro" class="mention hashtag" rel="nofollow noopener" target="_blank">#libretro</a> frontend by <a href="https://social.sineware.ca/@seshpenguin" class="u-url mention" rel="nofollow noopener" target="_blank">@seshpenguin</a> <a href="https://mastodon.social/tags/emulation" class="mention hashtag" rel="nofollow noopener" target="_blank">#emulation</a> <a href="https://mastodon.social/tags/retroarch" class="mention hashtag" rel="nofollow noopener" target="_blank">#retroarch</a> <a href="https://mastodon.social/tags/retrogaming" class="mention hashtag" rel="nofollow noopener" target="_blank">#retrogaming</a> <a href="https://mastodon.social/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://mastodon.social/tags/kde" class="mention hashtag" rel="nofollow noopener" target="_blank">#kde</a> <a href="https://lemmy.kde.social/c/kde" class="u-url mention" rel="nofollow noopener" target="_blank">@kde</a>

stafwagUsing OpenTofu/Terraform to create a disposable Tails virtual machine<a href="https://stafwag.github.io/blog/blog/2025/06/22/using-opentofu-to-create-tails-environment/" rel="nofollow noopener" translate="no" target="_blank">https://stafwag.github.io/blog/blog/2025/06/22/using-opentofu-to-create-tails-environment/</a><a href="https://mastodon.social/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://mastodon.social/tags/linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#linux</a> <a href="https://mastodon.social/tags/opentufo" class="mention hashtag" rel="nofollow noopener" target="_blank">#opentufo</a> <a href="https://mastodon.social/tags/tails" class="mention hashtag" rel="nofollow noopener" target="_blank">#tails</a> <a href="https://mastodon.social/tags/terraform" class="mention hashtag" rel="nofollow noopener" target="_blank">#terraform</a> <a href="https://mastodon.social/tags/tor" class="mention hashtag" rel="nofollow noopener" target="_blank">#tor</a> <a href="https://mastodon.social/tags/stafwag" class="mention hashtag" rel="nofollow noopener" target="_blank">#stafwag</a> <a href="https://mastodon.social/@stafwag" class="u-url mention" rel="nofollow noopener" target="_blank">@stafwag</a>

Droppie [infosec] 🐨:archlinux: :kde: :firefox_nightly: :thunderbird: :vegan:<a href="https://infosec.exchange/@deadbeefdotmonster" class="u-url mention" rel="nofollow noopener" target="_blank">@deadbeefdotmonster</a> Last time [not recently, maybe a year'ish ago] that i tried enabling 3D Accel [is that what you mean by "hardware accel"?] it seemed to work well, but it broke the ability for me to Suspend [aka Save] my VMs each time, ie, i had to fully SD them, then cold SU them next time. That was a bigger PITA for me than the hitherto lack of accel, so i disabled it again ever since. Ofc <a href="https://infosec.space/tags/QEMU" class="mention hashtag" rel="nofollow noopener" target="_blank">#QEMU</a> / <a href="https://infosec.space/tags/KVM" class="mention hashtag" rel="nofollow noopener" target="_blank">#KVM</a> / <a href="https://infosec.space/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> / <a href="https://infosec.space/tags/VirtManager" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtManager</a> have had many updates since then. Maybe it's better now?

postmodernWhat solutions do Wayland users use for passing keybindings (ex: Alt-Tab) through to a VM being viewed with <code>virt-viewer</code> or <code>remote-viewer</code> in a Wayland WM? X11 had some kind of special hint to tell the WM to pass all keybindings through to the VM's viewer window. Do you just temporarily disable keybindings while viewing a VM? Is it possible to run <code>virt-viewer</code> or <code>remote-viewer</code> in a separate instance of Wayland/wlroots that only displays that windows and passes all keyboard input to it (e.g. the Wayland equivalent of <code>xinit virt-viewer ... -- :1</code>)?<a href="https://infosec.exchange/tags/virtviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtviewer</a> <a href="https://infosec.exchange/tags/remoteviewer" class="mention hashtag" rel="nofollow noopener" target="_blank">#remoteviewer</a> <a href="https://infosec.exchange/tags/virtmanager" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtmanager</a> <a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://infosec.exchange/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> <a href="https://infosec.exchange/tags/wayland" class="mention hashtag" rel="nofollow noopener" target="_blank">#wayland</a> <a href="https://infosec.exchange/tags/labwc" class="mention hashtag" rel="nofollow noopener" target="_blank">#labwc</a>

postmodernI wonder if it's possible to do "video passthru" (not to be confused with GPU passthru) with libvirt/qemu? Is it possible to send all video data from qemu to an unallocated TTY or possibly an empty X/Wayland session and switch to it using Ctrl+Alt+F8+?<a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://infosec.exchange/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> <a href="https://infosec.exchange/tags/kvm" class="mention hashtag" rel="nofollow noopener" target="_blank">#kvm</a>

postmodernDecided to switch back to QXL+Spice, but with Spice Listen Type = None, and with CPU pinning, and directly sending audio to pipewire. Seems to have fixed the slow 2d graphics, while maintaining smooth video playback, and eliminated any random intermittent freezes that would crash the viewer.<a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://infosec.exchange/tags/virtio" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtio</a> <a href="https://infosec.exchange/tags/qxl" class="mention hashtag" rel="nofollow noopener" target="_blank">#qxl</a>

postmodernI enabled OpenGL acceleration under VirtIO and video playback is smooth, but now other 2d things have suddenly become very slow, such as switching between windows and closing large windows. Is this a known problem? Or do I need a faster GPU or CPU?<a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://infosec.exchange/tags/virtio" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtio</a> <a href="https://infosec.exchange/tags/virgl" class="mention hashtag" rel="nofollow noopener" target="_blank">#virgl</a> <a href="https://infosec.exchange/tags/virglrenderer" class="mention hashtag" rel="nofollow noopener" target="_blank">#virglrenderer</a>

postmodernAlso wtf, why are Virtio Graphics so much slower than QXL Graphics? I was under the impression that Virtio was supposed to have lower overhead.<a href="https://infosec.exchange/tags/qemu" class="mention hashtag" rel="nofollow noopener" target="_blank">#qemu</a> <a href="https://infosec.exchange/tags/virtio" class="mention hashtag" rel="nofollow noopener" target="_blank">#virtio</a> <a href="https://infosec.exchange/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://infosec.exchange/tags/qxl" class="mention hashtag" rel="nofollow noopener" target="_blank">#qxl</a>

Scott Williams 🐧These 200G <a href="https://mastodon.online/tags/Broadcom" class="mention hashtag" rel="nofollow noopener" target="_blank">#Broadcom</a> NICs have harmed my sanity.<a href="https://mastodon.online/tags/Linux" class="mention hashtag" rel="nofollow noopener" target="_blank">#Linux</a> <a href="https://mastodon.online/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a>

Joachim Weber [friendica] 🦖 🦔 🐲Neben Fehlerkorrekturen stecken in der aktualisierten Libvirt nur eine Handvoll Neuerungen, die sich aber als durchweg nützlich entpuppen. So unterstützt die Version 11.4 die Konfiguration von NVRAM bei bhyve, während die Hilfswerkzeuge $PATH nutzen.<a href="https://anonsys.net/search?tag=Libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#Libvirt</a> <a href="https://anonsys.net/search?tag=Virtualisierung" class="mention hashtag" rel="nofollow noopener" target="_blank">#Virtualisierung</a> <a href="https://www.linux-community.de/nachrichten/libvirt-11-4-0-unterstuetzt-power11-prozessoren-via-qemu/" rel="nofollow noopener" target="_blank">Libvirt 11.4.0 unterstützt POWER11-Prozessoren via Qemu - LinuxCommunity</a>

Johannes KastlHey <a href="https://fosstodon.org/@fedora" class="u-url mention" rel="nofollow noopener" target="_blank">@fedora</a>,are there any plans to release the <a href="https://digitalcourage.social/tags/Vagrant" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vagrant</a> box for <a href="https://digitalcourage.social/tags/Fedora42" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora42</a> to app.vagrantup.com?There is already a box available on the Fedora server, but without metadata (which makes updates hard...).<a href="https://download.fedoraproject.org/pub/fedora/linux/releases/42/Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-libvirt-42-1.1.x86_64.vagrant.libvirt.box" rel="nofollow noopener" translate="no" target="_blank">https://download.fedoraproject.org/pub/fedora/linux/releases/42/Cloud/x86_64/images/Fedora-Cloud-Base-Vagrant-libvirt-42-1.1.x86_64.vagrant.libvirt.box</a>(I know Vagrant is no longer used widely and Hashicorp messed up with the whole licensing trouble, but having an existing box available easiy would really be appreciated nontheless...)Have a nice day, everyone!<a href="https://digitalcourage.social/tags/Vagrant" class="mention hashtag" rel="nofollow noopener" target="_blank">#Vagrant</a> <a href="https://digitalcourage.social/tags/Fedora" class="mention hashtag" rel="nofollow noopener" target="_blank">#Fedora</a> <a href="https://digitalcourage.social/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a>

AdamResolve Libvirt Error Unable to Find EFI FirmwareA step by step guide on how to fix the Libvirt Error Unable to Find EFI Firmware by updating the paths in the virtual machine’s configuration.<a href="https://www.adamsdesk.com/posts/resolve-libvirt-error-unable-find-efi-firmware/" rel="nofollow noopener" translate="no" target="_blank">https://www.adamsdesk.com/posts/resolve-libvirt-error-unable-find-efi-firmware/</a><a href="https://fosstodon.org/tags/blog" class="mention hashtag" rel="nofollow noopener" target="_blank">#blog</a> <a href="https://fosstodon.org/tags/VirtualMachine" class="mention hashtag" rel="nofollow noopener" target="_blank">#VirtualMachine</a> <a href="https://fosstodon.org/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://fosstodon.org/tags/QEMU" class="mention hashtag" rel="nofollow noopener" target="_blank">#QEMU</a> <a href="https://fosstodon.org/tags/tech" class="mention hashtag" rel="nofollow noopener" target="_blank">#tech</a> <a href="https://fosstodon.org/tags/technology" class="mention hashtag" rel="nofollow noopener" target="_blank">#technology</a>

Johannes KastlIn case you want to get your hands dirty with Traefik, Kubernetes and the new GatewayAPI, I got you covered.Here is another vagrant-libvirt setup that has <a href="https://digitalcourage.social/tags/k3s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k3s</a>, <a href="https://digitalcourage.social/tags/Traefik" class="mention hashtag" rel="nofollow noopener" target="_blank">#Traefik</a> and a <a href="https://digitalcourage.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> deployment. Instead of using a <a href="https://digitalcourage.social/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a> <a href="https://digitalcourage.social/tags/ingress" class="mention hashtag" rel="nofollow noopener" target="_blank">#ingress</a> or a Traefik ingressroute, this setup uses the <a href="https://digitalcourage.social/tags/GatewayAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#GatewayAPI</a> resources like Gateways and HTTPRoutes.<a href="https://codeberg.org/johanneskastl/traefik_gateway-api_on_k3s_vagrant_libvirt_ansible" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/johanneskastl/traefik_gateway-api_on_k3s_vagrant_libvirt_ansible</a> <a href="https://github.com/johanneskastl/traefik_gateway-api_on_k3s_vagrant_libvirt_ansible" rel="nofollow noopener" translate="no" target="_blank">https://github.com/johanneskastl/traefik_gateway-api_on_k3s_vagrant_libvirt_ansible</a>As usual, <a href="https://digitalcourage.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> does the heavy lifting and deploys everything in the cluster.Have a lot of fun.<a href="https://digitalcourage.social/tags/k8s" class="mention hashtag" rel="nofollow noopener" target="_blank">#k8s</a> <a href="https://digitalcourage.social/tags/Kubernetes" class="mention hashtag" rel="nofollow noopener" target="_blank">#Kubernetes</a> <a href="https://digitalcourage.social/tags/Traefik" class="mention hashtag" rel="nofollow noopener" target="_blank">#Traefik</a> <a href="https://digitalcourage.social/tags/Ingress" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ingress</a> <a href="https://digitalcourage.social/tags/GatewayAPI" class="mention hashtag" rel="nofollow noopener" target="_blank">#GatewayAPI</a> <a href="https://digitalcourage.social/tags/DevOps" class="mention hashtag" rel="nofollow noopener" target="_blank">#DevOps</a> <a href="https://digitalcourage.social/tags/vagrant" class="mention hashtag" rel="nofollow noopener" target="_blank">#vagrant</a> <a href="https://digitalcourage.social/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://digitalcourage.social/tags/Nginx" class="mention hashtag" rel="nofollow noopener" target="_blank">#Nginx</a> <a href="https://digitalcourage.social/tags/HellYeah" class="mention hashtag" rel="nofollow noopener" target="_blank">#HellYeah</a>

Johannes Kastl<a href="https://indieweb.social/@dragotin" class="u-url mention" rel="nofollow noopener" target="_blank">@dragotin</a> <a href="https://mastodon.social/@darix" class="u-url mention" rel="nofollow noopener" target="_blank">@darix</a> <a href="https://social.opencloud.eu/@OpenCloud" class="u-url mention" rel="nofollow noopener" target="_blank">@OpenCloud</a> <a href="https://fosstodon.org/@opensuse" class="u-url mention" rel="nofollow noopener" target="_blank">@opensuse</a> Here is the vagrant-libvirt setup I currently use to test the new package: <a href="https://codeberg.org/johanneskastl/opencloud_opensuse_vagrant_libvirt_ansible" rel="nofollow noopener" translate="no" target="_blank">https://codeberg.org/johanneskastl/opencloud_opensuse_vagrant_libvirt_ansible</a> <a href="https://github.com/johanneskastl/opencloud_opensuse_vagrant_libvirt_ansible" rel="nofollow noopener" translate="no" target="_blank">https://github.com/johanneskastl/opencloud_opensuse_vagrant_libvirt_ansible</a>Most boilerplate and surrounding things are fine, the executable runs, but currently the setup is broken due to missing assets / assets not being created.As stated in the README, work in progress under heavy development... :-)<a href="https://digitalcourage.social/tags/openSUSE" class="mention hashtag" rel="nofollow noopener" target="_blank">#openSUSE</a> <a href="https://digitalcourage.social/tags/OpenCloud" class="mention hashtag" rel="nofollow noopener" target="_blank">#OpenCloud</a> <a href="https://digitalcourage.social/tags/Ansible" class="mention hashtag" rel="nofollow noopener" target="_blank">#Ansible</a> <a href="https://digitalcourage.social/tags/vagrant" class="mention hashtag" rel="nofollow noopener" target="_blank">#vagrant</a> <a href="https://digitalcourage.social/tags/libvirt" class="mention hashtag" rel="nofollow noopener" target="_blank">#libvirt</a> <a href="https://digitalcourage.social/tags/hellyeah" class="mention hashtag" rel="nofollow noopener" target="_blank">#hellyeah</a> <a href="https://digitalcourage.social/tags/packagerslife" class="mention hashtag" rel="nofollow noopener" target="_blank">#packagerslife</a>

Frühere Suchanfragen

Suchoptionen

Verwaltet von:

Serverstatistik:

#libvirt