{
  "$type": "site.standard.document",
  "bskyPostRef": {
    "cid": "bafyreifw6xnkrjtl35vzcd3s4dacdnoob6sklxa7zrwj3hzo5l76kn6ezm",
    "uri": "at://did:plc:4n6wgsqsqm6q2hjncgwmreey/app.bsky.feed.post/3me7djophyt22"
  },
  "coverImage": {
    "$type": "blob",
    "ref": {
      "$link": "bafkreiheenidu5kbwdgs7wezsf345ooelyumap5vfl3fxbwf3nme7drmuq"
    },
    "mimeType": "image/jpeg",
    "size": 30712
  },
  "path": "/post/45262104",
  "publishedAt": "2026-02-05T16:09:49.000Z",
  "site": "https://programming.dev",
  "tags": [
    "Linux",
    "cm0002",
    "9 comments",
    "https://linuxiac.com/virtualbox-gains-a-working-kvm-backend-in-development-builds/"
  ],
  "textContent": "submitted by cm0002 to linux\n36 points | 9 comments\nhttps://linuxiac.com/virtualbox-gains-a-working-kvm-backend-in-development-builds/\n\n> A recent development in the VirtualBox source tree introduces an early but usable KVM backend for Linux hosts. According to a comment by contributor Alexander Eichner, the new backend is now in a workable state, or at least when running modern guest operating systems. Older or more unusual guests, such as DOS, have not yet been tested.\n>\n> And if you’re wondering what benefits this brings, the main one is that having a KVM backend allows VirtualBox to continue running virtual machines even when its own kernel modules (vboxdrv, vboxnetflt, vboxnetflt, vboxnetflt) cannot be loaded.\n>\n> This is especially relevant on modern Linux systems, where Secure Boot, kernel hardening, or distribution-specific policies can block third-party kernel drivers. In such cases, VirtualBox will now automatically fall back to using KVM if it is available on the host system.",
  "title": "VirtualBox Gains a Working KVM Backend [for Linux hosts] in Development Builds"
}