You signed in with another tab or window.
Reload
to refresh your session.
You signed out in another tab or window.
Reload
to refresh your session.
You switched accounts on another tab or window.
Reload
to refresh your session.
By clicking “Sign up for GitHub”, you agree to our
terms of service
and
privacy statement
. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
The virtual machine 'test_default_1466505567911_94122' has terminated unexpectedly during startup with exit code 1 (0x1)
#7507
The virtual machine 'test_default_1466505567911_94122' has terminated unexpectedly during startup with exit code 1 (0x1)
irvifa
opened this issue
Jun 21, 2016
· 7 comments
# vi: set ft=ruby :
# All Vagrant configuration is done below. The "2" in Vagrant.configure
# configures the configuration version (we support older styles for
# backwards compatibility). Please don't change it unless you know what
# you're doing.
Vagrant
.
configure
(
"2"
)
do
|
config
|
# The most common configuration options are documented and commented below.
# For a complete reference, please see the online documentation at
# https://docs.vagrantup.com.
# Every Vagrant development environment requires a box. You can search for
# boxes at https://atlas.hashicorp.com/search.
config
.
vm
.
box
=
"hashicorp/precise64"
# Disable automatic box update checking. If you disable this, then
# boxes will only be checked for updates when the user runs
# `vagrant box outdated`. This is not recommended.
# config.vm.box_check_update = false
# Create a forwarded port mapping which allows access to a specific port
# within the machine from a port on the host machine. In the example below,
# accessing "localhost:8080" will access port 80 on the guest machine.
# config.vm.network "forwarded_port", guest: 80, host: 8080
# Create a private network, which allows host-only access to the machine
# using a specific IP.
# config.vm.network "private_network", ip: "192.168.33.10"
# Create a public network, which generally matched to bridged network.
# Bridged networks make the machine appear as another physical device on
# your network.
# config.vm.network "public_network"
# Share an additional folder to the guest VM. The first argument is
# the path on the host to the actual folder. The second argument is
# the path on the guest to mount the folder. And the optional third
# argument is a set of non-required options.
# config.vm.synced_folder "../data", "/vagrant_data"
# Provider-specific configuration so you can fine-tune various
# backing providers for Vagrant. These expose provider-specific options.
# Example for VirtualBox:
# config.vm.provider "virtualbox" do |vb|
# # Display the VirtualBox GUI when booting the machine
# vb.gui = true
# # Customize the amount of memory on the VM:
# vb.memory = "1024"
# end
# View the documentation for the provider you are using for more
# information on available options.
# Define a Vagrant Push strategy for pushing to Atlas. Other push strategies
# such as FTP and Heroku are also available. See the documentation at
# https://docs.vagrantup.com/v2/push/atlas.html for more information.
# config.push.define "atlas" do |push|
# push.app = "YOUR_ATLAS_USERNAME/YOUR_APPLICATION_NAME"
# end
# Enable provisioning with a shell script. Additional provisioners such as
# Puppet, Chef, Ansible, Salt, and Docker are also available. Please see the
# documentation for more information about their specific syntax and use.
# config.vm.provision "shell", inline: <<-SHELL
# apt-get update
# apt-get install -y apache2
# SHELL
Debug output
irvi@irvi-test:~/Vagrant/test$ vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Importing base box 'hashicorp/precise64'...
==> default: Matching MAC address for NAT networking...
==> default: Checking if box 'hashicorp/precise64' is up to date...
==> default: Setting the name of the VM: test_default_1466505567911_94122
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> 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", "945f1854-3311-433e-a1e4-1ee1b7b07600", "--type", "headless"]
Stderr: VBoxManage: error: The virtual machine 'test_default_1466505567911_94122' has terminated unexpectedly during startup with exit code 1 (0x1)
VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component MachineWrap, interface IMachine
It looks like this is a bug in Virtualbox:
http://askubuntu.com/questions/122211/getting-error-message-when-trying-to-start-a-virtual-machine
You can follow the steps there to a solution. Thanks! 😄
I face this error after updating kernel on my fedora 25 desktop. Here is the solution which vagrant itself suggest for that:
sudo dnf install akmod-VirtualBox kernel-devel-4.12.11-200.fc25.x86_64
sudo akmods --kernels 4.12.11-200.fc25.x86_64 && systemctl restart systemd-modules-load.service
For Windows users: on Windows 10, I installed everything as
ADMINISTRATOR
and only the following configuration worked for me:
Vagrant 1.9.2
:
Download Vagrant 1.9.2
Oracle VM VirtualBox 5.1.30
:
Download Oracle VM VirtualBox 5.1.30
For older versions of
VirtualBox
, the virtual machine has terminated unexpectedly.
For newer versions of
VirtualBox
, the host-only adapter cannot be created.
When you upgrade or downgrade, make sure that you
permanently delete (Shift + Delete)
the following folders from
C:\Users\your-user
:
.vagrant
,
.VirtualBox
and
Virtual VM Machines
. When using
vagrant up
, these folders will be created again.
After each program install and uninstall, make sure to restart your computer. Old files from VirtualMachine and Vagrant are persistent until the OS boots up again.
I'm going to lock this issue because it has been closed for
30 days
⏳. This helps our maintainers find and focus on the active issues.
If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.
