Welcome to the Linux Foundation Forum!

Vagrant Up Error on MacOS High Sierra Version 10.13.6

kriba
kriba Posts: 8
in LFD271 Class Forum - Discontinued

Hi

I am encountering an error when I run the "vagrant up" command.

Error Msg

No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
vagrant up --provider=PROVIDER, which should give you a more specific
error message for that particular provider.

Looking for help.

Comments

  • kriba
    kriba Posts: 8

    Some more info...

    Kribakarans-MBP:Downloads kribakaran.narasimhan$ vagrant box add --name fabric-fundamentals fabric-fundamentals.box
    ==> box: Box file was not detected as metadata. Adding it directly...
    ==> box: Adding box 'fabric-fundamentals' (v0) for provider:
    box: Unpacking necessary files from: file:///Users/kribakaran.narasimhan/Downloads/fabric-fundamentals.box
    The box you're attempting to add already exists. Remove it before
    adding it again or add it with the --force flag.

    Name: fabric-fundamentals
    Provider: virtualbox
    Version: 0

  • kriba
    kriba Posts: 8

    Tried...

    vagrant up --provider=PROVIDER

    Kribakarans-MBP:Downloads kribakaran.narasimhan$ vagrant up --provider virtualbox
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Importing base box 'fabric-fundamentals'...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Setting the name of the VM: Downloads_default_1536473615777_66544
    Vagrant is currently configured to create VirtualBox synced folders with
    the SharedFoldersEnableSymlinksCreate option enabled. If the Vagrant
    guest is not trusted, you may want to disable this option. For more
    information on this option, please refer to the VirtualBox manual:

    https://www.virtualbox.org/manual/ch04.html#sharedfolders

    This option can be disabled globally with an environment variable:

    VAGRANT_DISABLE_VBOXSYMLINKCREATE=1

    or on a per folder basis within the Vagrantfile:

    config.vm.synced_folder '/host/path', '/guest/path', SharedFoldersEnableSymlinksCreate: false
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    ==> default: Forwarding ports...
    default: 3000 (guest) => 3000 (host) (adapter 1)
    default: 3333 (guest) => 3333 (host) (adapter 1)
    default: 8080 (guest) => 8080 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
    ==> default: Running 'pre-boot' VM customizations...
    ==> default: Booting VM...
    There was an error while executing VBoxManage, a CLI used by Vagrant
    for controlling VirtualBox. The command and stderr is shown below.

    Command: ["startvm", "67ab6027-1b03-4ee7-9c55-9786f9e97dde", "--type", "headless"]

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

  • JonathanLevi
    JonathanLevi Posts: 26
    edited September 2018

    Hi @kriba
    Jonathan Levi from HACERA here.

    First question:
    The provider is 'virtualbox' indeed.

    Second question:
    Have you tried to "vagrant destroy" and then to "vagrant up" (that's regarding the "The box you're attempting to add already exists. Remove it before")

    Third question: (in case 2 didn't end up with a successful boot):

    But if you could provide us with some more information/diagnostics, such as your operating system (type and version), the version of vagrant used, etc... it may shed some more light.

    Hard to tell when there is no error message - but let's go for it and dig in.

    Thanks, Jonathan

  • kriba
    kriba Posts: 8

    Thanks, Jonathan for the response.

    I tried vagrant destroy and vagrant up.

    Here is the output after I destroyed vagrant.

    Kribakarans-MBP:Downloads kribakaran.narasimhan$ vagrant destroy
    default: Are you sure you want to destroy the 'default' VM? [y/N] y
    ==> default: Destroying VM and associated drives...
    Kribakarans-MBP:Downloads kribakaran.narasimhan$ vagrant up
    Bringing machine 'default' up with 'virtualbox' provider...
    ==> default: Importing base box 'fabric-fundamentals'...
    ==> default: Matching MAC address for NAT networking...
    ==> default: Setting the name of the VM: Downloads_default_1537685446996_44704
    ==> default: Fixed port collision for 8080 => 8080. Now on port 2200.
    ==> default: Clearing any previously set network interfaces...
    ==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
    ==> default: Forwarding ports...
    default: 3000 (guest) => 3000 (host) (adapter 1)
    default: 3333 (guest) => 3333 (host) (adapter 1)
    default: 8080 (guest) => 2200 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
    ==> default: Running 'pre-boot' VM customizations...
    ==> default: Booting VM...
    There was an error while executing VBoxManage, a CLI used by Vagrant
    for controlling VirtualBox. The command and stderr is shown below.

    Command: ["startvm", "4a9200c0-a4dc-4c21-b2d6-2546b52e41c1", "--type", "headless"]

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

    Hope this helps in identifying the issue.

  • JonathanLevi
    JonathanLevi Posts: 26
    edited September 2018

    Thank you @kriba,

    Interesting. So they report back that "The virtual machine has terminated unexpectedly during startup..." and that's all !? Nice ;-)

    OK, let me see if we can reproduce it. We have some MacOS Sierras here.
    What version of Vagrant are you running?

    Thanks again, Jonathan

  • kriba
    kriba Posts: 8

    Vagrant version 2.1.4

  • JonathanLevi
    JonathanLevi Posts: 26

    Sorry, we can't reproduce this. What Virtual box version are you using?

    The only thing we saw with a similar "error" was with an older version of Virtual Box.

    Please let us know and we'll try to replicate your exact set up on Mac.

Categories

Upcoming Training