The thing is that your system is heavily modified in unknown ways. There's no way on earth that you're not getting any messages in the '/var/log/system.log' after a (un)successful run of a 'kextload' command. That alone put two huge question marks where my eye sockets used to be and had me scratching my head and hunting for answers. Shooting in the dark is an understatement.Lod wrote:their clean install is in fact from a system image created by them.
It wouldn't surprise me if it was the antivirus that's doing this. They may have a list of allowed kext files that are allowed or not to load? I have no clue. And Docker actually has a daemon running that gets a lock on the VirtualBox related kexts and you can't simply replace them on the fly, like you'd do with a normal VirtualBox installation. I don't even know why they're doing this, but I haven't studied it.
The final problem is that I can't replicate the problem with the kext loading, since I can't "fake" an unloadable kext. Let me know if you figure anything out.
