After upgrade mac Mojave, I also upgrade virtualbox from 5.1.18 to lastest version 5.2.20, because the old version can't use anymore
when I boot the vm, show error log
The virtual machine 'Samsung Galaxy S9 - 8.0 - API 26 - 1440x2960' has terminated unexpectedly during startup with exit code 1 (0x1).
Please provide a VM log file. With the VM fully shut down, right click it in the GUI. Select "Show Log" and save "VBox.log" (no other file) to a zip file. Attach the zip here.
00:00:00.080970 File system of '/Users/daniel.yp/.Genymobile/Genymotion/deployed/
Samsung Galaxy S9 - 8.0 - API 26 - 1440x2960/Snapshots/{a12908a4-967e-497f-8db0-32f480cf8e3e}.vmdk' is unknown
Genymotion is a program that relies on VirtualBox, but modifies its configuration files in unknown ways to us, and with unknown consequences. It is not supported on these VirtualBox user forums, they have their own Genymotion support channels. If you are having this problem with a standalone version of VirtualBox (after a complete uninstallation of Genymotion), then we can continue this discussion.
And on top of that, Android guests are not officially supported...
Moving to "Other Guests" from "OSX Hosts".
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.
well I uninstall the genymotion
I confirm genymotion is not the reason, because It show error before I install genymotion
so I create new VM ant boot it
error log is the same
The virtual machine 'win10' has terminated unexpectedly during startup with exit code 1 (0x1).
Is that all the error you get? And no logs? How then did you manage to get the log for the Samsung VM?
In any event, try with the latest VirtualBox, since you're at 5.1.18 with OSX 10.13.x:
VirtualBox VM 5.1.18 r114002 darwin.amd64 (Mar 15 2017 16:25:52) release log
00:00:00.023809 OS Version: Darwin Kernel Version 17.7.0: Thu Jun 21 22:53:14 PDT 2018; root:xnu-4570.71.2~1/RELEASE_X86_64
You might want to print the following steps, or save them in a test file on your desktop, because there are a couple of reboots, and you don't want to go "hunting" in the forums...
Download the latest release, or the latest test build (NOT the development snapshot), if you don't already have them.
Reboot.
Make sure you're part of the "admin" group. If you are logged in with the primary user account/owner, you are part of the admin group.
Mount the DMG from the previous step. Run "VirtualBox_Uninstall.tool". Make sure there are no error messages. If there are, please post them, exactly as they appear.
Reboot.
Mount the DMG from the previous steps. Double-click the "VirtualBox.pkg". As soon as you start the installation, press Cmd+L to show the log. Select "Show All Logs" from the drop-down menu. Before the last step of the installation (Done), click the "Save" in the log window. ZIP and attach that file.
Start VirtualBox. If it crashes, open "Console.app" and look at "~/Library/Logs". Is there a VirtualBox related log with the current date/time? ZIP and attach that file as well.
After all, I start to believe that this is indeed an "OSX Hosts" issue, moving it.
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.
Did you read the 2nd part of the message? About re-installing VirtualBox and grabbing some logs? Please re-read it...
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.
Thank you
I tried to follow your steps and got the log of step 6.
There is no related log in ~/Library/Logs
Start vm error, the log in the application is empty
