I have Vagrant 1.4.3, VMWare Fusion plugin 2.3.0, VMWare Fusion 6, OS X
10.9.1. When running 'vagrant up', Vagrant sometimes waits forever for the
VM to boot, even though it's actually up. I cannot always reproduce this
problem: sometimes it works, and sometimes it doesn't work. When it
Hello Hongli,
Have you tried adding vm.gui = true?
I often have issues with boxes that were created with an older version
of Workstation/Fusion, and upon startup Fusion asks you if you'd like to
upgrade the hardware config to the current version. This stops the
system from booting at all
On Tue, Feb 11, 2014 at 5:34 PM, Will Froning will.fron...@gmail.com wrote:
Hello Hongli,
Have you tried adding vm.gui = true?
Is it already running with vm.gui = true. I confirm in the GUI that
the VM boots properly and has a network connection.
--
Phusion | Ruby Rails deployment, scaling
what the guest os?
can you share a gist with
vagrantfile
ifconfig -a
cat /etc/sysconfig/network-scripts/ifcfg-eth*
Alvaro.
On Wed, Feb 12, 2014 at 1:33 AM, Hongli Lai hongli...@gmail.com wrote:
I've tried deleting all leases files in /var/db/vmware. I then stopped
VMWare Fusion, and re-ran
Hi Jaace,
have you tried `config.vbguest.auto_update = false`?
You can also build your own basebox with the correct guest additions being
already installed, bento might help you with that:
https://github.com/opscode/bento
HTH, Torben
--
You received this message because you are subscribed to
Every now and again I see a problem where the Vagrant box is built but if I
try Vagrant up or Vagrant ssh I get VM not created or it starts building
the box (and failing as A VirtualBox machine with the name '[whatever]'
already exists.). The underlying Vagrant files are not changing, although
Had the same problem , just ran vagrant reload and all fixed.
Hope it helps.
On Friday, September 23, 2011 2:54:25 AM UTC-7, prof3ta wrote:
Hi,
I have a simple Vagrantfile which uses a lucid32 box.
I'm using Snow Leopard and vagrant version 0.8.7.
When I try to launch the box, I get:
Hi,
tl;dr: on my Win7 box Vagrant doesn't get the output of the VBoxManage
command, so breaks completely.
I installed Ruby 1.9.3, Vagrant 1.4.3 and VirtualBox 4.3.6-91406 on my
Win7-64bit computer.
VirtualBox works perfectly, and vagrant init properly creates a
VagrantFile.
But when I ran
There is a .vagrant folder in the directory that you are using, and it
contains an ID to a virtual machine. if something / something else is
modifying that file outside of vagrant the behavior you are seeing can
happen.
On Tue, Feb 11, 2014 at 4:32 PM, Dave Lowndes d...@room9.co.nz wrote:
