VirtualBox

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 Frank Mehnert)

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)

Kernel_2017-06-01-112439_kenorb.panic (7.7 KB ) - added by bronek 7 years ago.
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
Kernel_2017-06-01-113239_kenorb.panic (8.0 KB ) - added by bronek 7 years ago.
panic(cpu 5 caller 0xffffff8011c09f4a): Kernel trap at 0xffffff8011aa6b34, type 6=invalid opcode
Kernel_2017-06-01-114405_kenorb.panic (8.8 KB ) - added by bronek 7 years ago.
panic(cpu 1 caller 0xffffff8015209f4a): Kernel trap at 0xffffff80150a6b34, type 6=invalid opcode

Download all attachments as: .zip

Change History (7)

by bronek, 7 years ago

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

by bronek, 7 years ago

panic(cpu 5 caller 0xffffff8011c09f4a): Kernel trap at 0xffffff8011aa6b34, type 6=invalid opcode

by bronek, 7 years ago

panic(cpu 1 caller 0xffffff8015209f4a): Kernel trap at 0xffffff80150a6b34, type 6=invalid opcode

comment:1 by Socratis, 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 Frank Mehnert, 7 years ago

Description: modified (diff)

comment:3 by bronek, 7 years ago

Some when starting VM from the command line: VBoxManage startvm SomeVM

comment:4 by Socratis, 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.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use