Blake,
The code for it is actually already in the plugin, but it isn't exposed
publicly yet. The reason is mostly due to a missing feature in Vagrant core
that I plan on implementing soon. The urgency though is simply not high
for me because linked clones don't actually buy you a lot with
John,
You may want to see this CentOS Packer template here:
https://github.com/mitchellh/packer-templates/tree/master/centos-6.5-x86_64
I don't want to overload you with too many things, but running packer
build virtualbox.json on that generates a completely valid CentOS image
for Vagrant (but
You're missing a significant portion of the debug log making this
relatively useless. Please upload the full thing and I'll take a look. Gist
it, because it'll be large.
On Mon, Jan 20, 2014 at 6:55 AM, Stephan Buys stephan.b...@gmail.comwrote:
Hi,
When trying to boot a VMWare Fusion (and
Stephan,
There isn't one for VMware but here is the Vagrant CHANGELOG:
https://github.com/mitchellh/vagrant/blob/master/CHANGELOG.md
We're hoping to add a VMware changelog soon!
Best,
Mitchell
On Mon, Jan 20, 2014 at 12:11 AM, Stephan Buys stephan.b...@gmail.comwrote:
Hi all,
I must
Jaco,
Try running the given commands manually within the VM. Sometimes the VM
gives you more detailed errors (although Vagrant usually outputs them).
Make sure the VirtualBox guest addition kernel modules are loaded in the VM
as well.
best,
Mitchell
On Fri, Jan 31, 2014 at 8:03 AM, Jaco du
Michael,
I'm not sure how your old VM worked but the reason the new one isn't
working is probably because you need to configure the OS too. I apologize
if you know this already, but it is very relevant if you don't: simply
adding a network adapter won't cause the OS to magically configure it
Mats,
I'm sorry you had trouble finding information. But if you click one of the
biggest call to actions on the home page: Getting Started, it has a Why
Vagrant sentence in the second sentence. I'm not sure how much easier it
can get than that!
Otherwise, if you feel you can make it better, the
Hi! Can you set VAGRANT_LOG=debug and get that output? This is definitely
not working as intended!
Best,
Mitchell
On Sun, Feb 2, 2014 at 7:44 PM, Arrivance cmpl...@gmail.com wrote:
Alright, so I downloaded Vagrant, in the attempt to create a dev
environment for something I'm working on.
Raphael,
Not currently [easily]. In the next version of Vagrant (1.5), Vagrant has
an 'rsync' synced folder mechanism that can do this for you, however.
best,
Mitchell
On Sun, Feb 2, 2014 at 10:15 PM, Raphael Cruzeiro
raphaelcruze...@raphaelcruzeiro.com wrote:
When I am setting up an
Robin,
NFS is the best approach right now. In the next version of Vagrant, rsync
synced folders will be available .This will allow Vagrant to use rsync to
send folders to the guest, allowing the native guest filesystem to be used.
You can see here that the native VM filesystem performance is very
Owain,
You might want to reach out and ping the vagrant-windows folks directly, as
well. The best way to do this is probably via the issues on the repo.
Best,
mitchell
On Tue, Feb 4, 2014 at 1:19 AM, Owain Perry owain.pe...@gmail.com wrote:
Hi,
I am having issues with port forward
:06 PM, Arrivance cmpl...@gmail.com wrote:
On Sunday, February 2, 2014 6:46:10 PM UTC, Mitchell Hashimoto wrote:
Hi! Can you set VAGRANT_LOG=debug and get that output? This is definitely
not working as intended!
Best,
Mitchell
http://pastebin.com/YfGEy4tk - here we are!
--
You received
It looks like this is a bug with the underlying SSH/SCP library that
Vagrant uses. Personally, I've never seen it before and I'm not sure why
it is behaving like that. Could you please report a bug to net-ssh/net-scp?
Best,
Mitchell
On Sun, Feb 9, 2014 at 8:59 PM, kapitanluffy pirata
Tyler,
This usually happens if you overwrote ~/.ssh/authorized_keys somehow. The
most common way this happens is you synced a folder into the home directory
of the VM.
Best,
Mitchell
On Fri, Feb 14, 2014 at 8:28 AM, Tyler Kerr destaria...@gmail.com wrote:
I had a server with vagrant
AG,
You're right, the first issue will be fixed with the next release of
Vagrant. I apologize about that.
As for the second: do you have SSH installed? Vagrant doesn't come with
SSH. The easiest way to get SSH is to just install msysgit.
Best,
Mitchell
On Fri, Feb 21, 2014 at 3:43 AM, smersh2
Hi,
The exception is originating from a plugin vagrant-vsphere. Please
contact that plugin author about this happening!
Best,
Mitchell
On Fri, Feb 21, 2014 at 5:01 AM, bwalli...@gmail.com wrote:
I have a jenkins server running on Centos 6.5, it is started as a server
and as the user build.
Julien,
The way Ansible works is to be installed on the host machine. We have plans
to introduce another ansible provisioner that runs ansible in local mode
and installs it on the guets, but its not there yet.
Best,
Mitchell
On Mon, Mar 3, 2014 at 3:10 PM, Julien Martin bal...@gmail.com wrote:
Remove `/opt/vagrant` and reinstall.
On Wed, Mar 12, 2014 at 10:09 AM, Brad bradley.g.sm...@gmail.com wrote:
Greetings
I updated Vagrant to 1.5 using the 64 bit rpm for fedora.
[bgsmith@pico test1] rpm -qa | grep -i vagrant
vagrant-1.5.0-1.x86_64
When I try to launch Vagrant I get the
Ken,
Vagrant can only install rsync into SOME guest OSes. Windows is not
currently supported.
On Wed, Mar 12, 2014 at 2:18 PM, Ken Sykora ksyk...@nerdery.com wrote:
Hi all:
I've been playing with the new file sharing types for Vagrant 1.5 and have
a few questions
1) For rsync, the blog
, is there a known workaround for the time being?
On Wednesday, March 12, 2014 3:55:44 PM UTC-6, Mitchell Hashimoto wrote:
Marc,
This was a bug introduced in 1.5.0 that is now fixed. It will be part of
1.5.1 that will be released shortly.
Best,
Mitchell
On Wed, Mar 12, 2014 at 12:39 PM, Marc
Brian,
You can rename them just fine and Vagrant will create new ones. What issues
are you running into?
On Thu, Mar 13, 2014 at 1:17 AM, Brian Capouch bri...@palaver.net wrote:
I wonder if there is a tip anywhere to remove .vagrant and
.vagrant.d from one's home directory before trying to
Hi,
Parallelization is not implemented for every provider. VirtualBox is one of
those providers.
On Mon, Mar 17, 2014 at 8:12 AM, AM-PM ampmt...@googlemail.com wrote:
I attached my sample vagrantfile, i am not able to configure my
vagrantfile to use parallel feature.
I am usng Vagrant 1.4.3
David,
Vagrant is supposed to gracefully handle when it can't connect to the
internet. This would be a bug! I'll look into it.
Best,
Mitchell
On Fri, Mar 21, 2014 at 10:20 PM, Alvaro Miranda Aguilera
kiki...@gmail.com wrote:
Hello
According to the manual, that feature should be off by
Steve,
Can you get the debug log with `--debug`. That might help with more
output info. Please gist since it'll be very loud.
Best,
Mitchell
On Sat, Mar 29, 2014 at 1:01 PM, Steve Pitschke stevep...@gmail.com wrote:
Recently when I try to restart my Vagrant image by using
Paul,
Not at the moment. The primary reason for the 1 hour expiration is for
security: we already just use security through obscurity (the name),
and we wanted to limit the time in which a person could actually
happen to find a share URL.
In practice, maybe extending it to 2 hours would be fine.
Alex,
I'm guessing that the cloud sever plugin you're using might not be
using the built-in rsync functionality. For exmaple, AWS and Rackspace
plugins haven't been updated to use this and they still use their own
built-in mechanism which doesn't support all of the same flags yet.
Best,
Mitchell
Please share your Vagrantfile
On Mon, Apr 14, 2014 at 3:16 PM, Steve Kirkpatrick skirkpatr...@ghx.com wrote:
Hello,
Trying to figure out why Vagrant (tried 1.5.1, 1.5.2 and 1.5.3) would run
the same provisioners multiple times on up and destroy.
Here is the output from a destroy:
$
Can you share your Vagrantfile? You're getting a pretty weird syntax
error out of your Vagrantfile.
On Fri, Apr 18, 2014 at 6:30 AM, AJ NOURI ajn@gmail.com wrote:
After upgrading to 1.5.3, on the first vagrant up command (reconfigure
VMs)
And no Vagrantfile seems to work anymore!!
The
Jeremy,
Coming in late here to say that this bug has been resolved, but took quite
a big of internal changes so it is slated for Vagrant 1.6.
With 1.6, rsync-auto will see even the folders your provisioner sets up.
Best,
Mitchell
--
You received this message because you are subscribed to the
Hello!
To install Vagrant, use the official packages, especially if you're
just getting started: http://www.vagrantup.com/downloads.html
From that page, I recommend following through to the getting started
guide as well.
Best,
Mitchell
On Tue, Apr 22, 2014 at 6:58 PM, utsav kumar
Coming in Vagrant 1.6:
http://www.vagrantup.com/blog/feature-preview-vagrant-1-6-global-status.html
On Mon, Apr 28, 2014 at 12:04 PM, Christian Berendt
bere...@b1-systems.de wrote:
Is there a command/plugin to list all running Vagrant instances on a system?
At the moment I have several
The installers are hosted on S3, so I doubt its our problem. :)
On Thu, May 1, 2014 at 10:19 AM, Moops Blanders irons...@gmail.com wrote:
Anyone having problems downloading Vagrant from the website? Tried twice in
Chrome and got a network failed error.
Then tried in Safari and it seems to
Niklas,
You'll have to acquire Windows ISOs yourself using a legal method.
Once the ISO is acquired, you can use a project such as packer-windows
to very easily create Windows Vagrant boxes. We're trying to make this
as plug-and-play as possible, and you'll hear more about this in
upcoming
This unknown error is 100% always an issue with VMware itself. It is
unfortunate they don't have a more descriptive error message. One way
to get the real error message to surface is to enable GUI mode. VMware
usually pops up a message telling you what went wrong.
Best,
Mitchell
On Tue, May 6,
Its a top priority to fix. You can expect a fix in 1.6.1 this week. I
apologize for this. Luckily, there are no internal state changes
between 1.5 and 1.6. I'd recommend downgrading for now.
On Tue, May 6, 2014 at 1:01 PM, Chris Handy chrisjha...@gmail.com wrote:
Multiple people are getting it
It looks like this is coming from a plugin, make sure you remove all
plugins, they may not be aware that Vagrant works with Windows now.
Best,
Mitchell
On Wed, May 7, 2014 at 8:23 AM, Kasper Nielsen kaspe...@gmail.com wrote:
Hi,
I'm trying out the new windows guest feature in 1.6 but I am
Nadeem,
This is usually because VT-x isn't enabled on your machine. You have
to do this from the BIOS.
On Wed, May 7, 2014 at 2:34 AM, Nadeem Ahmed n.ahmed.ans...@gmail.com wrote:
i am getting error message while going vagrant up
the guest machine entered an invalid state while waiting for it
point, but
there isn't a big value for us right now to do this and its extra
work.
Best,
Mitchell
On Thu, May 8, 2014 at 12:01 AM, Christian Berendt
bere...@b1-systems.de wrote:
On 05/08/2014 02:22 AM, Mitchell Hashimoto wrote:
We do send release notifications prefixed with [ANN] that you can
The release process for Vagrant requires executing a script anyways,
so perhaps I can hook something up in there to post something
somewhere...
I'll see what I can do to make this better.
On Thu, May 8, 2014 at 12:13 AM, Mitchell Hashimoto
mitchell.hashim...@gmail.com wrote:
Christian,
You're
Diego,
There isn't, and won't be from within the Vagrantfile for the
forseeable time. But we are considering adding a `vagrant port`
command that will tell you where things were forwarded to.
Best,
Mitchell
On Fri, May 9, 2014 at 10:32 AM, Diego Zamboni di...@zzamboni.org wrote:
Hi,
I'm
VirtualBox itself doesn't support VirtualBox running in VirtualBox.
VMware this works fine.
On Fri, May 9, 2014 at 11:56 AM, blong brianbl...@gmail.com wrote:
I'm assuming this isn't recommended, but stay with me! I'm trying to
configure a CentOS environment to run VirtualBox and Vagrant
Hey!
This looks amazing! I noticed you're using `VBoxManage` directly. You
should take advantage of Vagrant 1.6's new global status and global
control
(http://www.vagrantup.com/blog/feature-preview-vagrant-1-6-global-status.html)
and you'll be able to make this work with ANY Vagrant environment,
, Mitchell Hashimoto
mitchell.hashim...@gmail.com wrote:
Brian,
VirtualBox doesn't support running in VirtualBox. You can run
VirtualBox in another VM (VMware) usually, but it is very expensive.
Best,
Mitchell
On Sun, May 11, 2014 at 2:23 PM, Brian Long brianbl...@gmail.com wrote
The URL for the box you specified is only for VirtualBox. If you want
a Hyper-V box, use hashicorp/precise64
On Mon, May 19, 2014 at 8:46 PM, Eric Sepich ericsepic...@gmail.com wrote:
My OS is Windows 8.1. I have attached my Vagrantfile. I am getting some
messaging about the provider coming out
Matt,
For this you'll need to use a custom docker host VM. But don't worry,
it is _very_ easy. See the docs here:
http://docs.vagrantup.com/v2/docker/basics.html
On Thu, May 22, 2014 at 12:16 PM, Matt Ho matt...@gmail.com wrote:
I'm trying to use vagrant with docker and would like to configure
Matt,
Right, you'll have to create a new Vagrantfile to represent the new
host VM. I know you're fine with the VM image we're providing but
unfortunately there is no way to modify that without creating a new
Vagrantfile.
Best,
Mitchell
On Thu, May 22, 2014 at 1:02 PM, Matt Ho matt...@gmail.com
Hi,
We just pushed Vagrant VMware Adapter 2.5.0. This contains minor bug
fixes across all platforms but most importantly adds the groundwork
for Fusion 7 as well as support for the VMware Fusion Tech Preview
which allows the adapter to work well with Yosemite (OS X 10.10).
Note that VMware
Hello,
I've just pushed version 3.0.0 of the Vagrant VMware plugins, which
enables support for Fusion 7 (released today) and lays the groundwork
for Workstation 11 (to be released shortly I imagine). Just as we did
last year, there will be an upgrade fee associated with this if you
own the
Jay,
Vagrant has a quite a few committers currently, though they mostly
specialize in certain areas (Ansible, Windows, etc.). We're certainly
always looking to add more interested/willing individuals to the
project.
Best,
Mitchell
On Tue, Sep 23, 2014 at 11:59 AM, jay vyas
Joe,
Sounds like it. I'm not sure what that command is doing under the
covers, but its out of our control.
Best,
Mitchell
On Sun, Oct 19, 2014 at 7:58 PM, Joe Fiorini j...@joefiorini.com wrote:
Okay, so I got a little bit further, so I'm chocking the original problem up
to a bad build of my
,
Mitchell
On Tue, Dec 9, 2014 at 10:17 PM, Mitchell Hashimoto
mitchell.hashim...@gmail.com wrote:
Marc,
I think I know what this is and I'm working on a fix now.
Best,
Mitchell
On Tue, Dec 9, 2014 at 10:14 PM, Marc-André Courtois court...@gmail.com
wrote:
I updated to 1.7.0 and started
Mark,
Nope, you will never have to re-purchase the plugin for the Vagrant
version update. You may have to redownload it one day but not for this
version (and we've never broken backwards compatibility yet for the
plugin).
Best,
Mitchell
On Wed, Dec 10, 2014 at 8:25 AM, Mark Fletcher
:06 UTC-6, Mitchell Hashimoto wrote:
Marc,
This should now be fixed. Please redownload the installer.
Best,
Mitchell
On Tue, Dec 9, 2014 at 10:32 PM, Mitchell Hashimoto
mitchell@gmail.com wrote:
Marc,
New installers are building. I'll elaborate on what went wrong:
Our
Frank,
The location of these boxes hasn't changed in nearly a year. I'd say
that this is probably just due to transient issues.
Best,
Mitchell
On Wed, Dec 17, 2014 at 2:43 PM, Frank Patz-Brockmann
frank.p...@gmail.com wrote:
After month I've returned to using vagrant and find downloading base
:08 PM UTC-4, Mitchell Hashimoto wrote:
Chester,
Did you install the VMware provider? That error message is becuse the
provider itself is not installed.
Best,
Mitchell
On Tue, Jan 6, 2015 at 12:38 PM, Chester Lee chester@gmail.com
wrote:
I just did it. and it shows `hashicorp
Hi,
The gem install in the latest version just tells you to use the installer.
It is for people who don't realize installers exist yet.
Best,
Mitchell
On Fri, May 15, 2015 at 3:37 AM, mnz hz mnz...@gmail.com wrote:
i think it's cool if i can install vagrant using gem command:)
--
You
Hi,
1.7.4 will be released this week to address that, that is the major
regression 1.7.3 introduced. :(
Best,
Mitchell
On Mon, Jul 13, 2015 at 9:02 AM, jpbourbon jpbour...@gmail.com wrote:
Hi all,
I was wondering you you're gong to do a new release soon to fix #5955,
or should I just
Hi,
Ubuntu themselves provide official Vagrant boxes without source code in the
boxes.
I'm not a lawyer, but that seems like a blessing to do so.
Best,
Mitchell
On Mon, Nov 23, 2015 at 11:08 PM, wrote:
> In my understanding of GPL you MUST NOT distribute GPL software in any
>
ary to purchase an older version?
> This is on my old Mac Pro with OSX 10.6.8 (Snow Leopard).
> It's old, but is still an awesome workhorse that I use for a lot of virtual
> machines include Mint 18 and Windows 10 with Visual Studio.
>
>
>
> On Monday, November 6, 2017 at 2:40:4
Hey Mahmood,
This is an OS or BIOS level setting, and can’t be set by Vagrant or VirtualBox.
Please check for help for your specific OS on enabling AMD-V, and also check
your BIOS settings on boot.
Best,
Mitchell
On Mar 14, 2018, 9:29 AM -0700, Mahmood Naderan , wrote:
>
60 matches
Mail list logo