Hello, my problem is solved. i think it caused by my virtualbox version.
I'have installed latest version and my vagrant up command go to the end.
Thanks for your help.
Schad
2014-10-07 23:34 GMT+00:00 Alvaro Miranda Aguilera kiki...@gmail.com:
after you do vagrant up, can you
vagrant ssh
that is the latest error message :
Vagrant::Errors::VBoxManageError: There was an error while executing
`VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: [modifyvm, cc78133c-e489-4682-9f93-1d6127a1be6b, --natpf1,
Hi Alvaro,
thx a lot for your replay. But i've changed all 3 different paths, like
described:
1. Vagrant Project: This is on my external disk. But it includes a
folder .vagrant that has some michine-ids in it, maybe this is the problem
2. VAGRANT_HOME: The Path is changed to my
Thanks a lot for the response, Alvaro,
Let me throw a couple things at you:
I normally do all my work in a Linux VirtualBox guest within my
(company-supplied) Windows host. I'd prefer to have a Linux host, but it is
what it is.
I needed to create a consistent development environment to share
Hi Jamie,
sounds familiar.
You might also be interested in:
https://github.com/fgrehm/vagrant-lxc which is conceptually more similar to
your original approach with nested VMs
https://github.com/tknerr/bills-kitchen which shows another approach on how
you can bundle development environment for
Hi Chris,
finally I got it working, it even survives a `vagrant reload` now ;-)
See here for Vagrantfile (and comments for further description)
https://gist.github.com/tknerr/b5ecc3d809fce8f22cbex
HTH,
Torben
On Wed, Sep 24, 2014 at 6:13 AM, Chris Johnson wchrisjohn...@gmail.com wrote:
