{"slug": "kvm", "name": "KVM", "category": "infra", "category_name": "Infrastructure and DevOps", "description": "", "recommenders": 6, "commenters": 20, "warners": 6, "score": 1.764, "rising": -0.64, "first": "2025-11-27", "latest": "2026-09-26", "why": "addition of KVM! I remember when this was not a given, in the Xen days", "why_is_quote": true, "has_verdict": false, "sentiment": {"recommend": 6, "neutral": 7, "compare": 1, "warn": 6}, "spark": [0, 0, 1, 1, 2, 0, 0, 1, 0, 1, 0, 0], "listed": true, "loved": [], "caveat": "", "short_quote": "addition of KVM! I remember when this was not a given, in the Xen days", "kind": "", "icon": true, "domain": null, "github_repo": null, "official_url": "https://linux-kvm.org", "pricing": "", "aliases": ["KVM"], "verdict": null, "praise": [{"label": "", "summary": "", "quotes": [{"id": 790396577, "item_id": 49399786, "url": "https://news.ycombinator.com/item?id=49399786", "by": "isityettime", "date": "2026-08-22", "version": null, "stance": "recommend", "quote": "addition of KVM! I remember when this was not a given, in the Xen days", "excerpt": "I imagine for some end users a lot of this stuff is happily invisible, just like you say. But for me, a few kinds of changes have been highly visible as a user: - basically all filesystem changes, especially the mainstreaming of copy-on-write filesystems - not a change, but dramatically better filesystems performance than Windows or macOS has always been noticeable - the addition of cgroups and cgroupsv2, and later u", "context": "", "use_case": "virtualization", "switched_from": "Xen", "story": "Linux 7.2 Released"}, {"id": 777956689, "item_id": 48622293, "url": "https://news.ycombinator.com/item?id=48622293", "by": "sgc", "date": "2026-06-21", "version": null, "stance": "recommend", "quote": "I prefer a lot more security for a bit less flexibility.", "excerpt": "I think in most scenarios you don't need to worry so much about kvm ram use, since it looks static but actually it's not and you can over-commit [1]. And of course disk allocation can be dynamic as well. I prefer a lot more security for a bit less flexibility. I am not as ram rich as you are, and still every time I think of my few LXCs, my main thought is 'why did I do that?'. [1] https://docs.redhat.com/en/documenta", "context": "", "use_case": "Virtual machines", "switched_from": "", "story": "Running MicroVMs in Proxmox VE, the Easy Way"}, {"id": 759614259, "item_id": 47475891, "url": "https://news.ycombinator.com/item?id=47475891", "by": "imtringued", "date": "2026-03-22", "version": null, "stance": "recommend", "quote": "don't forget to enable KVM for performance", "excerpt": ">Okay, so you're running into the same problem that LLMs are. I can't tell if you are a troll or not, but you can't complain that nobody understands your intentionally vague and obtuse way to describe the problem at hand to pretend you're superior. https://www.publiccontractsscotland.gov.uk/NoticeDownload/DownloadDocument.aspx?id=OCT398050&idx=9 You have to rename the file ending to PDF. It's probably the wrong spec,", "context": "", "use_case": "", "switched_from": "", "story": "Some Things Just Take Time"}, {"id": 759567537, "item_id": 47472971, "url": "https://news.ycombinator.com/item?id=47472971", "by": "k_roy", "date": "2026-03-21", "version": null, "stance": "recommend", "quote": "\u201cvmm\u201d is a toy compared to kvm/libvirt.", "excerpt": "> I have a small Alpine VM that I often forget about \u201cvmm\u201d is a toy compared to kvm/libvirt. > I also have Debian 12 on a Mac Mini and while it's systemd, it could be OpenRC for all that I care about it. I assume Intel? I haven\u2019t paid attention to Linux on Macs in a long time. But I love Devuan for this reason.", "context": "", "use_case": "", "switched_from": "", "story": "Revert \"userdb: add birthDate field to JSON user records"}, {"id": 759286019, "item_id": 47455376, "url": "https://news.ycombinator.com/item?id=47455376", "by": "imtringued", "date": "2026-03-20", "version": null, "stance": "recommend", "quote": "I use limactl with qemu and kvm", "excerpt": "I think this is particularly evident with AI. The early adopters started years ago and they've seen improvements over time that they started attributing them to their own skill. They tell you that if you didn't spend years prompting the AI, it will be difficult to catch up. However, the exact opposite is happening. As the models get better, the need for the perfect prompt starts waning. Prompt engineering is a skill ", "context": "", "use_case": "", "switched_from": "", "story": "I'm OK being left behind, thanks"}]}], "caveats": [{"label": "", "summary": "", "quotes": [{"id": 791798896, "item_id": 49487431, "url": "https://news.ycombinator.com/item?id=49487431", "by": "d3Xt3r", "date": "2026-08-29", "version": null, "stance": "warn", "quote": "Unfortunately even your solution isn't immune to vulnerabilities, as kvm can be leveraged to gain access to the host", "excerpt": "Unfortunately even your solution isn't immune to vulnerabilities, as kvm can be leveraged to gain access to the host by means of exploits like Januscape (CVE-2026-53359) or Zapscape (CVE-2026-64561). A more secure option would be to avoid kvm completely and just run the container under an isolated kernel space using mklinux. The other advantage of mklinux is performance, there's no virtualisation tax to pay. See: htt", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: MicroVM daemon, deploy any Docker image"}, {"id": 791274659, "item_id": 49454666, "url": "https://news.ycombinator.com/item?id=49454666", "by": "bonzini", "date": "2026-08-26", "version": null, "stance": "warn", "quote": "it was KVM that turned out to have the worst bugs", "excerpt": "QEMU has a secure subset, and the kitchen sink around it. For a properly configured VM, even better if wrapped in SELinux, it is not easy to escape even QEMU. In this case, of the four bugs it found: * Two were in libslirp, which is not part of that subset; user mode networking these days should use passt (https://passt.top/), an insanely cool hack that does user mode networking at many Gb/s and is secure * One (whic", "context": "", "use_case": "", "switched_from": "", "story": "VMs won't contain cyber-capable agents"}, {"id": 787218912, "item_id": 49201182, "url": "https://news.ycombinator.com/item?id=49201182", "by": "ux266478", "date": "2026-08-06", "version": null, "stance": "warn", "quote": "you don't touch hardware virtualization with a 10 foot pole", "excerpt": "Gonna have to point out that's a KVM CVE. I was very specific about using a bytecode interpreter. If you're serious about a secure sandbox, you don't touch hardware virtualization with a 10 foot pole. In fact, you don't even use an emulator that lowers code into native machine code like QEMU. The standard for secure sandboxes is Bochs: https://github.com/bochs-emu/Bochs Not that Bochs is perfect, a new CVE was discov", "context": "", "use_case": "", "switched_from": "", "story": "Humans missed 1 in 3 threats approving AI agent commands across 40k game runs"}, {"id": 782159089, "item_id": 48884943, "url": "https://news.ycombinator.com/item?id=48884943", "by": "rurban", "date": "2026-07-12", "version": null, "stance": "warn", "quote": "Now everybody switched to kvm with none. Only speed matters, security not at all.", "excerpt": "There was no abuse and bad attitude. He was telling the truth about Linux hypervisors. And it got worse since then. Then they talked Xen, which at least has a security boundary. Now everybody switched to kvm with none. Only speed matters, security not at all.", "context": "", "use_case": "hypervisor", "switched_from": "", "story": "Theo de Raadt: \"You've been smoking something mind altering\" (2007)"}]}], "who": [{"by": "crabbone", "context": "sets up air-gapped testing of their product", "url": "https://news.ycombinator.com/item?id=49855295", "date": "2026-09-26"}, {"by": "freedomben", "context": "all-Linux user", "url": "https://news.ycombinator.com/item?id=48437600", "date": "2026-06-07"}], "tags": [], "use_cases": ["virtualization", "air-gapped product testing", "hypervisor", "virtual machines", "stateful virtual machines", "vm hosting"], "compared": [{"slug": "xen", "name": "Xen", "co": 5, "switched_from": 1, "switched_to": 0}, {"slug": "qemu", "name": "QEMU", "co": 6, "switched_from": 0, "switched_to": 0}, {"slug": "linux", "name": "Linux", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "proxmox", "name": "Proxmox", "co": 3, "switched_from": 0, "switched_to": 0}, {"slug": "qubes-os", "name": "Qubes OS", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "codex", "name": "Codex", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "macos", "name": "macOS", "co": 2, "switched_from": 0, "switched_to": 0}, {"slug": "freebsd", "name": "FreeBSD", "co": 2, "switched_from": 0, "switched_to": 0}], "makers": [], "threads": [{"url": "https://news.ycombinator.com/item?id=49849985", "title": "Revealing the details of how OpenAI agents hacked Hugging Face", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49485801", "title": "Show HN: MicroVM daemon, deploy any Docker image", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49450188", "title": "VMs won't contain cyber-capable agents", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49376265", "title": "Linux 7.2 Released", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49213029", "title": "Responding to the next frontier of critical cyber capabilities", "mentions": 1}, {"url": "https://news.ycombinator.com/item?id=49195468", "title": "Humans missed 1 in 3 threats approving AI agent commands across 40k game runs", "mentions": 1}], "sentiment_by_month": {"2025-11": {"neutral": 1}, "2025-12": {"neutral": 2}, "2026-01": {"warn": 1, "recommend": 1}, "2026-02": {"recommend": 1}, "2026-03": {"recommend": 2, "compare": 1}, "2026-04": {}, "2026-05": {"neutral": 1}, "2026-06": {"neutral": 1, "recommend": 1}, "2026-07": {"warn": 2}, "2026-08": {"warn": 3, "neutral": 1, "recommend": 1}, "2026-09": {"neutral": 1}, "2026-10": {}}, "versions": [], "version_unnamed": 0, "family_ref": null, "runs_on": null, "lines": [], "quotes": [{"id": 797684720, "item_id": 49855295, "url": "https://news.ycombinator.com/item?id=49855295", "by": "crabbone", "date": "2026-09-26", "version": null, "stance": "neutral", "quote": "we use KVM, so, I just edit the VM description and remove the NIC from it", "excerpt": "Part of my day job is to set up testing of our product in air-gapped environment. It's not difficult. There's a straightforward way to ensure no connection to Internet (we use KVM, so, I just edit the VM description and remove the NIC from it). It's not any kind of rocket science. The tests then communicate over serial console. The reason we have to test it isn't because our product would randomly break into someone ", "context": "sets up air-gapped testing of their product", "use_case": "air-gapped product testing", "switched_from": "", "story": "Revealing the details of how OpenAI agents hacked Hugging Face"}, {"id": 791798896, "item_id": 49487431, "url": "https://news.ycombinator.com/item?id=49487431", "by": "d3Xt3r", "date": "2026-08-29", "version": null, "stance": "warn", "quote": "Unfortunately even your solution isn't immune to vulnerabilities, as kvm can be leveraged to gain access to the host", "excerpt": "Unfortunately even your solution isn't immune to vulnerabilities, as kvm can be leveraged to gain access to the host by means of exploits like Januscape (CVE-2026-53359) or Zapscape (CVE-2026-64561). A more secure option would be to avoid kvm completely and just run the container under an isolated kernel space using mklinux. The other advantage of mklinux is performance, there's no virtualisation tax to pay. See: htt", "context": "", "use_case": "", "switched_from": "", "story": "Show HN: MicroVM daemon, deploy any Docker image"}, {"id": 791274659, "item_id": 49454666, "url": "https://news.ycombinator.com/item?id=49454666", "by": "bonzini", "date": "2026-08-26", "version": null, "stance": "warn", "quote": "it was KVM that turned out to have the worst bugs", "excerpt": "QEMU has a secure subset, and the kitchen sink around it. For a properly configured VM, even better if wrapped in SELinux, it is not easy to escape even QEMU. In this case, of the four bugs it found: * Two were in libslirp, which is not part of that subset; user mode networking these days should use passt (https://passt.top/), an insanely cool hack that does user mode networking at many Gb/s and is secure * One (whic", "context": "", "use_case": "", "switched_from": "", "story": "VMs won't contain cyber-capable agents"}, {"id": 790396577, "item_id": 49399786, "url": "https://news.ycombinator.com/item?id=49399786", "by": "isityettime", "date": "2026-08-22", "version": null, "stance": "recommend", "quote": "addition of KVM! I remember when this was not a given, in the Xen days", "excerpt": "I imagine for some end users a lot of this stuff is happily invisible, just like you say. But for me, a few kinds of changes have been highly visible as a user: - basically all filesystem changes, especially the mainstreaming of copy-on-write filesystems - not a change, but dramatically better filesystems performance than Windows or macOS has always been noticeable - the addition of cgroups and cgroupsv2, and later u", "context": "", "use_case": "virtualization", "switched_from": "Xen", "story": "Linux 7.2 Released"}, {"id": 787437201, "item_id": 49214825, "url": "https://news.ycombinator.com/item?id=49214825", "by": "sparsesignal", "date": "2026-08-07", "version": null, "stance": "neutral", "quote": "moving the whole dev environment (editors, agents, containers) inside a QEMU/KVM VM", "excerpt": "> I stress about my agent sandboxes all the time Same here, so I ended up moving the whole dev environment (editors, agents, containers) inside a QEMU/KVM VM that reaches the internet but has no route to the host, the LAN, or any other private address. I wrote a script to create such VMs and also verify network containment by scanning outward from inside the guest. Even then, I still don't feel great when running age", "context": "", "use_case": "", "switched_from": "", "story": "Responding to the next frontier of critical cyber capabilities"}, {"id": 787218912, "item_id": 49201182, "url": "https://news.ycombinator.com/item?id=49201182", "by": "ux266478", "date": "2026-08-06", "version": null, "stance": "warn", "quote": "you don't touch hardware virtualization with a 10 foot pole", "excerpt": "Gonna have to point out that's a KVM CVE. I was very specific about using a bytecode interpreter. If you're serious about a secure sandbox, you don't touch hardware virtualization with a 10 foot pole. In fact, you don't even use an emulator that lowers code into native machine code like QEMU. The standard for secure sandboxes is Bochs: https://github.com/bochs-emu/Bochs Not that Bochs is perfect, a new CVE was discov", "context": "", "use_case": "", "switched_from": "", "story": "Humans missed 1 in 3 threats approving AI agent commands across 40k game runs"}, {"id": 782159089, "item_id": 48884943, "url": "https://news.ycombinator.com/item?id=48884943", "by": "rurban", "date": "2026-07-12", "version": null, "stance": "warn", "quote": "Now everybody switched to kvm with none. Only speed matters, security not at all.", "excerpt": "There was no abuse and bad attitude. He was telling the truth about Linux hypervisors. And it got worse since then. Then they talked Xen, which at least has a security boundary. Now everybody switched to kvm with none. Only speed matters, security not at all.", "context": "", "use_case": "hypervisor", "switched_from": "", "story": "Theo de Raadt: \"You've been smoking something mind altering\" (2007)"}, {"id": 780940560, "item_id": 48808785, "url": "https://news.ycombinator.com/item?id=48808785", "by": "rvz", "date": "2026-07-06", "version": null, "stance": "warn", "quote": "This one is really not good as it is the first KVM guest-to-host exploit working on both AMD and Intel.", "excerpt": "The full write up is here: [0]. This is a very nasty vulnerability and risks any service that uses and allows nested x86 virtualization features at risk. Including those running VMs as a service. > Running the PoC inside a guest VM can trigger a host kernel panic. A full escape exploit that works in a controlled environment also exists, but it is not released at this time and is planned to be released in the very dis", "context": "", "use_case": "virtualization", "switched_from": "", "story": "Januscape: Guest-to-Host Escape in KVM/x86 [CVE-2026-53359]"}, {"id": 777956689, "item_id": 48622293, "url": "https://news.ycombinator.com/item?id=48622293", "by": "sgc", "date": "2026-06-21", "version": null, "stance": "recommend", "quote": "I prefer a lot more security for a bit less flexibility.", "excerpt": "I think in most scenarios you don't need to worry so much about kvm ram use, since it looks static but actually it's not and you can over-commit [1]. And of course disk allocation can be dynamic as well. I prefer a lot more security for a bit less flexibility. I am not as ram rich as you are, and still every time I think of my few LXCs, my main thought is 'why did I do that?'. [1] https://docs.redhat.com/en/documenta", "context": "", "use_case": "Virtual machines", "switched_from": "", "story": "Running MicroVMs in Proxmox VE, the Easy Way"}, {"id": 775001601, "item_id": 48437600, "url": "https://news.ycombinator.com/item?id=48437600", "by": "freedomben", "date": "2026-06-07", "version": null, "stance": "neutral", "quote": "I use KVM (with virt-manager) extensively", "excerpt": "I love podman and use it extensively, but am less sure how useful the machine functionality will be (to me). I use KVM (with virt-manager) extensively, and I could see how treating VMs as ephemeral like containers might be nice for some workflows, but for me I want my VMs to be stateful as they are now. Anything I want container workflow for I just use containers. I don't do any Windows though, all linux. What are so", "context": "all-Linux user", "use_case": "stateful virtual machines", "switched_from": "", "story": "Podman 6: machine usability improvements"}, {"id": 770854800, "item_id": 48178425, "url": "https://news.ycombinator.com/item?id=48178425", "by": "fsflover", "date": "2026-05-18", "version": null, "stance": "neutral", "quote": "", "excerpt": "Which other approach to security do you consider reliable? Through correctness? Through obscurity? https://blog.invisiblethings.org/2008/09/02/three-approaches-to-computer-security.html", "context": "", "use_case": "", "switched_from": "", "story": "The foundations of a provably secure operating system (PSOS) (1979) [pdf]"}, {"id": 761217954, "item_id": 47576122, "url": "https://news.ycombinator.com/item?id=47576122", "by": "sidkshatriya", "date": "2026-03-30", "version": null, "stance": "compare", "quote": "I can't imagine its been tested as thoroughly as KVM", "excerpt": "I love FreeBSD but Linux just provides every feature under the sun when it comes to virtualization. Do you find any missing features on bhyve ? Is bhyve reliable ? I can't imagine its been tested as thoroughly as KVM ...", "context": "", "use_case": "virtualization", "switched_from": "", "story": "From Proxmox to FreeBSD and Sylve in Our Office Lab"}, {"id": 759614259, "item_id": 47475891, "url": "https://news.ycombinator.com/item?id=47475891", "by": "imtringued", "date": "2026-03-22", "version": null, "stance": "recommend", "quote": "don't forget to enable KVM for performance", "excerpt": ">Okay, so you're running into the same problem that LLMs are. I can't tell if you are a troll or not, but you can't complain that nobody understands your intentionally vague and obtuse way to describe the problem at hand to pretend you're superior. https://www.publiccontractsscotland.gov.uk/NoticeDownload/DownloadDocument.aspx?id=OCT398050&idx=9 You have to rename the file ending to PDF. It's probably the wrong spec,", "context": "", "use_case": "", "switched_from": "", "story": "Some Things Just Take Time"}, {"id": 759567537, "item_id": 47472971, "url": "https://news.ycombinator.com/item?id=47472971", "by": "k_roy", "date": "2026-03-21", "version": null, "stance": "recommend", "quote": "\u201cvmm\u201d is a toy compared to kvm/libvirt.", "excerpt": "> I have a small Alpine VM that I often forget about \u201cvmm\u201d is a toy compared to kvm/libvirt. > I also have Debian 12 on a Mac Mini and while it's systemd, it could be OpenRC for all that I care about it. I assume Intel? I haven\u2019t paid attention to Linux on Macs in a long time. But I love Devuan for this reason.", "context": "", "use_case": "", "switched_from": "", "story": "Revert \"userdb: add birthDate field to JSON user records"}, {"id": 759286019, "item_id": 47455376, "url": "https://news.ycombinator.com/item?id=47455376", "by": "imtringued", "date": "2026-03-20", "version": null, "stance": "recommend", "quote": "I use limactl with qemu and kvm", "excerpt": "I think this is particularly evident with AI. The early adopters started years ago and they've seen improvements over time that they started attributing them to their own skill. They tell you that if you didn't spend years prompting the AI, it will be difficult to catch up. However, the exact opposite is happening. As the models get better, the need for the perfect prompt starts waning. Prompt engineering is a skill ", "context": "", "use_case": "", "switched_from": "", "story": "I'm OK being left behind, thanks"}, {"id": 751461072, "item_id": 46966317, "url": "https://news.ycombinator.com/item?id=46966317", "by": "newsoftheday", "date": "2026-02-10", "version": null, "stance": "recommend", "quote": "I use KVM", "excerpt": "I use KVM, never tried proxmox, don't need it, don't want it.", "context": "", "use_case": "VM hosting", "switched_from": "", "story": "The Switch to Linux and the Beginning of My Self-Hosting Journey"}, {"id": 748224530, "item_id": 46764033, "url": "https://news.ycombinator.com/item?id=46764033", "by": "OhMeadhbh", "date": "2026-01-26", "version": null, "stance": "recommend", "quote": "FreeBSD VM via KVM and it seems to work well", "excerpt": "Lol. Yes. I would like to say that's not true... and for quite a while my Dell XPS would do all three, but it wasn't a cheap device. I think their driver team isn't supporting my 8 year old XPS anymore as sleeping is... problematic. And power management on linux laptops has always been worse than windows. But... I will gnaw my left arm off before I go back to Mach or WinNT. (Maybe I'll try using HaikuOS as my daily d", "context": "", "use_case": "", "switched_from": "", "story": "Apple, What Have You Done?"}, {"id": 746699473, "item_id": 46668717, "url": "https://news.ycombinator.com/item?id=46668717", "by": "Joel_Mckay", "date": "2026-01-18", "version": null, "stance": "warn", "quote": "A kvm hypervisor is not perfect", "excerpt": "A kvm hypervisor is not perfect, as sandbox escape was demonstrated even with https://qubes-os.org/ . On modern AMD/Intel/ARM64 consumer processors it is not possible to completely prevent bleeding keys across regions. Only the old Sun systems with hardware encrypted mmu pages could actually enforce context isolation. If performance is not important, and people are dealing with something particularly nasty... than ru", "context": "", "use_case": "", "switched_from": "", "story": "Singularity Rootkit: SELinux bypass and netlink filter (ss/conntrack hidden)"}, {"id": 742366209, "item_id": 46397888, "url": "https://news.ycombinator.com/item?id=46397888", "by": "crawshaw", "date": "2025-12-26", "version": null, "stance": "neutral", "quote": "Thank you! Yes, KVM.", "excerpt": "Thank you! Yes, KVM. And public IPs are very useful and we want to do them. We will have to charge and/or limit them, unlike VMs, unfortunately, because IPv4 is scarce. (I am busy trying to buy some right now.) You can follow along here: https://github.com/boldsoftware/exe.dev/issues/6", "context": "", "use_case": "Virtualization", "switched_from": "", "story": "Exe.dev/"}, {"id": 737767921, "item_id": 46110495, "url": "https://news.ycombinator.com/item?id=46110495", "by": "evanjrowley", "date": "2025-12-01", "version": null, "stance": "neutral", "quote": "Intel's GPU SR-IOV already works with KVM on Linux!", "excerpt": "https://learn.microsoft.com/en-us/windows-server/virtualization/hyper-v/gpu-partitioning#supported-gpus It relies upon SR-IOV and only several server-specific Nvidia GPUs are listed as supported. Intel's Flex dGPUs and Arc iGPUs have supported SR-IOV for years now, but they aren't listed there. It would be super awesome if Microsoft could add it for Intel Arc iGPUs, desktop versions of Windows, and WSL2! Intel's GPU ", "context": "", "use_case": "", "switched_from": "", "story": "Isn't WSL2 just a VM?"}, {"id": 737157569, "item_id": 46072348, "url": "https://news.ycombinator.com/item?id=46072348", "by": "afr0ck", "date": "2025-11-27", "version": null, "stance": "neutral", "quote": "I tried to port it to KVM", "excerpt": "I worked at Linaro, who was contracting for Qualcomm. Qualcomm were pushing for some protected hypervisor called Gunyah (which had its own Linux interface and needed a new qemu port) that apparently no one liked. I tried to port it to KVM [1], but upstream folks (mostly Google) outright rejected the port. Otherwise KVM would have been available on QCOM boards. You can still try it. I have a Linux kernel and a Qemu po", "context": "", "use_case": "", "switched_from": "", "story": "Same-day upstream Linux support for Snapdragon 8 Elite Gen 5"}]}