Here are both, the vagrantfile contents and the stdout and stderr
Here is the vagranfile
# -*- mode: ruby -*-
# vi: set ft=ruby :
vmName = 'example500'
vmHost = 'example500'
Vagrant.configure(2) do |config|
config.vm.box = "centos7.1"
# config.vm.network "forwarded_port", guest: 80, host: 8080
# config.vm.network "private_network", ip: "192.168.33.10"
# config.vm.network "public_network"
config.vm.network "public_network", bridge: "en0"
# config.vm.network "public_network", bridge: "Intel(R) Centrino(R)
Advanced-N 6235", adapter: "1"
# config.vm.synced_folder "../data", "/vagrant_data"
config.vm.hostname = vmName
config.vm.provider "virtualbox" do |vb|
# Display the VirtualBox GUI when booting the machine
vb.gui = true
vb.name = vmName
# Customize the amount of memory on the VM:
vb.customize ["modifyvm", :id, "--clipboard", "bidirectional"]
vb.customize ["modifyvm", :id, "--draganddrop", "bidirectional"]
vb.memory = "4094"
end
# config.vm.provision "shell", inline: <<-SHELL
# sudo apt-get update
# sudo apt-get install -y apache2
# SHELL
end
#vagrant init hashicorp/precision64
Here is the stdout and stderr
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Fixed port collision for 22 => 2222. Now on port 2200.
==> default: Clearing any previously set network interfaces...
==> default: Specific bridge 'en0' not found. You may be asked to specify
==> default: which network to bridge to.
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
default: Adapter 2: bridged
==> default: Forwarding ports...
default: 22 => 2200 (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
On Saturday, December 5, 2015 at 2:53:09 AM UTC-5, Alvaro Miranda Aguilera
wrote:
>
> Have you check ram utilzation?
>
> sum all the ram you are using in VM and try to leave 2GB for the host.
>
> If you gave 8GB ram, just use max 6GB for guest, that is 3 guest of 2GB
> each one.
>
> 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 [email protected].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/5319015b-2416-4eeb-bec3-6499930660b4%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
