Issues installing vagrant on high sierra

Discussions related to using VirtualBox on Mac OS X hosts.
Post Reply
jeffsikala
Posts: 1
Joined: 18. Oct 2018, 19:19

Issues installing vagrant on high sierra

Post by jeffsikala »

I'm currently running vargant version 2.1.5 on my mac high sierra 10.13.6

So after completing the vagrant init and vagrant up command I'm suppose to have a fully running virtual machine in virtualbox. But after running vagrant up I get this instead.

`There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.

Command: ["startvm", "3574f45d-aade-4053-af8b-0c88330e855f", "--type", "headless"]

Stderr: VBoxManage: error: The virtual machine 'saltstates_default_1539870640620_6152' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine`

Any idea what this is about?
socratis
Site Moderator
Posts: 27329
Joined: 22. Oct 2010, 11:03
Primary OS: Mac OS X other
VBox Version: VirtualBox+Oracle ExtPack
Guest OSses: Win(*>98), Linux*, OSX>10.5
Location: Greece

Re: Issues installing vagrant on high sierra

Post by socratis »

Vagrant is a program that relies on VirtualBox but modifies its configuration files in unknown ways to us. It is not supported on these VirtualBox user forums, they have their own Vagrant support channels. If you are having this problem with a standalone version of VirtualBox (after a complete uninstallation of Vagrant), then we can continue this discussion.
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.
Post Reply