I recently (today) updated my Virtualbox and vagrant installs to the latest versions. When I got to boot a current project this happens. I destroyed my old vagrant box that the project was created with, and created a new one as a test, but I still get the same error.
Error that comes to screen after "vagrant up"
There was an error while executing VBoxManage, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "007ab888-e415-4f3a-9a4a-3682504c718a", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'Projects_default_1514560086822_51787' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\my.name\VirtualBox VMs\Projects_default_1514560086822_51787\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Vagrant version
2.0.1
Virtualbox version
5.2.4
Host operating system
Windows 10
Guest operating system
CentOS7.2
Vagrantfile
$set_environment_variables = <<SCRIPT
tee "/etc/profile.d/myvars.sh" > "/dev/null" <<EOF
# required environment variables.
export ELASTIC_USER=xxxxxxxxxx
export ELASTIC_PASS=xxxxxxxxxx
export NODE_TLS_REJECT_UNAUTHORIZED=0
export SNOW_USER=xxxxxxxxxx
export SNOW_PASS=xxxxxxxxx
EOF
SCRIPT
Vagrant.configure("2") do |config|
# avoid self signed SSL issues
config.vm.box_download_insecure = true
#config.vm.network "forwarded_port", guest:80, host:8080, host_ip: "127.0.0.1"
config.vm.network "forwarded_port", guest:9000, host:9000, host_ip: "127.0.0.1" # node
config.vm.network "forwarded_port", guest:9014, host:9014, host_ip: "127.0.0.1" # node
#config.vm.network "forwarded_port", guest:3000, host:3000, host_ip: "127.0.0.1" # grafana
config.vm.network "forwarded_port", guest:9200, host:9200, host_ip: "127.0.0.1" # elastic
config.vm.network "forwarded_port", guest:5601, host:5601, host_ip: "127.0.0.1" # kibana
# pull the Vagrant box
config.vm.box="DockerNodeElastic 1.0.6"
config.vm.box_url="CentOS-72-Elastic-Node-Docker-1.0.6.box"
config.ssh.username="vagrant"
config.ssh.password="vagrant"
config.vm.synced_folder ".", "/vagrant",
:mount_options => ["dmode=777", "fmode=777"]
# optional
config.vm.provider "virtualbox" do |v|
v.memory=1024
end
config.vm.provision "shell", inline: $set_environment_variables, run: "always"
end
Debug output
https://gist.github.com/YeeP79/f05958c705748b1c431e04c65b569f2a
VBoxHardening.log
https://gist.github.com/YeeP79/4d794d987b2db57f54aec99c25f95c0c
Expected behavior
vagrant machine should have booted up
Actual behavior
Stuck in starting
I recently (today) updated my Virtualbox and vagrant installs to the latest versions. When I got to boot a current project this happens. I destroyed my old vagrant box that the project was created with, and created a new one as a test, but I still get the same error.
Error that comes to screen after "vagrant up"
There was an error while executing
VBoxManage, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "007ab888-e415-4f3a-9a4a-3682504c718a", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'Projects_default_1514560086822_51787' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\my.name\VirtualBox VMs\Projects_default_1514560086822_51787\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
Vagrant version
2.0.1
Virtualbox version
5.2.4
Host operating system
Windows 10
Guest operating system
CentOS7.2
Vagrantfile
Debug output
https://gist.github.com/YeeP79/f05958c705748b1c431e04c65b569f2a
VBoxHardening.log
https://gist.github.com/YeeP79/4d794d987b2db57f54aec99c25f95c0c
Expected behavior
vagrant machine should have booted up
Actual behavior
Stuck in starting