Why? Nothing wrong with running your network interface in a VM. There are reasons for doing so even if drivers aren't an issue. Qubes OS does this, for instance, for security reasons.
replyWindows also does. Almost everything is a VM in windows these days.
replyIt's just how things work these days. If you'd say "I run my VPN client in a docker container" it would raise a lot less eyebrows. Yet it's not very different, really.
Though conceptually I'd frown at having to run Linux. I'd prefer upgrading the hardware to a supported chip.
Windows isn't running entire fucking separate kernel to run wifi driver, the fuck you're talking about
replyDefinitely not independent kernels but my guess is he's referring to Virtualization-Based Security (VBS) - it gets turned on by default if your Win10/11 system has virtualization enabled.
reply One such example security solution is memory integrity, which protects and hardens Windows by running kernel mode code integrity within the isolated virtual environment of VBS. Kernel mode code integrity is the Windows process that checks all kernel mode drivers and binaries before they're started, and prevents unsigned or untrusted drivers or system files from being loaded into system memory.
Link: https://learn.microsoft.com/en-us/windows-hardware/design/de...
no matter how it's implemented, it must not be a user-requiring (or even user-facing) task
replyNot really weird when some firmware are close to being full blown OS. An alpine VM can be run with 64 MB which is lower than a lot of software.
replyI've used cellular modems which run Linux or ThreadX internally.
replyWeren't there iPhones that had wifi chips that ran Linux?
reply[dead]
reply