Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vagrant doesn't start with smb type share #4004

Closed
zerkms opened this issue Jun 9, 2014 · 4 comments
Closed

Vagrant doesn't start with smb type share #4004

zerkms opened this issue Jun 9, 2014 · 4 comments

Comments

@zerkms
Copy link

zerkms commented Jun 9, 2014

version 1.6.2 (just noticed there is 1.6.3 available)

The Vagrantfile is default as generated with vagrant init with only one additional line added:

config.vm.synced_folder "e:\\tmp\\vagrant-rsync\\data\\", "/vagrant_data", type: "smb"

vagrant up --debug last lines are:

...
DEBUG subprocess: Waiting for process to exit. Remaining to timeout: 32000
DEBUG subprocess: Exit status: 0
 INFO warden: Calling IN action: #<VagrantPlugins::SyncedFolderNFS::ActionCleanup:0x36bc250>
DEBUG host: Searching for cap: nfs_prune
DEBUG host: Checking in: windows
 INFO nfs: Host doesn't support pruning NFS. Skipping.
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolderCleanup:0x3753528>
 INFO subprocess: Starting process: ["C:\\Windows\\System32\\WindowsPowerShell\\v1.0\\/powershell.EXE", "-NoProfile", "-ExecutionPolicy", "Bypass", "$PSVersionTable.PSVersion.Major"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 2

After this output it freezes infinitely until Ctrl-C is sent.

@mitchellh
Copy link
Contributor

I've been told this a few times but have neve rbeen able to repro. Can you please try to debug further? Sorry. Specifically, try executing that command (the powershell.exe) command and see if it hangs in a normal shell for you. Please let me know.

@ghost
Copy link

ghost commented Aug 14, 2014

same problem with vagrant-1.6.3.

 INFO nfs: Host doesn't support pruning NFS. Skipping.
 INFO warden: Calling IN action: #<Vagrant::Action::Builtin::SyncedFolderCleanup:0x37e3108>
 INFO subprocess: Starting process: ["C:\\windows\\System32\\WindowsPowerShell\\v1.0/powershell.EXE", "-NoProfile", "-ExecutionPolicy", "Bypass", "$PSVersionTable.PSVersion.Major"]
DEBUG subprocess: Selecting on IO
DEBUG subprocess: stdout: 2

@mkuzmin
Copy link
Contributor

mkuzmin commented Sep 1, 2014

This is a duplicate of #3894

@piotr-cz
Copy link

piotr-cz commented Sep 3, 2014

I'd say this as a duplicate of #3257.

The output of $PSVersionTable.PSVersion.Major is 2 which doesn't necessarily cause halt, but at least says that you are running PowerShell 2.x.

Apparently you should update the PowerShell to 3.0+ (available for Windows 7+).

I'd appreciate if PS scripts would run on 2.0 ;)

@ghost ghost locked and limited conversation to collaborators Apr 10, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

4 participants