Hello,

I've previously posted regarding the same issue for versions of 
vagrant-vmware-workstation > 4.0.24. I am posting now to confirm the same 
issue on 5.0.4. I have previously raised a support ticket with Hashicorp a 
month ago but haven't received an answer, other than to check I was running 
as an administrator, which I am.

I am unable to install the vagrant-vmware-workstation v5.0.4 on Windows 10 
under a domain account with administrator privileges, HOMEDRIVE U: and 
HOME: C:\Users\<UserName>.

*I'm seeing the following:*

c:\dev\ssrn>vagrant plugin install vagrant-vmware-workstation
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.4.gem (100%)
Building native extensions. This could take a while...

*It never returns from building native extensions. Hitting CTRL-C leads to 
the following output:*

ERROR: Failed to build gem native extension.

    current directory: 
C:/Users/SmithSta/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4/ext/vagrant-vmware-desktop
C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r 
./siteconf20171129-7652-qq6md5.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/SmithSta/.vagrant.d/gems/2.4.2/gems/vagrant-vmware-workstation-5.0.4 
for inspection.
Results logged to 
C:/Users/SmithSta/.vagrant.d/gems/2.4.2/extensions/x64-mingw32/2.4.0/vagrant-vmware-workstation-5.0.4/gem_make.out

*Or with debug, the last few lines are:*

DEBUG bundler: Enabling user defined remote RubyGems sources
DEBUG bundler: Enabling default remote RubyGems sources
DEBUG bundler: Adding source - https://rubygems.org/
DEBUG bundler: Adding source - https://gems.hashicorp.com/
DEBUG bundler: Current source list for install: ["https://rubygems.org/";, 
"https://gems.hashicorp.com/";]
DEBUG bundler: Generating new builtin set instance.
DEBUG bundler: Generating new plugin set instance. Skip gems - []
DEBUG bundler: Generating solution set for installation.
DEBUG bundler: Activating solution set: ["ruby_dep-1.3.1", "erubis-2.7.0", 
"builder-3.2.3", "gyoku-1.3.1", "nori-2.6.0", "multi_json-1.12.2", 
"little-plugger-1.1.4", "logging-2.2.2", "rubyntlm-0.6.2", 
"httpclient-2.8.3", "ffi-1.9.18", "gssapi-1.2.0", "winrm-2.2.3", 
"rubyzip-1.2.1", "winrm-fs-1.1.0", "winrm-elevated-1.1.0", "wdm-0.1.1", 
"netrc-0.11.0", "mime-types-data-3.2016.0521", "mime-types-3.1", 
"unf_ext-0.0.7.4", "unf-0.1.4", "domain_name-0.5.20170404", 
"http-cookie-1.0.3", "rest-client-2.0.2", "rb-kqueue-0.2.5", 
"net-ssh-4.1.0", "net-scp-1.2.1", "net-sftp-2.1.2", "log4r-1.1.10", 
"hashicorp-checkpoint-0.1.4", "rb-inotify-0.9.10", "rb-fsevent-0.10.2", 
"listen-3.1.5", "i18n-0.8.0", "childprocess-0.6.3", "vagrant-2.0.1", 
"vagrant-share-1.1.9", "vagrant-vmware-workstation-5.0.4", 
"bigdecimal-1.3.0", "bundler-1.16.0", "io-console-0.4.6", "json-2.0.4", 
"openssl-2.0.5", "psych-2.2.2", "rdoc-5.0.0"]
DEBUG bundler: Activating gem vagrant-share-1.1.9
DEBUG bundler: Activating gem vagrant-vmware-workstation-5.0.4
DEBUG bundler: Activating gem bigdecimal-1.3.0
DEBUG bundler: Activating gem bundler-1.16.0
DEBUG bundler: Installing required gems.
Building native extensions. This could take a while...

*The Windows process tree is as follows:*


   1. vagrant  plugin install vagrant-vmware-workstation --debug
   2. ruby 
   C:\HashiCorp\Vagrant\embedded\gems\gems\vagrant-2.0.1\bin\vagrant plugin 
   install vagrant-vmware-workstation --debug
   3. C:\Windows\system32\cmd.exe /c 
   "C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe -r 
   ./siteconf20171129-7648-1icz2ll.rb extconf.rb 2>&1"
   4. C:/HashiCorp/Vagrant/embedded/mingw64/bin/ruby.exe  -r 
   ./siteconf20171129-7648-1icz2ll.rb extconf.rb 
   5. .\vagrant-vmware-installer_windows_amd64.exe install
   6. C:\Windows\system32\wbem\wmic.exe useraccount where "SID like 
   'S-1-5-%-500'" get name
   

*wmic.exe has 3 threads, each with the following respective stack:*

Thread Start Address: wmic.exe+0x3f460, Thread State: Wait:WrLpcReply
0 ntoskrnl.exe!KeSynchronizeExecution+0x3f26
1 ntoskrnl.exe!KeWaitForMultipleObjects+0x109c
2 ntoskrnl.exe!KeWaitForMultipleObjects+0xb3f
3 ntoskrnl.exe!KeWaitForMutexObject+0x377
4 ntoskrnl.exe!KeUnstackDetachProcess+0x2230
5 ntoskrnl.exe!ObDereferenceObjectDeferDelete+0x28a
6 ntoskrnl.exe!KeWaitForMultipleObjects+0x1283
7 ntoskrnl.exe!KeWaitForMultipleObjects+0xb3f
8 ntoskrnl.exe!KeWaitForMutexObject+0x377
9 ntoskrnl.exe!ExReleasePushLockSharedEx+0x7c8
10 ntoskrnl.exe!ObReferenceObjectByHandle+0xbb58
11 ntoskrnl.exe!ObReferenceObjectByHandle+0xa831
12 ntoskrnl.exe!ObReferenceObjectByHandle+0x8b0d
13 ntoskrnl.exe!setjmpex+0x3ab3
14 ntdll.dll!ZwAlpcSendWaitReceivePort+0x14
15 RPCRT4.dll!NdrSimpleStructUnmarshall+0x6481
16 RPCRT4.dll!I_RpcSendReceive+0xce
17 combase.dll!PropVariantCopy+0x12c2b
18 combase.dll!PropVariantCopy+0x182c5
19 combase.dll!PropVariantCopy+0x17797
20 combase.dll!HICON_UserFree+0xa2c
21 RPCRT4.dll!NdrpClientCall2+0x31f
22 combase.dll!HICON_UserFree+0x383
23 combase.dll!ObjectStublessClient32+0xfc32
24 fastprox.dll!CWbemDataPacket::IsValid+0x193
25 wmic.exe+0x1491a
26 wmic.exe+0x16c2a
27 wmic.exe+0x13f66
28 wmic.exe+0x3989b
29 wmic.exe+0x387c3
30 wmic.exe+0x3f3dd
31 KERNEL32.DLL!BaseThreadInitThunk+0x14
32 ntdll.dll!RtlUserThreadStart+0x21


Thread Start Address: ntdll.dll!RtlReleaseSRWLockExclusive+0x1370, Thread 
State: WrQueue
0 ntoskrnl.exe!KeSynchronizeExecution+0x3f26
1 ntoskrnl.exe!KeWaitForMultipleObjects+0x109c
2 ntoskrnl.exe!KeWaitForMultipleObjects+0xb3f
3 ntoskrnl.exe!KeWaitForMutexObject+0x377
4 ntoskrnl.exe!KeUnstackDetachProcess+0x2230
5 ntoskrnl.exe!ObDereferenceObjectDeferDelete+0x28a
6 ntoskrnl.exe!KeWaitForMultipleObjects+0x1283
7 ntoskrnl.exe!KeWaitForMultipleObjects+0xb3f
8 ntoskrnl.exe!KeRemoveQueueEx+0x2f0
9 ntoskrnl.exe!ObfReferenceObject+0x118
10 ntoskrnl.exe!ExAcquireFastMutex+0x48c
11 ntoskrnl.exe!setjmpex+0x3ab3
12 ntdll.dll!ZwWaitForWorkViaWorkerFactory+0x14
13 ntdll.dll!RtlReleaseSRWLockExclusive+0x1ade
14 KERNEL32.DLL!BaseThreadInitThunk+0x14
15 ntdll.dll!RtlUserThreadStart+0x21


Thread Start Address: combase.dll!Ordinal112+0x720, Thread State: 
Wait:WrUserRequest
0 ntoskrnl.exe!KeSynchronizeExecution+0x3f26
1 ntoskrnl.exe!KeWaitForMultipleObjects+0x109c
2 ntoskrnl.exe!KeWaitForMultipleObjects+0xb3f
3 ntoskrnl.exe!KeWaitForMutexObject+0x377
4 ntoskrnl.exe!KeUnstackDetachProcess+0x2230
5 ntoskrnl.exe!ObDereferenceObjectDeferDelete+0x28a
6 ntoskrnl.exe!KeWaitForMultipleObjects+0x1283
7 ntoskrnl.exe!KeWaitForMultipleObjects+0xb3f
8 ntoskrnl.exe!KeWaitForMultipleObjects+0x4fe
9 win32kfull.sys!Ordinal2232+0x5a3
10 win32kfull.sys!Ordinal2232+0x1b8
11 win32kfull.sys!Ordinal1763+0x1943
12 win32kfull.sys!Ordinal1647+0x92
13 ntoskrnl.exe!setjmpex+0x3ab3
14 win32u.dll!NtUserGetMessage+0x14
15 USER32.dll!GetMessageW+0x26
16 combase.dll!CoReleaseMarshalData+0x715
17 combase.dll!CoReleaseMarshalData+0x843
18 combase.dll!Ordinal112+0xcbb
19 combase.dll!Ordinal112+0x79c
20 KERNEL32.DLL!BaseThreadInitThunk+0x14
21 ntdll.dll!RtlUserThreadStart+0x21

If I manually run "C:\Windows\system32\wbem\wmic.exe useraccount", I also 
observe it never returns. This seems to be the root cause.

-- 
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 vagrant-up+unsubscr...@googlegroups.com.
To view this discussion on the web visit 
https://groups.google.com/d/msgid/vagrant-up/7dd20acc-0de1-4a12-8ed5-4e2aecbbd1a1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to