[vagrant-up] Re: Clear Linux box

have you tried vmware-fusion? i found it faster than parallels, especially with nested virtualization. now you got me curious if this would translate to better battery performance. there are also a couple vagrant xhyve ports, and an article about them.

Re: [vagrant-up] different box by provider?

On Monday, August 7, 2017 at 5:06:15 AM UTC-7, Alvaro Miranda Aguilera wrote: > > Hello > > > https://www.vagrantup.com/docs/providers/configuration.html#overriding-configuration > > If you think is not easy to reach, OR, something is missed, please feel > free to say so, so we can update the

Re: [vagrant-up] different box by provider?

Hello https://www.vagrantup.com/docs/providers/configuration.html#overriding-configuration If you think is not easy to reach, OR, something is missed, please feel free to say so, so we can update the documentation. Where do you think is more natural to have this if the current place is hard to

Re: [vagrant-up] different box by provider?

On Monday, August 7, 2017 at 4:40:43 AM UTC-7, Torben Knerr wrote: > > Hi, > > you can override it in a provider specific block using the 2nd block > argument, e.g.: > > Thanks! where is this documented? vagrant needs a wiki for all the stuff not covered in the docs. -- This mailing list

Re: [vagrant-up] different box by provider?

Hi, you can override it in a provider specific block using the 2nd block argument, e.g.: config.vm.provider :virtualbox do |vbox, override| override.vm.box = "some/box" end config.vm.provider :libvirt do |libv, override| override.vm.box = "other/box" end Cheers, Torben On

[vagrant-up] different box by provider?

how does one specify a different box for different providers? for example hashicorp/xenial64 for virtualbox, something else for libvirt. -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of

Re: [vagrant-up] Vagrant tries to use IPv6 address and fails to connect via WinRM

I think that issue is fixed on some code changes on Vagrant hyperv provider. On Monday, 7 August 2017 13:47:06 UTC+5:30, ashok vaddevalli wrote: > > Hi Alvaro, > > That issue is related to Vagrant hyperv. I am also getting same issue on > Vagrant vsphere. > > > Thanks, > Ashok > > > > On Monday,

Re: [vagrant-up] Vagrant tries to use IPv6 address and fails to connect via WinRM

For temporary solution, I have disabled ipv6 on guest VM, now I am getting different error below. E:\Vagrant-vpshere\Vagrant>vagrant up --provider=vsphere Bringing machine 'default' up with 'vsphere' provider... ==> default: Calling vSphere CloneVM with the following settings: ==> default: --

Re: [vagrant-up] Using Vagrant login behind a corporate firewall fails

Hello You can set this variable to the cert file you need to use: SSL_CERT_FILE Alvaro On Thu, Aug 3, 2017 at 10:14 PM, Steve A (MM) wrote: > I am using a private vagrant repository and will need to login as part of > a CI/CD process. > > Testing this on the cli I am

Re: [vagrant-up] Vagrant tries to use IPv6 address and fails to connect via WinRM

Hello There is an issue already open for this: https://github.com/mitchellh/vagrant/issues/8759 You can follow that one. Alvaro On Sat, Aug 5, 2017 at 7:03 AM, ashok vaddevalli wrote: > *Vagrant version* > Vagrant 1.9.7 > > > *Host operating system* > Windows 7 > >