Crash MacBook Pro Host, Windows Guest

[rritoch]

Host:
macOS Catalina
Version 10.15.2
MacBook Pro (15-inch, 2019)
2.3 GHz 8-Core Intel Core i9
32 GB 2400 MHz DDR4
Radeon Pro Vega 20 4 GB
Intel UHD Graphics 630 1536 MB

Guest: Windows 10 Pro

Error:

Code: Select all

panic(cpu 2 caller 0xffffff801fe6520a): Kernel trap at 0xffffffa40a325f56, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007f92b80ae000, CR3: 0x00000007577cf18a, CR4: 0x00000000003626e0
RAX: 0x0000000000000000, RBX: 0x00007f92a0107144, RCX: 0x0000000000000200, RDX: 0x0000000000000515
RSP: 0xffffffa406294c60, RBP: 0xffffffa406294d00, RSI: 0x00007f92a00d0000, RDI: 0x00007f92b80ae000
R8:  0x00007f92a0107118, R9:  0x00007f92a0107178, R10: 0x0000000000000000, R11: 0x00007f92a0107142
R12: 0x00007f92a0107140, R13: 0x0000000000027000, R14: 0x00007f92a0107138, R15: 0x00007f92a0107118
RFL: 0x0000000000050246, RIP: 0xffffffa40a325f56, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00007f92b80ae000, Error code: 0x0000000000000002, Fault CPU: 0x2, PL: 1, VF: 5

Backtrace (CPU 2), Frame : Return Address
0xffffffa4062946c0 : 0xffffff801fd3bb1b 
0xffffffa406294710 : 0xffffff801fe733e5 
0xffffffa406294750 : 0xffffff801fe64e5e 
0xffffffa4062947a0 : 0xffffff801fce2a40 
0xffffffa4062947c0 : 0xffffff801fd3b207 
0xffffffa4062948c0 : 0xffffff801fd3b5eb 
0xffffffa406294910 : 0xffffff80204d24f9 
0xffffffa406294980 : 0xffffff801fe6520a 
0xffffffa406294b00 : 0xffffff801fe64f08 
0xffffffa406294b50 : 0xffffff801fce2a40 
0xffffffa406294b70 : 0xffffffa40a325f56 
0xffffffa406294d00 : 0xffffffa40a311735 
0xffffffa406294dc0 : 0xffffffa40a258da9 
0xffffffa406294df0 : 0xffffffa40a24de55 
0xffffffa406294e30 : 0xffffffa40a242ed5 
0xffffffa406294fb0 : 0xffffffa40a32d168 
0xffffff83dda838d0 : 0xffffffa40a25a906 
0xffffff83dda83a60 : 0xffffff7fa38d04cf 
0xffffff83dda83a70 : 0xffffff7fa38e320b 
0xffffff83dda83b30 : 0xffffff7fa38e2b79 
0xffffff83dda83b50 : 0xffffff801ffd6b02 
0xffffff83dda83b80 : 0xffffff801ffcae30 
0xffffff83dda83c00 : 0xffffff801ffbc12e 
0xffffff83dda83df0 : 0xffffff802025f8ab 
0xffffff83dda83e20 : 0xffffff80202b86f5 
0xffffff83dda83f40 : 0xffffff802039acba 
0xffffff83dda83fa0 : 0xffffff801fce3206 
      Kernel Extensions in backtrace:
         org.virtualbox.kext.VBoxDrv(6.0.14)[53BAF3B2-AB27-321B-9DF8-7A1395C58923]@0xffffff7fa38ce000->0xffffff7fa39bdfff

BSD process name corresponding to current thread: VirtualBoxVM
Boot args: chunklist-security-epoch=0 -chunklist-no-rev2-dev

Mac OS version:
19C57

Kernel version:
Darwin Kernel Version 19.2.0: Sat Nov  9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64
Kernel UUID: C3E7E405-C692-356B-88D3-C30041FD1E72
Kernel slide:     0x000000001fa00000
Kernel text base: 0xffffff801fc00000
__HIB  text base: 0xffffff801fb00000
System model name: MacBookPro15,3 (Mac-1E7E29AD0135F9BC)
System shutdown begun: NO

System uptime in nanoseconds: 894764642500
last loaded kext at 21448630108: >AudioAUUC	1.70 (addr 0xffffff7fa6e89000, size 28672)
last unloaded kext at 317981374231: >usb.!UHostPacketFilter	1.0 (addr 0xffffff7fa25e9000, size 24576)
loaded kexts:
org.virtualbox.kext.VBoxNetAdp	6.0.14
com.avast.PacketForwarder	2.1
org.virtualbox.kext.VBoxNetFlt	6.0.14
com.avast.FileShield	4.0.0
org.virtualbox.kext.VBoxUSB	6.0.14
org.virtualbox.kext.VBoxDrv	6.0.14
>AudioAUUC	1.70
@kext.AMDFramebuffer	3.0.4
@kext.AMDRadeonX5000	3.0.4
@kext.AMDRadeonServiceManager	3.0.4
>!AGraphicsDevicePolicy	4.5.21
@fileutil	20.036.15
@AGDCPluginDisplayMetrics	4.5.21
>!AHV	1
|IOUserEthernet	1.0.1
|IO!BSerialManager	7.0.2f4
>AGPM	111.4.1
>!APlatformEnabler	2.7.0d0
>X86PlatformShim	1.0.0
>pmtelemetry	1
>!AUpstreamUserClient	3.6.8
>AGDCBacklightControl	4.5.21
@Dont_Steal_Mac_OS_X	7.0.0
>!A!IKBLGraphics	14.0.3
>BridgeAudioCommunication	6.60
>!AThunderboltIP	3.1.3
@kext.AMD10000!C	3.0.4
>!AHIDALSService	1
>!ATopCaseHIDEventDriver	3420.1
>!A!ICFLGraphicsFramebuffer	14.0.3
>!AAVEBridge	6.1
>!AMCCSControl	1.13
>!AMuxControl2	4.5.21
>!ABridgeAudio!C	6.60
>!AGFXHDA	100.1.422
>!A!IPCHPMC	2.0.1
>!A!ISlowAdaptiveClocking	4.0.0
@filesystems.autofs	3.0
>usb.!UHostBillboardDevice	1.0
>BCMWLANFirmware4355.Hashstore	1
>BCMWLANFirmware4364.Hashstore	1
>BCMWLANFirmware4377.Hashstore	1
@filesystems.hfs.kext	522.0.9
@BootCache	40
@!AFSCompression.!AFSCompressionTypeDataless	1.0.0d1
@!AFSCompression.!AFSCompressionTypeZlib	1.0.0
>!AVirtIO	1.0
>!ABCMWLANBusInterfacePCIe	1
@filesystems.apfs	1412.61.1
@private.KextAudit	1.0
>!ASmartBatteryManager	161.0.0
>!AACPIButtons	6.1
>!ASMBIOS	2.1
>!AACPIEC	6.1
>!AAPIC	1.7
$!AImage4	1
@nke.applicationfirewall	303
$TMSafetyNet	8
@!ASystemPolicy	2.0.0
|EndpointSecurity	1
@kext.AMDRadeonX5000HWLibs	1.0
@kext.AMDRadeonX5000HWServices	3.0.4
|IOUSBUserClient	900.4.2
|IOAVB!F	800.17
>!ASSE	1.0
>!ABacklightExpert	1.1.0
@!AGPUWrangler	4.5.21
>!AHS!BDriver	3420.1
>IO!BHIDDriver	7.0.2f4
|IO!BHost!CUARTTransport	7.0.2f4
|IO!BHost!CTransport	7.0.2f4
>!A!ILpssUARTv1	3.0.60
>!A!ILpssUARTCommon	3.0.60
>!AOnboardSerial	1.0
|IOAccelerator!F2	438.2.8
>X86PlatformPlugin	1.0.0
>!ASMBus!C	1.0.18d1
>!AGraphicsControl	4.5.21
>!AHIDKeyboard	209
>!AActuatorDriver	3420.2
>!AMultitouchDriver	3420.2
>!AInputDeviceSupport	3420.4
|IONDRVSupport	569.3
>IOPlatformPlugin!F	6.0.0d8
@kext.AMDSupport	3.0.4
@!AGraphicsDeviceControl	4.5.21
|IOGraphics!F	569.3
|IOSlowAdaptiveClocking!F	1.0.0
@plugin.IOgPTPPlugin	800.14
|IOEthernetAVB!C	1.1.0
@kext.triggers	1.0
>usb.cdc.ncm	5.0.0
>usb.cdc	5.0.0
>usb.networking	5.0.0
>usb.!UHostCompositeDevice	1.2
>usb.!UHub	1.2
|IOSurface	269.6
@filesystems.hfs.encodings.kext	1
|IOAudio!F	300.2
@vecLib.kext	1.2.0
>!ABCMWLANCore	1.0.0
>mDNSOffloadUserClient	1.0.1b8
>IOImageLoader	1.0.0
|IOSerial!F	11
|IO80211!FV2	1200.12.2b1
>corecapture	1.0.4
|IOSkywalk!F	1
>!AThunderboltPCIDownAdapter	2.5.2
>!AThunderboltDPInAdapter	6.2.4
>!AThunderboltDPAdapter!F	6.2.4
>!AHPM	3.4.4
>!A!ILpssI2C!C	3.0.60
>!A!ILpssDmac	3.0.60
>!A!ILpssI2C	3.0.60
>!AThunderboltNHI	5.8.1
|IOThunderbolt!F	7.4.7
>usb.!UVHCIBCE	1.2
>usb.!UVHCI	1.2
>usb.!UVHCICommonBCE	1.0
>usb.!UVHCICommon	1.0
>!AEffaceableNOR	1.0
|IOBufferCopy!C	1.1.0
|IOBufferCopyEngine!F	1
|IONVMe!F	2.1.0
|IOUSB!F	900.4.2
>usb.!UXHCIPCI	1.2
>usb.!UXHCI	1.2
>!AEFINVRAM	2.1
>!AEFIRuntime	2.1
>!ASMCRTC	1.0
|IOSMBus!F	1.1
|IOHID!F	2.0.0
$quarantine	4
$sandbox	300.0
@kext.!AMatch	1.0.0d1
>!AKeyStore	2
>!UTDM	489.60.3
|IOSCSIBlockCommandsDevice	422.0.2
>!ACredentialManager	1.0
>KernelRelayHost	1
>!ASEPManager	1.0.1
>IOSlaveProcessor	1
>!AFDEKeyStore	28.30
>!AEffaceable!S	1.0
>!AMobileFileIntegrity	1.0.5
@kext.CoreTrust	1
|CoreAnalytics!F	1
|IOTimeSync!F	800.14
|IONetworking!F	3.4
>DiskImages	493.0.0
|IO!B!F	7.0.2f4
|IO!BPacketLogger	7.0.2f4
|IOUSBMass!SDriver	157.40.7
|IOSCSIArchitectureModel!F	422.0.2
|IO!S!F	2.1
|IOUSBHost!F	1.2
>usb.!UCommon	1.0
>!UHostMergeProperties	1.2
>!ABusPower!C	1.0
|IOReport!F	47
>!AACPIPlatform	6.1
>!ASMC	3.1.9
>watchdog	1
|IOPCI!F	2.9
|IOACPI!F	1.4
@kec.pthread	1
@kec.corecrypto	1.0
@kec.Libm	1

[JiF_Brodeur]

Hi, I found a way to make VirtualBox usable on macOS 10.15.2, change your Graphic Controller (VM - Settings - Display - Graphics Controller) to VBoxVGA instead of VMSVGA, it will complain of Invalid settings detected at the bottom but go ahead and always shutdown you VM, DO NOT SAVE state. There seems to be an issue related to the graphic driver.
Thanks
Jean-François

[socratis]

Jean-François,
As I mentioned in another thread: first investigate, then copy/paste. The OP isn't even using VMSVGA theoretically, they're using a Win10 guest which defaults to VBoxSVGA, not VMSVGA. And there's no mention of saved-state/resume...

[JiF_Brodeur]

Hi @Socratis, I mentioned the no save/restore recommendation since this is the most troublesome feature on macOS for VirtualBox. But I get the point.
Thanks
Jean-François

[socratis]

I mentioned the no save/restore recommendation since this is the most troublesome feature on macOS for VirtualBox.

There are a lot of crashes going on with the latest series of Macs, mostly the ones with the T2 chip. On the other hand, there are a lot of crashes going on with the latest series of OSX releases. And to top it off, there are a lot of crashes with the newly introduced vGPUs in VirtualBox. You belong in the last category with the save/restore and the VERR_PGM_HANDLER_NOT_FOUND.

Not all of them are the same...

[donealot]

@socratis - I've ended up searching these forums to see if there was any help in getting VB 6.1 to run properly on my 2018 15" MBP running 10.15.2. Long and short, I've been having random crashes of VB since the 6.x series release. After seeing all of the random issues with no known solution, I defaulted to my default fix on the Mac since I worked as a computer support technician back in days of OS 9. Long and short it work and I have a rock solid stable VB on my machine now.

What I did was reset the SMC controller (sorry I couldn't post a hyperlink but this is my first post and first day as a member) including the "If that doesn't resolve the issue, follow these steps:" part on the page. I then reset the PRAM on my system. I also changed my HD to be seen as a SSD and turned off USB 3.0 but I've since changed those settings back and all my random issues with reboots have been solved.

I think everyone should try the SMC reset and PRAM resets to see if it resolves their random reboots like it did for me.

[JiF_Brodeur]

Hi @donealot, you might have done a lot but your suggestion are along the line of killing a chicken and using snake oil. Most people on the forum have specific issues with VirtualBox only and resetting SMC and PRAM wont help much IMHO.
Thanks for the suggestion
Jean-François

[socratis]

you might have done a lot but your suggestion are along the line of killing a chicken and using snake oil

Yeah, I've seen other users doing the same thing actually. I won't be naming names...

[donealot]

@JiF_Brodeur - Just curious how resetting the SMC and PRAM are any different from the suggestions by many to reinstall and start with a clean OS? IMO it is not very different when you consider that both are addressing memory/cache issues, just on different levels. If as some have pointed out that the random crashes, which no-one has any idea of the source, is caused by with the T2 chip, then resetting then SMC/PRAM makes more sense the reinstalling the OS as those procedures might actually clear up issues emanating from the T2 chip.

In addition, Apple actually recommends resetting the SMC if, "Your Mac performs unusually slowly, even though its CPU isn't under an abnormally heavy load." My Mac was performing much slower when running VB then it should have and the issue is now resolved after resetting the SMC. The PRAM reset was just for good measure as I was having multiple hard reboots a day when trying to use VB and clearing the PRAM will, according to Apple, "and recent kernel panic information." In addition, since no-one outside of Apple has a really good idea of the internal workings of the T2 chip and they provide a specific procedure to reset it on a T2 Mac, I think it has a little more to it then snake oil and headless chickens and could actually resolve problems individuals are having with the virtualization interface.

[JiF_Brodeur]

@donealot - Hi, I understand where you are going with that suggestion but, the only problem most people in this forum have is specifically with VB, and more so, it is when staring a VM, and it started with Catalina, I think it might be macOS version related, I would not do any hardware reset of any kind to help resolved that, but that is my opinion and Thanks for jumping in, maybe it maight help who knows, this issue has been going on for months and no luck thus far.
Thanks
Jean-François

[socratis]

I would not do any hardware reset of any kind to help resolved that

A reboot and a reset never, ever hurt anyone. Au contraire!

[donealot]

@ JiF_Brodeur and @socratis - Appreciate the perspective. On my end, so far so good on my machine. No more random hard crashes when using VB 6.1 on my MacBook Pro 2018. Might be worth a try by other members to see if the SMC reset and PRAM clearing helps.

[JiF_Brodeur]

@donealot, Hi, what is your configuration(SW & HW), how often do you use VBox? I did a lot of testing and I am still hesitant to do a PRAM and SMC reset but I found a solution that worked 100% of my 20 or so reboot. Simply using graphic controller VBoxVGA and starting in headless mode then do a Show! voilà no more kernel panic on restarting a VM.
Thanks
Jean-François

[JiF_Brodeur]

@donealot @socratis Hi, I did SMC reset and PRAM clear, I then started VBox and cold boot my VM, it worked for the first 2 trials and then Kernel Panic, after yet another reboot I've test the only working solution which is to start in headless mode and it worked, so SMC reset & PRAM clear did not do it for me.
Thanks
Jean-François

[JiF_Brodeur]

HI, problem solved with VB 6.1.2, no more kernel panic with starting a VM.
Thanks to everyone who helped.
Jean-Francois