Virtualbox 6.1.34: Nope, smap not there for the guest even though it is there for the host (Ubuntu 20.04, but with a too-new kernel I can't test the driver against. Now... Where did I put that spare SSD....) VMWare Player: Have to check to see if SMAP is allowed there shortly... On Fri, May 20, 2022 at 7:09 PM Jim Mattson <jmattson@xxxxxxxxxx> wrote: > > On Fri, May 20, 2022 at 3:03 PM Brian Cowan <brcowan@xxxxxxxxx> wrote: > > > > Well, the weird thing is that this is hypervisor-specific. KVM=kaboom. > > VirtualBox is happy, and we can't make this happen on > > roughly-analogous ESX hosts. I can't directly test on my (ubuntu) > > laptop because the driver won't build on the too-new ubuntu 20.04.2 > > "Hardware enablement" kernel as it's too new. But either all the other > > hypervisors are doing this wrong and allowing this access, or KVM is. > > > > Not being a kernel expert makes this interesting. I'm passing the > > possibility list over the wall to the kernel folks, but most of the > > evidence we're seeing **seems** to point to KVM... > > Which version of kvm? Any unusual kvm module parameters? > > Does the guest under the happy hypervisors report that it has smap (in > /proc/cpuidinfo)?
