jono

Getting this issue as well... EDIT: The issue was indeed SELinux, at least for me. I (temporarily) fixed it by running `setenforce 0`.

Here's the (hopefully final) solution that I've come up with to fix SELinux issues: EDIT: changed commands to use `semanage fcontext` since `chcon` is temporary... EDIT2: marked projectsend/cache as writeable...

Getting the same issue. The fix seems to be changing https://github.com/projectsend/projectsend/blob/28bb937d7a270284ccdd8eda6d25db47e61f5d37/manage-files.php#L306-L314

@thewolfram Sorry for the late reply! `invtsc` isn't related to this problem, although the game spamming `cpuid` is a much more realistic scenario. You can just use the usermode logger...

> Its ok, I'm replying from another account because unable to access mine, anyway some guy posted that it is for sure happening because game is spamming `cpuid`. Do you...

> > > Its ok, I'm replying from another account because unable to access mine, anyway some guy posted that it is for sure happening because game is spamming `cpuid`....

> I've got another idea which is get the return address in our `cpuid` emulation function so we find out who is spamming it, and then ept hook the page...

> What do you mean by return address? You can check guest rip in the vmcs to see who called cpuid, but finding the return address would be difficult without...

Related solution by Daax: https://www.unknowncheats.me/forum/3247434-post5.html. The only downside to his solution is that it requires a vm-exit on every `rdtsc` instruction, which results in a heavy performance hit. The general...

One idea is to enable/disable `rdtsc` vm-exiting only when it is required: i.e. only when `cpuid` or a similar instruction has been executed.