The Kernel-based Virtual Machine (KVM) allows Linux systems to function as hypervisors without needing any extra software, but VMs created with it don’t behave exactly like real hardware does. Sometimes that’s important, though, so [sandwich] built a tool called vfio-native that obscures the fact that software might be running in a virtual machine.

There are plenty of the ways that virtual hardware differs from bare metal. The VM may behave slightly differently for obscure instructions in ways that are measurable, it may take slightly longer to perform some tasks, or the hypervisor may simply announce itself directly. vfio-native includes some kernel patches that solve some bugs which address the different behaviors, changes the way that the kernel identifies itself, and attempts to force the CPUs to behave in ways that real hardware would behave. With all of this applied to the virtual machine, it scores a 1/85 against a VM detection tool, with a standard KVM virtual machine scoring 10/85.

For anyone looking to test this out, it’s available in the AUR for Arch Linux. Also, it’s probably worth mentioning that there are more reasons to use this than cheating at Counter-Strike. For example, security researchers testing malware need to know how that software behaves when it thinks its on real hardware, and some may behave in benign ways when confined to virtual machines. Some licensed software also may disable itself when it detects its running in a VM, which can be a nuisance for things like software controlling industrial tools which only run on operating systems that are no longer maintained or hardware that can’t be found anymore. Some other tools we’ve seen before perform similar tasks as well.

Since we last covered the way that the Linux Kernel project has been dealing with the influx of code created using LLM-based coding assistants, all the way back in April, things have changed a lot, with most recently the Linux maintainers deciding to fully drop the requirement to mark LLM-assisted commits with the Assisted-by tag.

While not a fully uncontroversial decision – as also reported by Phoronix – with key maintainers already having made this decision it seems certain to proceed. This is not the only change made fairly recently, with a ‘Sashiko’ bot introduced that is supposed to handle code reviews.

In a July LKML post [Linus Torvalds] defends this decision, with a follow-up post in August by [Jakub Kicinski] it being stated that budget has been secured for using Meta’s LLMs, using said LLM-based resources for reviewing patches, as well as creating and editing commit messages. As noted by [Jakub] they’re running multiple frontier models on each patch to try and weed out confabulations.

Whether this will prove to be the right decision remains to be seen. Whereas most open source projects have firmly banished or heavily curtailed LLM-based contributions on slop, copyright as well as licensing grounds, the Linux Kernel project may be an interesting experiment in what the outcome of the exact opposite approach will be.