Windows guest breaks Mac OS X host if Mac Sleeps

[bigmac182]

I have a Windows 10 guest running on Mac OS X 10.11.4 (El Capitan) and if my Mac goes to sleep while running the Windows 10 guest I get the Mac version of the blue screen of death and have to reboot.

Log just shows it going to sleep and then rebooting:


2/8/16 12:52:09.000 PM kernel[0]: Opened file /var/log/SleepWakeStacks.bin, size 172032, extents 1, maxio 2000000 ssd 1
2/8/16 12:52:09.000 PM kernel[0]: polled file major 1, minor 0, blocksize 4096, pollers 5
2/8/16 12:52:09.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000280
2/8/16 12:52:09.000 PM kernel[0]: ARPT: 12308.127747: AirPort_Brcm43xx::powerChange: System Sleep
2/8/16 12:52:09.000 PM kernel[0]: ARPT: 12308.127766: IOPMPowerSource Information: onSleep, SleepType: Normal Sleep, 'ExternalConnected': Yes, 'TimeRemaining': 0,
2/8/16 12:52:09.000 PM kernel[0]: AppleCamIn::systemWakeCall - messageType = 0xE0000340
2/8/16 1:28:20.000 PM kernel[0]: AppleThunderboltNHIType2::prePCIWake - power up complete - took 14 us
2/8/16 1:28:20.000 PM kernel[0]: AppleThunderboltGenericHAL::earlyWake - complete - took 0 milliseconds
2/8/16 1:28:20.000 PM kernel[0]: AirPort: Link Down on awdl0. Reason 1 (Unspecified).
2/8/16 1:28:20.000 PM kernel[0]: ARPT: 12308.805169: wl0: leaveModulePoweredForOffloads: Wi-Fi will stay on.


Any suggestions?

[mpack]

It is rather important to know the VirtualBox version, and the Win10 build number for that matter.

[loukingjr]

This thread needs to be moved to VirtualBox on Mac OS X pre-releases. Assuming "10.11.4" is not a typo.

[bigmac182]

Not a typo. I didnt realize there was a pre-release queue.

Mac build is - 10.11.4 Beta (15E33e)
Virtual box version is- 5.0.14

Windows Build is- Version 1511 (OS Build 10586.71)

Very repeatable as it just happened again.

Please move where needed

Here is the crash report:

*** Panic Report ***
panic(cpu 0 caller 0xffffff8012fcc23a): Kernel trap at 0xffffff92166bfa6c, type 6=invalid opcode, registers:
CR0: 0x000000008001003b, CR2: 0x000000010836d000, CR3: 0x0000000100bff118, CR4: 0x00000000001627e0
RAX: 0x0000000000000000, RBX: 0xffffff9200920000, RCX: 0x0000000000000000, RDX: 0xffffff92167c0380
RSP: 0xffffff92117439f0, RBP: 0xffffff9211743a10, RSI: 0xffffff9200920000, RDI: 0x000000001e87a000
R8: 0xffffff92166d6cf0, R9: 0xffffff9211743a10, R10: 0xffffff9211743b08, R11: 0x0000000000000206
R12: 0xffffff9200905000, R13: 0xffffff9200920000, R14: 0xffffff9200905000, R15: 0xffffff9211743eb0
RFL: 0x0000000000010246, RIP: 0xffffff92166bfa6c, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x000000010836d000, Error code: 0x0000000000000000, Fault CPU: 0x0, PL: 1

Backtrace (CPU 0), Frame : Return Address
0xffffff9211743680 : 0xffffff8012ed8b12
0xffffff9211743700 : 0xffffff8012fcc23a
0xffffff92117438e0 : 0xffffff8012fea143
0xffffff9211743900 : 0xffffff92166bfa6c
0xffffff9211743a10 : 0xffffff92166bf236
0xffffff9211743a40 : 0xffffff92166d6ef3
0xffffff9211743ab0 : 0xffffff7f95ed280b
0xffffff9211743ac0 : 0xffffff7f95ee5ad5
0xffffff9211743b60 : 0xffffff8013136b62
0xffffff9211743ba0 : 0xffffff8013124bae
0xffffff9211743c30 : 0xffffff8013119bda
0xffffff9211743e20 : 0xffffff8013383e6b
0xffffff9211743e50 : 0xffffff80133c56ed
0xffffff9211743f60 : 0xffffff8013425d91
0xffffff9211743fb0 : 0xffffff8012fea946
Kernel Extensions in backtrace:
org.virtualbox.kext.VBoxDrv(5.0.14)[A272EAA2-9920-3F34-A32A-F2FD5C05D271]@0xffffff7f95ed1000->0xffffff7f95f30fff

BSD process name corresponding to current thread: VirtualBoxVM

[socratis]

You should definitely move the discussion to the thread that already deals with this very issue: Board index ‹ General ‹ VirtualBox on Mac OS X Hosts ‹ VirtualBox on Mac OS X pre-releases ‹ Sleep kernel panics on 10.11.4 Beta.

[mpack]

Locking this one.