I have several VBox Guests for legacy support work with various Windows and Linux VMs.
Checking my InstallHistory.plist file, I upgraded to VBox 6.0.8 on 5/15@11:53 and all Guest VMs worked fine.

Hey guys, I just installed VirtualBox 6 (first install) to a Mac OS X 10.13.6 and tried to create my first VM using CentOS but I never got to see the mouse pointer, I did notice that when the mouse passed on top of the list boxes they showed the mouse was on top of them, but I couldn't see the mouse pointer itself, what can I do? Free for personal, educational or evaluation use under the terms of the VirtualBox Personal Use and Evaluation License on Windows, Mac OS X, Linux and Solaris x-86 platforms: Platform. For use with Version 6.1.18 only. All Platforms (Windows, Mac OS X, Solaris and Linux) 6.1.18 ExtPack.

Later the same day 5/15@16:27, the macOS 10.14.5 upgrade was offered. I reviewed the changelog and upgraded.
However, since upgrading macOS, I began seeing a fairly consistent crash when starting any VBox Guest instance.

• Creating a VirtualBox Virtual Machine for CentOS 8: Open VirtualBox and click on New. Now, type in a name for the Virtual Machine (VM), select the Type to Linux.
• Re: Trying to clone Centos guest with different MAC NOT WORK. Sep 2014, 19:44. If the MAC address shows that it has been changed in the VirtualBox config for the guest then you would see this in ifconfig on the guest. If not then there is something wrong with the guest as it.

I wasn't willing to downgrade macOS, so I ran the VirtualBox_uninstall.tool script and re-installed VBox 6.0.6.
(Yes, I first needed to apply the magic incantation 'spctl kext-consent add VB5E2TV963' in Recovery Mode).
Regrettably, VBox 6.0.6 still hard crashes on starting any Guest VM. The macOS crash log begins:

Code: Select allExpand viewCollapse view

*** Panic Report ***
panic(cpu 12 caller 0xffffff8019adb92d): Kernel trap at 0xffffffa3e1565f56, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00007fb038416000, CR3: 0x0000000860c06117, CR4: 0x00000000000226e0
RAX: 0x0000000000000000, RBX: 0x00007faff823ed44, RCX: 0x0000000000000200, RDX: 0x0000000000000319
RSP: 0xffffffa3de183c60, RBP: 0xffffffa3de183d00, RSI: 0x00007faff8218000, RDI: 0x00007fb038416000
R8: 0x00007faff823ed18, R9: 0x00007faff823ed78, R10: 0x0000000000000000, R11: 0x00007faff823ed42
R12: 0x00007faff823ed40, R13: 0x0000000000016c00, R14: 0x00007faff823ed38, R15: 0x00007faff823ed18
RFL: 0x0000000000010246, RIP: 0xffffffa3e1565f56, CS: 0x0000000000000008, SS: 0x0000000000000010
Fault CR2: 0x00007fb038416000, Error code: 0x0000000000000002, Fault CPU: 0xc, PL: 1, VF: 5
Backtrace (CPU 12), Frame : Return Address
0xffffffa3de183730 : 0xffffff80199aea2d
.
.
.
Kernel Extensions in backtrace:
org.virtualbox.kext.VBoxDrv(6.0.6)[96C33780-8C46-3129-B202-5823404C4DA0]@0xffffff7f9e338000->0xffffff7f9e427fff
BSD process name corresponding to current thread: VirtualBoxVM
Mac OS version:
18F132
Kernel version:
Darwin Kernel Version 18.6.0: Thu Apr 25 23:16:27 PDT 2019; root:xnu-4903.261.4~2/RELEASE_X86_64


I've issued crash logs via the 'Send to Apple' dialog prompt, but the VBox engineers really need to see this.
What's the suggestion here: Is there any point to further downgrading to VBox 6.0.4?

Virtualbox Centos Minimal Resize

Virtualbox Centos Copy Paste

(I can

Virtualbox Mac Download

sometimes

Centos Virtualbox Machine

get into a Guest VM without crashing, but it's not bankable)