A couple of days ago all was working fine on my macOS 10.15.5 with VirtualBox 6.0.20.
I have Windows10 and Ubuntu. Today I needed Windows and when started I got the Windows 'blue' screen saying that some critical system files were not found and it tried to repair itself, for no avail.
Download macOS Catalina ISO. You’ve to download macOS Catalina ISO from the link provided. In my own experience. Best fix is to delete it and don't use it. A mac will run windows and linux fine if used in an external USB, or bootcamp will assist with a permanent install of windows. Not sure the scope of use with VM needs but I hope this helps.
Then I tried Ubuntu, which simply didn't start and its status turned to 'Aborted'
I have managed to install macOS Catalina 10.15.5 from an ISO created from the vanilla MacStore downloaded App on Virtualbox following GeekRars excellent tutorials with a few minor tweaks. CPU AMD Ryzen 9 3900X 12-Core Processor. M/B ASUSTeK TUF GAMING X570-PLUS. O/S Windows 10 Pro 64-bit. V/B Virtualbox 6.1.10 + Extentions. I am unable to install virtualbox on macOS Catalina. Tried both the GUI installer and Homebrew. Here's what happens if I try to create a VM even after the failed installation: macos catalina virtualbox. Restart your mac in Recovery mode (cmd + R) Then open a. Virtualbox vm quit unexpectedly. Steps to Reproduce: Run VM. Keep VM window focused. Lock computer using key-shortcut Control +Command +Q. Result: VM crashes with below MAC error log. Logs: Process: VirtualBoxVM 22199 Path: /Applications/VirtualBox.app/Contents/Resources/VirtualBoxVM.app/Contents/MacOS/VirtualBoxVM.
Making a long story short. I did a clean install of VirtualBox 6.1.10, used new and backed up VDI files for Windows and Linux. Created new VM re-using my VDI disks and tested, trying to look at the logs.
It simply getting aborted whatever I try. I have no idea of what's going on. Looking at my log at
- Code: Select allExpand viewCollapse view
~/VirtualBox VMs/Ubuntu_old/Logs/VBox.log
- Code: Select allExpand viewCollapse view
...
00:00:01.897119 Firmware type: failed - VERR_NOT_SUPPORTED
...
# the end of my log
00:00:02.211154 VMMDev: Guest Log: BIOS: AHCI 0-P#0: PCHS=16383/16/63 LCHS=1024/255/63 0x0000000001000000 sectors
00:00:02.212571 PIT: mode=2 count=0x48d3 (18643) - 64.00 Hz (ch=0)
00:00:02.229405 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000116cf5000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
00:00:02.692486 GUI: UIMachineViewNormal::resendSizeHint: Restoring guest size-hint for screen 0 to 800x600
00:00:02.700394 GUI: 2D video acceleration is disabled
00:00:02.700470 GUI: HID LEDs sync is enabled
00:00:02.738224 GUI: UIMachineLogicNormal::sltCheckForRequestedVisualStateType: Requested-state=0, Machine-state=5
00:00:04.694171 PIT: mode=2 count=0x10000 (65536) - 18.20 Hz (ch=0)
00:00:04.695038 VMMDev: Guest Log: BIOS: Boot : bseqnr=1, bootseq=0231
00:00:04.695713 VMMDev: Guest Log: BIOS: Boot from Floppy 0 failed
00:00:04.696378 VMMDev: Guest Log: BIOS: Boot : bseqnr=2, bootseq=0023
00:00:04.697268 VMMDev: Guest Log: BIOS: CDROM boot failure code : 0003
00:00:04.697644 VMMDev: Guest Log: BIOS: Boot from CD-ROM failed
00:00:04.698085 VMMDev: Guest Log: BIOS: Boot : bseqnr=3, bootseq=0002
00:00:04.698938 VMMDev: Guest Log: BIOS: Booting from Hard Disk...
00:00:04.749144 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000000000000 w=720 h=400 bpp=0 cbLine=0x0 flags=0x0 origin=0,0
00:00:05.353478 Display::i_handleDisplayResize: uScreenId=0 pvVRAM=0000000116e21000 w=640 h=480 bpp=32 cbLine=0xA00 flags=0x0 origin=0,0
I can run Ubuntu memory test from the Grub option and starting the VM in headless mode the status shows 'running' and that's all.
I hope someone can help me somehow.
Virtualbox Vm Quit Unexpectedly Mac Catalina Free
Thanks in advance,Alan
Can't Install Virtualbox On Mac Catalina
Whether you’re setting up a fresh Linux VM in VirtualBox on macOS Catalina (10.15.6), or migrating a VM over from an older macOS version, you can be in for a nasty surprise — once the VM boots, VirtualBox crashes with a mere stack trace.
Personally I tested this with openSUSE, but since there’s similar reports from Ubuntu, this seems a fairly common problem.
The error and the stack trace will look something along these lines:
The solution is simple, yet all the more annoying: disable audio in the VM settings.
At a guess, one of the many new security limitations in Catalina is denying VirtualBox permissions and the latter does’t know what to do besides throwing a fit.
Comments are closed.