Trying to package a Windows 12 guest. Running Vagrant 1.7.4 and Virtualbox
5.0.10. The package process hangs after the following debug output:
INFO subprocess: Starting process: ["/usr/local/bin/VBoxManage", "export",
"cf55be88-0314-4118-9d5d-f1fbff91f108", "--output",
doesn't exist
create it as fixed size
change it to shareable
end
attach disk to vm
The gist have a loop, so you can define by code size, number, path
hope this helps
Alvaro.
On Sat, Jun 20, 2015 at 6:51 AM, Jeff Sussna j...@ingineering.it
javascript: wrote:
I'm trying
Have a Vagrantfile with a chef-solo provisioner and a few cookbooks.
'vagrant up' and 'vagrant provision' work fine. However, after 'vagrant
reload' the cookbooks appear to have been deleted from the guest. On a
Centos guest, /tmp/vagrant-chef/.../cookbooks directory on the guest is
empty. On
That worked. Thanks. This seems like a pretty major Vagrant bug.
On Tuesday, May 12, 2015 at 4:34:29 PM UTC-5, Torben Knerr wrote:
Hi Jeff,
you might be running into this:
https https://github.com/mitchellh/vagrant/issues/5199://
https://github.com/mitchellh/vagrant/issues/5199github.com
Makes no difference. Torben's workaround, though, does.
On Tuesday, May 12, 2015 at 5:11:47 PM UTC-5, Alvaro Miranda Aguilera wrote:
Can you test
vagrant reload --provision
On Wed, May 13, 2015 at 7:52 AM, Jeff Sussna j...@ingineering.it
javascript: wrote:
Have a Vagrantfile
Because…trust me, you don't want to know :-)
On Monday, May 19, 2014 7:27:07 PM UTC-5, Alvaro Miranda Aguilera wrote:
On Tue, May 20, 2014 at 9:51 AM, Jeff Sussna j...@ingineering.itjavascript:
wrote:
n top of a Linux VM.
I am lost on that part, Why it has to run on top of a linux vm
Was all set to use Packer to build myself a Windows guest Vagrant box for
Virtualbox. Then realized it has to run on top of a Linux VM. AFAIK
Virtualbox can't run on top of another virtualization layer. Is there any
hope for me?
--
You received this message because you are subscribed to the
Vagrant global-control functions work fine as long as I'm in the directory
with the Vagrantfile. From other directories they all return the following
error:
/Applications/Vagrant/embedded/gems/gems/vagrant-1.6.0/lib/vagrant/environment.rb:194:in
`active_machines': undefined method `join' for
Experimenting with the beta of Private Vagrant Cloud. Dumb question: how do
you tell vagrant where to look to find your private Vagrant Cloud server? I
can't find any mention of it in the docs.
--
You received this message because you are subscribed to the Google Groups
Vagrant group.
To
OK, I'm back. Doing something that needs the vagrant-omnibus plugin. It
introduces a multi-minute delay to every vagrant command.
On Tuesday, April 15, 2014 1:01:42 PM UTC-5, Jeff Sussna wrote:
And the moron award for the day goes to…me! 'vagrant plugin uninstall
vagrant-omnibus
lines? Or is
it all generally slow? etc.
Best,
Mitchell
On Tue, Apr 15, 2014 at 10:38 AM, Jeff Sussna
j...@ingineering.itjavascript:
wrote:
Out of nowhere, vagrant provision has suddenly become dog slow to start.
Running Vagrant 1.4.3/Virtualbox 4.2.18/OSX Mavericks 10.9.2. Had
11 matches
Mail list logo
