Opened 7 years ago
Last modified 7 years ago
#16805 new defect
darwin kernel crash on starting VM
Reported by: | bronek | Owned by: | |
---|---|---|---|
Component: | VM control | Version: | VirtualBox 5.1.22 |
Keywords: | Cc: | ||
Guest type: | Windows | Host type: | Mac OS X |
Description (last modified by )
I've got 3 crashes in sequence each time when running Windows VM, either from scratch or saved state.
One of the crash report reads this error:
panic(cpu 5 caller 0xffffff8003809f4a): "vmx_on: unexpected return -2 from __vmxon()"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.1.32/osfmk/i386/vmx/vmx_cpu.c:198
Another two have:
panic(cpu 5 caller 0xffffff8011c09f4a): Kernel trap at 0xffffff8011aa6b34, type 6=invalid opcode, registers: panic(cpu 1 caller 0xffffff8015209f4a): Kernel trap at 0xffffff80150a6b34, type 6=invalid opcode, registers:
It happens in 5.1.22 as well as before the upgrade.
Please find crash report details in the attachment.
Attachments (3)
Change History (7)
by , 7 years ago
Attachment: | Kernel_2017-06-01-112439_kenorb.panic added |
---|
by , 7 years ago
Attachment: | Kernel_2017-06-01-113239_kenorb.panic added |
---|
panic(cpu 5 caller 0xffffff8011c09f4a): Kernel trap at 0xffffff8011aa6b34, type 6=invalid opcode
by , 7 years ago
Attachment: | Kernel_2017-06-01-114405_kenorb.panic added |
---|
panic(cpu 1 caller 0xffffff8015209f4a): Kernel trap at 0xffffff80150a6b34, type 6=invalid opcode
comment:1 by , 7 years ago
You have the following kexts loaded that look really suspicious:
1. com.bluestacks.kext.Hypervisor 2. foo.tap 3. foo.tun 4. com.globaldelight.driver.Boom2Device 5. org.pqrs.driver.Karabiner 6. com.paragon-software.filesystems.ntfs
Try to get rid of them, in the order that I listed them above. Especially the "bluestacks" one is the one that might cause the vmx message that you're seeing.
comment:2 by , 7 years ago
Description: | modified (diff) |
---|
comment:4 by , 7 years ago
Unless you changed something in the configuration of your host, like getting rid of some of the kexts that I told you, I would not expect the situation to be different if you launched it via the command line, Apple Remote Desktop, ssh, or RDP.
vmx_on: unexpected return -2 from vmxon()"@/Library/Caches/com.apple.xbs/Sources/xnu/xnu-3789.1.32/osfmk/i386/vmx/vmx_cpu.c:198