So how to actually setup vagrant with vmware and wsl?

classic Classic list List threaded Threaded
2 messages Options
Reply | Threaded
Open this post in threaded view
|

So how to actually setup vagrant with vmware and wsl?

Georgi
Hello everybody,
so, Im using Windows 10 (version 1709), wsl, vmware workstation and vagrant.

Vagrant is setup on the Windows with the vmware workstation plugin licensed and everything works fine. For example:

----------------------------------------
C:\WINDOWS\system32>vagrant plugin list
vagrant-share (1.1.9, system)
  - Version Constraint: > 0
vagrant-vmware-workstation (5.0.4)
  - Version Constraint: > 0
----------------------------------------

The default provider is set to vmware_workstation (i.e VAGRANT_DEFAULT_PROVIDER=vmware_workstation).

Now, I want to use vagrant on wsl, so that I can do ansible provisionings. Now the fun stuff begins. I've installed
the debian package as per documentation and then added the env variable, so that vagrant has access to the native Windows System.

I cannot simply invoke vagrant, I need to use sudo everytime, otherwise if I use debug I got the following output (snippet):

----------------------------------------
DEBUG subprocess: Exit status: 0
 INFO subprocess: Starting process: ["/mnt/c/HashiCorp/Vagrant/bin/vagrant.exe", "version"]
 INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Vagrant failed to initialize at a very early stage:

Failed to invoke the VMware utility task.

  Cause: ERROR: Access is denied.

Please address the issue above and try again. If
this problem persists, please contact [hidden email]
----------------------------------------


If I try to start a machine, vagrant complains, that it cannot find a provider, even if I specify per hand one:

----------------------------------------
~/vagrant_test$ sudo vagrant up --provider=vmware_workstation
The provider 'vmware_workstation' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.
----------------------------------------

If I install and license the vmware_workstation provider on wsl, the vagrant
complains that it cannot find a vmware installation (which is actually correct).

 Any idea what am I doing wrong? I suppose installing and licensing the vmware_workstation provider
on Windows and not WSL should be sufficient, but this does not work currently.

Thank you in advance.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f3a60a6f-37c8-4426-b111-398f067e96f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
Reply | Threaded
Open this post in threaded view
|

Re: So how to actually setup vagrant with vmware and wsl?

Alvaro Miranda Aguilera
Hello

WSL information is here:

It should work for VirtualBox, and let you use Docker with a DOCKER_HOST

But WSL + VMWare is not yet listed in the page.

Thanks
Alvaro.

On Fri, Dec 15, 2017 at 3:09 PM, Georgi <[hidden email]> wrote:
Hello everybody,
so, Im using Windows 10 (version 1709), wsl, vmware workstation and vagrant.

Vagrant is setup on the Windows with the vmware workstation plugin licensed and everything works fine. For example:

----------------------------------------
C:\WINDOWS\system32>vagrant plugin list
vagrant-share (1.1.9, system)
  - Version Constraint: > 0
vagrant-vmware-workstation (5.0.4)
  - Version Constraint: > 0
----------------------------------------

The default provider is set to vmware_workstation (i.e VAGRANT_DEFAULT_PROVIDER=vmware_workstation).

Now, I want to use vagrant on wsl, so that I can do ansible provisionings. Now the fun stuff begins. I've installed
the debian package as per documentation and then added the env variable, so that vagrant has access to the native Windows System.

I cannot simply invoke vagrant, I need to use sudo everytime, otherwise if I use debug I got the following output (snippet):

----------------------------------------
DEBUG subprocess: Exit status: 0
 INFO subprocess: Starting process: ["/mnt/c/HashiCorp/Vagrant/bin/vagrant.exe", "version"]
 INFO subprocess: Command not in installer, restoring original environment...
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stderr: Vagrant failed to initialize at a very early stage:

Failed to invoke the VMware utility task.

  Cause: ERROR: Access is denied.

Please address the issue above and try again. If
this problem persists, please contact [hidden email]
----------------------------------------


If I try to start a machine, vagrant complains, that it cannot find a provider, even if I specify per hand one:

----------------------------------------
~/vagrant_test$ sudo vagrant up --provider=vmware_workstation
The provider 'vmware_workstation' could not be found, but was requested to
back the machine 'default'. Please use a provider that exists.
----------------------------------------

If I install and license the vmware_workstation provider on wsl, the vagrant
complains that it cannot find a vmware installation (which is actually correct).

 Any idea what am I doing wrong? I suppose installing and licensing the vmware_workstation provider
on Windows and not WSL should be sufficient, but this does not work currently.

Thank you in advance.

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/f3a60a6f-37c8-4426-b111-398f067e96f5%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.



--
Alvaro

--
This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list.
 
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
You received this message because you are subscribed to the Google Groups "Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [hidden email].
To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0ezKtE_HN-tvxO1Et61zSuHqSDDvK%2BvszO%2BzLd%3D5u2x-vg%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.