Attachments (1)
Change History (6)
by , 11 years ago
comment:1 by , 11 years ago
comment:2 by , 11 years ago
Summary: | problem start after update 4.3.4 → problem start after update 4.3.4 (VERR_VMX_VMXON_FAILED) |
---|
comment:5 by , 3 years ago
for those who find this thread later by Google:
POSSIBLE ERROR CODES:
VERR_VMM_SET_JMP_ABORTED_RESUME
VERR_VMX_VMXON_FAILED
POSSIBLE SOLUTIONS:
1) Problem with your proprietary BIOS. If it's not possible for you to switch to the opensource coreboot BIOS, at least try to update your proprietary BIOS to the latest version - or, if you are already on the latest-available version, reset your BIOS settings to default and save, then enable the virtualization and save again.
2) Problem with your antivirus software (i.e. Avast) which might be abusing the virtualization. Disable the hardware acceleration / virtualization in your antivirus settings, then reboot ( i.e. uncheck "Enable hardware-assisted virtualization" in Avast "Settings > General > troubleshooting", according to https://forums.virtualbox.org/viewtopic.php?f=1&t=105661#p515784 )
3) Problem with old VirtualBox compatibility with the very fresh Linux. Try to update your VirtualBox to the latest possible version (which in some cases may be beta) to fix this.
see attachment