Re: [vagrant-up] VMWare Plugin with VMware Workstation 12 Pro or Player?

2015-12-23 Thread Alvaro Miranda Aguilera
Hello, The version you require is Vmware workstation 12 pro. They did change the name of the player, so now is workstation player, however there is more a commercial/licensing limitation rather than a technical one. Alvaro. On Thu, Dec 24, 2015 at 1:20 PM, Torben Knerr wrote: > Hello everybod

[vagrant-up] VMWare Plugin with VMware Workstation 12 Pro or Player?

2015-12-23 Thread Torben Knerr
Hello everybody, first of all, congrats to the latest 1.8 release! :-) Quick question: for the vmware plugin, do I need a) VMware Workstation 12 Pro or would b) VMware Workstation 12 Player enough? Have a nice christmas time, Torben -- This mailing list is governed under the HashiCor

[vagrant-up] vagrant 1.8 fails to mount shared folder specified with UNC path

2015-12-23 Thread Vince Skahan
Running 1.8 on Windows7pro, vagrant seems to be getting confused re: backslashes in shared folder definitions. Worked under 1.7.4 and earlier. - I'm trying to mount a remote \\host.domain\path_here onto /some/local/path in the VM - previously, we had to escapebackslashes and double t

Re: [vagrant-up] Vagrant 1.8 fails with VM Ware plugin

2015-12-23 Thread Joe George
Manually upgrading plugin vagrant-vmware-fusion from 4.0.2 to 4.0.5 seems to have cleared up the problem. For some reason, running vagrant plugin update did not update it. On Tuesday, December 22, 2015 at 3:37:42 PM UTC-5, Alvaro Miranda Aguilera wrote: > > Hello, > > For VMWare plugin, you can

Re: [vagrant-up] Vagrant 1.8 failed to initialize at a very early stage

2015-12-23 Thread Alvaro Miranda Aguilera
Hi Justin. I did install just fine on the same version. Logs at the end. I even install the plugin that was causing problems, and rename to /(1/) to match your first install.. all went fine. Does your machine have internet access? Any chance you can uninstall the old version, blow away ~/.vagr