Closed cryptolok closed 8 years ago
Thanks for the bug report. The error seems to be related to KVM, not NoFear.
I dug through the Linux kernel source code and I assume you get this error because another hypervisor is running. hardware_enable()
returns -EBUSY
if the bit VMXE
of CR4
is set. Can you confirm that another hypervisor is running?
Yep, you're right... I forgot about another hypervisor... Runs great by the way. Nice project and thanks!
After
YOLO
installation with root on a physical machine and patchapply
ing, when trying to launchnofear
:Exit status 128.
Kernel logs indicate:
Whereas host CPU supports VMX and I use KVM regularly.
Any suggestions?