home.social

#qemu — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #qemu, aggregated by home.social.

  1. CVE-2026-12080 - Privilege Escalation in QEMU Guest Agent. TOCTOU & symlink abuse in guest-ssh-add-authorized-keys. CVSS 7.3. Unpatched. Restrict qga access immediately. #CVE #infosec #QEMU

    valtersit.com/cve/CVE-2026-120

  2. CVE-2026-12080 - Privilege Escalation in QEMU Guest Agent. TOCTOU & symlink abuse in guest-ssh-add-authorized-keys. CVSS 7.3. Unpatched. Restrict qga access immediately. #CVE #infosec #QEMU

    valtersit.com/cve/CVE-2026-120

  3. Most people are running containers on VM. But for some cases, I tried the opposite way on Fedora CoreOS: running VMs on qemu container.

    #container #qemu #fcos #linux

  4. Most people are running containers on VM. But for some cases, I tried the opposite way on Fedora CoreOS: running VMs on qemu container.

    #container #qemu #fcos #linux

  5. Most people are running containers on VM. But for some cases, I tried the opposite way on Fedora CoreOS: running VMs on qemu container.

    #container #qemu #fcos #linux

  6. Running libvirt's Virtual Machine Manager (virt-manager) on Linux and seeing a blurry VM console?

    With a simple change in the settings the blurry text disappears and is crystal clear again.

    A quick fix that might save you some frustration. #Linux #KVM #QEMU #VirtManager #OpenSource

    geekersdigest.com/how-to-fix-b

  7. Running libvirt's Virtual Machine Manager (virt-manager) on Linux and seeing a blurry VM console?

    With a simple change in the settings the blurry text disappears and is crystal clear again.

    A quick fix that might save you some frustration.

    geekersdigest.com/how-to-fix-b

  8. Running libvirt's Virtual Machine Manager (virt-manager) on Linux and seeing a blurry VM console?

    With a simple change in the settings the blurry text disappears and is crystal clear again.

    A quick fix that might save you some frustration. #Linux #KVM #QEMU #VirtManager #OpenSource

    geekersdigest.com/how-to-fix-b

  9. Running libvirt's Virtual Machine Manager (virt-manager) on Linux and seeing a blurry VM console?

    With a simple change in the settings the blurry text disappears and is crystal clear again.

    A quick fix that might save you some frustration. #Linux #KVM #QEMU #VirtManager #OpenSource

    geekersdigest.com/how-to-fix-b

  10. Running libvirt's Virtual Machine Manager (virt-manager) on Linux and seeing a blurry VM console?

    With a simple change in the settings the blurry text disappears and is crystal clear again.

    A quick fix that might save you some frustration. #Linux #KVM #QEMU #VirtManager #OpenSource

    geekersdigest.com/how-to-fix-b

  11. 🚀 Oh, joy! Someone decided to #rewrite #Linux 0.11 in #Rust, because clearly, what it needed was more hipster cred and extra bugs! 🙃 And surprise, surprise, it boots in QEMU—exactly where all the cutting-edge tech goes to die. 💀
    github.com/Poseidon-fan/linux- #QEMU #TechNews #HipsterDev #HackerNews #ngated

  12. 🚀 Oh, joy! Someone decided to #rewrite #Linux 0.11 in #Rust, because clearly, what it needed was more hipster cred and extra bugs! 🙃 And surprise, surprise, it boots in QEMU—exactly where all the cutting-edge tech goes to die. 💀
    github.com/Poseidon-fan/linux- #QEMU #TechNews #HipsterDev #HackerNews #ngated

  13. 🚀 Oh, joy! Someone decided to #rewrite #Linux 0.11 in #Rust, because clearly, what it needed was more hipster cred and extra bugs! 🙃 And surprise, surprise, it boots in QEMU—exactly where all the cutting-edge tech goes to die. 💀
    github.com/Poseidon-fan/linux- #QEMU #TechNews #HipsterDev #HackerNews #ngated

  14. 🚀 Oh, joy! Someone decided to #rewrite #Linux 0.11 in #Rust, because clearly, what it needed was more hipster cred and extra bugs! 🙃 And surprise, surprise, it boots in QEMU—exactly where all the cutting-edge tech goes to die. 💀
    github.com/Poseidon-fan/linux- #QEMU #TechNews #HipsterDev #HackerNews #ngated

  15. 🚀 Oh, joy! Someone decided to #rewrite #Linux 0.11 in #Rust, because clearly, what it needed was more hipster cred and extra bugs! 🙃 And surprise, surprise, it boots in QEMU—exactly where all the cutting-edge tech goes to die. 💀
    github.com/Poseidon-fan/linux- #QEMU #TechNews #HipsterDev #HackerNews #ngated

  16. How to compile *and test* software for a newer CPU than my host has.

    Running `qemu` with `-cpu max` gives me `segmentation fault`.

    Is qemu even able to emulate a newer CPU than host?
    #qemu #kvm

  17. How to compile *and test* software for a newer CPU than my host has.

    Running `qemu` with `-cpu max` gives me `segmentation fault`.

    Is qemu even able to emulate a newer CPU than host?
    #qemu #kvm

  18. How to compile *and test* software for a newer CPU than my host has.

    Running `qemu` with `-cpu max` gives me `segmentation fault`.

    Is qemu even able to emulate a newer CPU than host?
    #qemu #kvm

  19. How to compile *and test* software for a newer CPU than my host has.

    Running `qemu` with `-cpu max` gives me `segmentation fault`.

    Is qemu even able to emulate a newer CPU than host?
    #qemu #kvm

  20. How to compile *and test* software for a newer CPU than my host has.

    Running `qemu` with `-cpu max` gives me `segmentation fault`.

    Is qemu even able to emulate a newer CPU than host?
    #qemu #kvm

  21. so i tried to make a nested proxmox vgpu thingy. but it doesnt work cause when i enabled viommu on the vm the nvidia driver fails(RmInitAdapter failed) but when i disable viommu mdev doesnt work cause it needs /sys/kernel/iommu_groups/ which only exsists with iommu. i fucking hate this bullshit.

    #proxmox #vgpu #viommu #iommu #gpu #nvidia #server #homelab #selfhosting #vm #qemu #pciepassthrough #mdev

  22. so i tried to make a nested proxmox vgpu thingy. but it doesnt work cause when i enabled viommu on the vm the nvidia driver fails(RmInitAdapter failed) but when i disable viommu mdev doesnt work cause it needs /sys/kernel/iommu_groups/ which only exsists with iommu. i fucking hate this bullshit.

    #proxmox #vgpu #viommu #iommu #gpu #nvidia #server #homelab #selfhosting #vm #qemu #pciepassthrough #mdev

  23. New blog post!

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

    dwarmstrong.org/void-libvirt/

  24. New blog post!

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

    dwarmstrong.org/void-libvirt/

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

  25. New blog post!

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

    dwarmstrong.org/void-libvirt/

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

  26. New blog post!

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

    dwarmstrong.org/void-libvirt/

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

  27. New blog post!

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

    dwarmstrong.org/void-libvirt/

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

  28. Ich Held hab' mal wieder was zerbastelt:
    Ich hab' eine (Qemu) VM auf einem Proxmox schlafen gelegt… also suspended… vom GUI der Maschine aus (via noVNC), nicht von der Weboberfläche des Proxmox aus.
    D.h. für Proxmox ist die VM an, der noVNC-Viewer von Proxmox zeigt aber nur nen schwarzen Bildschirm und reagiert auf nix.

    So. Hat jemand eine Idee, wie ich eine suspendete Qemu-VM wieder unsuspenden kann? Oder muss ich sie hart rebooten?

    #Proxmox #VM #Qemu #noVNC #zerbastelt

  29. Ich Held hab' mal wieder was zerbastelt:
    Ich hab' eine (Qemu) VM auf einem Proxmox schlafen gelegt… also suspended… vom GUI der Maschine aus (via noVNC), nicht von der Weboberfläche des Proxmox aus.
    D.h. für Proxmox ist die VM an, der noVNC-Viewer von Proxmox zeigt aber nur nen schwarzen Bildschirm und reagiert auf nix.

    So. Hat jemand eine Idee, wie ich eine suspendete Qemu-VM wieder unsuspenden kann? Oder muss ich sie hart rebooten?

    #Proxmox #VM #Qemu #noVNC #zerbastelt

  30. Ich Held hab' mal wieder was zerbastelt:
    Ich hab' eine (Qemu) VM auf einem Proxmox schlafen gelegt… also suspended… vom GUI der Maschine aus (via noVNC), nicht von der Weboberfläche des Proxmox aus.
    D.h. für Proxmox ist die VM an, der noVNC-Viewer von Proxmox zeigt aber nur nen schwarzen Bildschirm und reagiert auf nix.

    So. Hat jemand eine Idee, wie ich eine suspendete Qemu-VM wieder unsuspenden kann? Oder muss ich sie hart rebooten?

    #Proxmox #VM #Qemu #noVNC #zerbastelt

  31. Ich Held hab' mal wieder was zerbastelt:
    Ich hab' eine (Qemu) VM auf einem Proxmox schlafen gelegt… also suspended… vom GUI der Maschine aus (via noVNC), nicht von der Weboberfläche des Proxmox aus.
    D.h. für Proxmox ist die VM an, der noVNC-Viewer von Proxmox zeigt aber nur nen schwarzen Bildschirm und reagiert auf nix.

    So. Hat jemand eine Idee, wie ich eine suspendete Qemu-VM wieder unsuspenden kann? Oder muss ich sie hart rebooten?

    #Proxmox #VM #Qemu #noVNC #zerbastelt

  32. Ich Held hab' mal wieder was zerbastelt:
    Ich hab' eine (Qemu) VM auf einem Proxmox schlafen gelegt… also suspended… vom GUI der Maschine aus (via noVNC), nicht von der Weboberfläche des Proxmox aus.
    D.h. für Proxmox ist die VM an, der noVNC-Viewer von Proxmox zeigt aber nur nen schwarzen Bildschirm und reagiert auf nix.

    So. Hat jemand eine Idee, wie ich eine suspendete Qemu-VM wieder unsuspenden kann? Oder muss ich sie hart rebooten?

    #Proxmox #VM #Qemu #noVNC #zerbastelt

  33. backed up my iBook G3's 30GB HDD to another newer drive in case it failed on me as it is 24~ years old.

    I also got it running QEMU, faster than the actual hardware with a bigger clock speed and more RAM.

    (700~ -> 900MHz, 256 -> 512MB)

    It last woke up on the iBook G3, now it's woken up in a QEMU PPC VM running on Apple Silicon.

    I'm really impressed that it just worked.

    #macOS #iBook #Computing #Apple #QEMU #Tech #Technology

  34. backed up my iBook G3's 30GB HDD to another newer drive in case it failed on me as it is 24~ years old.

    I also got it running QEMU, faster than the actual hardware with a bigger clock speed and more RAM.

    (700~ -> 900MHz, 256 -> 512MB)

    It last woke up on the iBook G3, now it's woken up in a QEMU PPC VM running on Apple Silicon.

    I'm really impressed that it just worked.

    #macOS #iBook #Computing #Apple #QEMU #Tech #Technology

  35. backed up my iBook G3's 30GB HDD to another newer drive in case it failed on me as it is 24~ years old.

    I also got it running QEMU, faster than the actual hardware with a bigger clock speed and more RAM.

    (700~ -> 900MHz, 256 -> 512MB)

    It last woke up on the iBook G3, now it's woken up in a QEMU PPC VM running on Apple Silicon.

    I'm really impressed that it just worked.

    #macOS #iBook #Computing #Apple #QEMU #Tech #Technology

  36. backed up my iBook G3's 30GB HDD to another newer drive in case it failed on me as it is 24~ years old.

    I also got it running QEMU, faster than the actual hardware with a bigger clock speed and more RAM.

    (700~ -> 900MHz, 256 -> 512MB)

    It last woke up on the iBook G3, now it's woken up in a QEMU PPC VM running on Apple Silicon.

    I'm really impressed that it just worked.

    #macOS #iBook #Computing #Apple #QEMU #Tech #Technology