I can watch the guest begin to boot in the console window. Right about the time the login prompt appears, the whole system goes black and reboots. Seems to happen every time - I've only done it twice since I don't enjoy having to restart everything I had running, but it did exactly the same thing both times. The MacOS crash log is attached. Here's the kexstat output:
Do you have the VBox.log from the last crash? ZIP it and attach it.
Does it happen only with that guest?
What's installed on your Mac that's not native?
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
1. Are there known issues with Avira? I would rather not remove it...
2. Attached
3. This is the only guest I have created on this machine so far
4. Sorry, not sure what you mean by "not native". Non-Apple software?
You're the first that I remember of that has Avira on OSX. I don't really like the kext "com.avira.kext.FileAccessControl", something doesn't feel/sound right about it.
VBox.log: see below for the analysis.
If this is the only guest, I'm going to change the title of the thread from "Mac crashes and reboots when I start a particular CentOS guest", because it implies a completely different situation.
Non-Apple software, especially software that needs an administrator account to be installed, software that's system-wide modifying. Like your Avira for example. Please post the output of the commands:
ls -ald /Applications/*/*
ls -al /Library/Extensions/
From your VBox.log:
00:00:01.383154 [/Devices/usb-ehci/] (level 2)
Not an earth shuttering change, but you could benefit if you're using USB3.
Go to the VM Settings » Display » Screen. Change the Graphics controller from "VMSVGA" to "VBoxVGA". Enable 3D acceleration. Increase the VRAM to the max 128 MB. Again, I don't expect this to make a difference in your crash.
Finally, can you try another client? Just booting from a LiveDVD should suffice. My preferred "stable" client is Mint 19. Download the ISO, create a new VM, boot from that. See if that crashes your host or not.
Do NOT send me Personal Messages (PMs) for troubleshooting, they are simply deleted.
Do NOT reply with the "QUOTE" button, please use the "POST REPLY", at the bottom of the form.
If you obfuscate any information requested, I will obfuscate my response. These are virtual UUIDs, not real ones.
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: 0x000000000a000000
Kernel text base: 0xffffff800a200000
__HIB text base: 0xffffff800a100000
System model name: MacBookPro16,1 (Mac-E1008331FDC96864)
System shutdown begun: NO