I think there is something wrong before VM is started, because there is no new logs. The new created VM also can't be started to install os.Failed to open a session for the virtual machine ubuntu-server.
The virtual machine 'ubuntu-server' has terminated unexpectedly during startup with exit code 1 (0x1).
Result Code: NS_ERROR_FAILURE (0x80004005)
Component: MachineWrap
Interface: IMachine {85cd948e-a71f-4289-281e-0ca7ad48cd89}
[Resolved] Fail to open VM on macOS 10.14.1
-
- Posts: 3
- Joined: 4. Nov 2018, 02:22
[Resolved] Fail to open VM on macOS 10.14.1
I upgrade macOS to Version 10.14.1 from 10.13. However the Virtualbox is not matched, so I install Virtualbox with version 5.2.20 successfully. But Virtualbox can't open VMs. The Error is:
- Attachments
-
- ubuntu-server-2018-11-02-16-25-21.log.zip
- (25.42 KiB) Downloaded 50 times
Last edited by socratis on 26. Dec 2018, 17:57, edited 1 time in total.
Reason: Marked as [Resolved].
Reason: Marked as [Resolved].
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fail to open VM on macOS 10.14.1
That tells me that this is the log from 2 days ago, with VirtualBox 5.1.18, and OSX 10.13.x, i.e. not a new log. Fine, wasn't really needed. You said you updated VirtualBox. Did you get any errors during the update? In any event, try this again...VirtualBox VM 5.1.18 r114002 darwin.amd64 (Mar 15 2017 16:25:52) release log 00:00:01.373316 Log opened 2018-11-02T02:36:49.048068000Z 00:00:01.373348 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.
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.
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.
-
- Posts: 3
- Joined: 4. Nov 2018, 02:22
Re: Fail to open VM on macOS 10.14.1
As I finished the steps, I got some crash log about virtualbox. These logs may be helpful to figure out what happened.
- Attachments
-
- 安装器日志 4-Nov-2018.txt.zip
- (3.5 KiB) Downloaded 31 times
-
- crash.txt.zip
- (15.85 KiB) Downloaded 38 times
-
- Posts: 3
- Joined: 4. Nov 2018, 02:22
Re: Fail to open VM on macOS 10.14.1
I can open VM after I update security software of symantec. Virtualbox 6.0 works fine to me. Thanks a lot.
-
- Site Moderator
- Posts: 27329
- Joined: 22. Oct 2010, 11:03
- Primary OS: Mac OS X other
- VBox Version: PUEL
- Guest OSses: Win(*>98), Linux*, OSX>10.5
- Location: Greece
Re: Fail to open VM on macOS 10.14.1
Glad you got it going. Marking as [Resolved].
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.
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.