hello for the vmware plugin the best is contact support.
Can you please email [email protected] Thanks Alvaro. On Thu, Oct 19, 2017 at 10:59 AM, Stefan Smith <[email protected]> wrote: > Hi, > > I'm unable to install the latest versions 4.0.25 or 5.0.0 of > the vagrant-vmware-workstation plugin. Version 4.0.24 installs without a > problem. I'm on Windows 10 in a corporate environment. > > Running vagrant plugin install vagrant-vmware-workstation > --plugin-version 5.0.0 fails with the following output (username replaced > with "xxxx"): > > ----------------- > > Installing the 'vagrant-vmware-workstation' plugin. This can take a few > minutes... > Fetching: vagrant-share-1.1.9.gem (100%) > Fetching: vagrant-vmware-workstation-5.0.0.gem (100%) > Building native extensions. This could take a while... > > Vagrant is installing the VMware plugin which requires > Administrator access. You may be prompted for your password to > complete setup. > > Failed to complete install: exec: "U:\\windows\\system32\\wbem\\wmic.exe": > file does not exist > Bundler, the underlying system Vagrant uses to install plugins, > reported an error. The error is shown below. These errors are usually > caused by misconfigured plugin installations or transient network > issues. The error from Bundler is: > > ERROR: Failed to build gem native extension. > > current directory: C:/Users/xxxx/.vagrant.d/gems/ > 2.3.4/gems/vagrant-vmware-workstation-5.0.0/ext/vagrant-vmware-desktop > C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r > ./siteconf20171019-11388-1knpft3.rb extconf.rb > *** extconf.rb failed *** > Could not create Makefile due to some reason, probably lack of necessary > libraries and/or headers. Check the mkmf.log file for more details. You > may > need configuration options. > > Provided configuration options: > --with-opt-dir > --without-opt-dir > --with-opt-include > --without-opt-include=${opt-dir}/include > --with-opt-lib > --without-opt-lib=${opt-dir}/lib > --with-make-prog > --without-make-prog > --srcdir=. > --curdir > --ruby=C:/HashiCorp/Vagrant/embedded/mingw64/bin/$(RUBY_BASE_NAME) > > extconf failed, exit code 1 > > Gem files will remain installed in C:/Users/xxxx/.vagrant.d/gems/ > 2.3.4/gems/vagrant-vmware-workstation-5.0.0 for inspection. > Results logged to C:/Users/xxxx/.vagrant.d/gems/ > 2.3.4/extensions/x64-mingw32/2.3.0/vagrant-vmware- > workstation-5.0.0/gem_make.out > > ----------------- > > If I first run SET HOMEDRIVE=C: > Running vagrant plugin install vagrant-vmware-workstation > --plugin-version 5.0.0 does not progress beyond the following output: > > ----------------- > > Installing the 'vagrant-vmware-workstation --version '5.0.0'' plugin. This > can take a few minutes... > Fetching: vagrant-vmware-workstation-5.0.0.gem (100%) > Building native extensions. This could take a while... > > Vagrant is installing the VMware plugin which requires > Administrator access. You may be prompted for your password to > complete setup. > > ----------------- > > Analysing the waiting process chain, it is as follows: > > vagrant plugin install vagrant-vmware-workstation --plugin-version 5.0.0 > ruby C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-2.0.0\bin\vagrant > plugin install vagrant-vmware-workstation --plugin-version 5.0.0 > C:\Windows\system32\cmd.exe /c > "C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe > -r ./siteconf20171019-12892-1bui6qc.rb extconf.rb 2>&1" > C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r > ./siteconf20171019-12892-1bui6qc.rb extconf.rb > .\vagrant-vmware-installer_windows_amd64.exe install > C:\windows\system32\wbem\wmic.exe useraccount where "SID like > 'S-1-5-%-500'" get name > > It seems to be hanging in WMIC.exe. Simply running > C:\windows\system32\wbem\wmic.exe > useraccount also hangs. > > Stef > > -- > 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 [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/vagrant-up/77b2973f-cca5-4594-aec1-2de12cb1e10d%40googlegroups.com > <https://groups.google.com/d/msgid/vagrant-up/77b2973f-cca5-4594-aec1-2de12cb1e10d%40googlegroups.com?utm_medium=email&utm_source=footer> > . > 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 [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/CAHqq0exdEkjx-D-vZraxkUSGwMmbZOk1Q1X56uugCiwQyO8E_A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
