vagrant up but the status of the VM is "Powered Off"

[Hui Zhao]

Hi I am new to vagrant. Please see my vagrant setting up structure in Windows 7 machine.

The bootstrap.sh is

#!/usr/bin/env bash
sudo -s <<EOF
yum makecache fast
yum update -y
cp /vagrant/consul /bin
firewall-cmd --zone=public --add-port=8300/tcp --permanent
firewall-cmd --zone=public --add-port=8500/tcp --permanent
firewall-cmd --reload
consul agent -dev -ui -bind "172.28.128.3" -client "172.28.128.3"
EOF

The Vagrantfile is 

Vagrant.configure(2) do |config|
  config.vm.box = "puppetlabs/centos-7.0-64-puppet"
  config.vm.network "private_network", ip: "172.28.128.3"
  config.vm.provision :shell, path: "bootstrap.sh"
end

Then I run the command "vagrant up"

But when I open the VirtualBox. The status is "Powered Off". 

Why?

[Alvaro Miranda Aguilera]

Hello,

so you are running this locally on your windows machine.

Can you share the following output

vagrant version

vagrant plugin list

vagrant status

vagrant halt

vagrant up

VBoxManage list vms

Thanks

alvaro.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/6463ed98-acaa-4424-a150-ad1c287e3fbb%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Hui Zhao]

The question is right now it is running after a few times deletion VM and installation. Not sure why it was not working. 

vagrant version: 1.8.1

vagrant plugin list: vagrant-share(1.1.5, system)

You received this message because you are subscribed to a topic in the Google Groups "Vagrant" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/vagrant-up/XUG8eXbhaKU/unsubscribe.
To unsubscribe from this group and all its topics, send an email to vagrant-up+...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0eze2r%2BR0oa8TRpX83oVTmMovYbiEXKOR8HL3Te2U4t9BA%40mail.gmail.com.

[dragon788]

Occasionally if the VM fails to boot Vagrant can be left in a bad state and leave a "lock" file behind that makes it think that the VM is running.

[Anthony M]

I recently saw similar behavious under Windows 10 using Vagrant and VirtualBox.  It turned out to be caused by VirtualBox not running as administrator.  If this is the cause of the problem then right clicking (perhaps with shift held down) on the VirtualBox icon should give you the option to run as administrator.