hangs on windows host while booting centos guest after "Checking mount"

[henning-flmnn]

Hello,

I'm, trying to set up an sshfs mounted folder in a Centos 7 guest from a windows 7 host.

I configure it like this

...
  config.vm.synced_folder ".", "/vagrant", disabled: true
  config.vm.synced_folder "../..", "/windata_home", type: "sshfs"
...

(the first entry to disable the nonworking default mount, the second for the sshfs mount)

What I get is:

$ vagrant up
==> default: Attempting graceful shutdown of VM...
==> default: Checking if box 'centos/7' is up to date...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
    default: Adapter 1: nat
==> default: Forwarding ports...
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 127.0.0.1:2222
    default: SSH username: vagrant
    default: SSH auth method: private key
==> default: Machine booted and ready!
==> default: Checking for guest additions in VM...
    default: No guest additions were detected on the base box for this VM! Guest
    default: additions are required for forwarded ports, shared folders, host only
    default: networking, and more. If SSH fails on this machine, please install
    default: the guest additions and repackage the box to continue.
    default:
    default: This is not an error message; everything may continue to work properly,
    default: in which case you may ignore this message.
==> default: Mounting SSHFS shared folder...
==> default: Mounting folder via SSHFS: C:/Users/myname/some/path => /windata
==> default: Checking Mount..

And from here ths boot hangs.
After waiting for ~10 minutes I entered CTRL-C, the machine was running, but the mountpoint exists and is empty.

Logfile vagrant_sshfs_sftp_server_stderr.txt is empty, vagrant_sshfs_ssh_stderr.txt just contains the warning Warning: Permanently added '[127.0.0.1]:2222' (ECDSA) to the list of known hosts.

sftp-server is installed via cygwin/openssh - before I did that, I ran into another error message, so as this went away after the installation I assume that's not the issue.

I'm not very proficient on windows, merely forced to work with it(and therefore setup a Linux VM to be able to actually do work), so I don't know much in terms of getting information from the Windows host and Virtualbox install to debug the situation.
If you need .

I searched for similar problems anywhere but did not find a solution or a hint on what to do to get the sshfs plugin working on windows, some people seem to have it running, though.

If theres anything I can add to this report to help solving it, please let me know.

[dustymabe]

hi @henning-flmnn, can you tell me what version of vagrant-sshfs you are using? Also what terminal are you using? I typically use cygwin. We have seen issues in the past with other terminals on windows like powershell but I think those issues should be resolved as well.

[henning-flmnn]

@dustymabe thanks - that already solved it! I've been using git bash(the shell provided with the git winodws installer), which I used for everything else before - and which also easily found the sftp-server.

Anyway, switching to the original cygwin Terminal solved the issue.

I added a PR with a note about this: #70

[dustymabe]

ahh. haven't used that shell before for this. it would be good if we can support it.

@hferentschik have you tried using vagrant sshfs with the "windows bash shell" before?

[henning-flmnn]

Hint @dustymabe @hferentschik :

It's not "windows bash" it's "git bash" :)
It's a build of bash that comes with the windows package of git.

Up until today I used the git bash daily, even though for simple stuff for a while, and didnt see any provlems and differences to a bash as I'd expect it to work (apart from some stuff missing that I otherwise have on Linux).

If there's anything I can help you testing, let me know

[dustymabe]

It's not "windows bash" it's "git bash" :)

@henning-flmnn thanks for the clarification - would be nice if that worked too. If you have access to a windows 10 machine It would be interesting to know if this worked there. It would also still be good to know if you are using the latest version of vagrant-sshfs or a previous version.

[henning-flmnn]

@dustymabe Sorry, I dont have a Win 10 available.

And sorry for leaving out the plugin version info, here it comes:

$ vagrant plugin list
vagrant-hostmanager (1.8.5)
vagrant-share (1.1.6, system)
vagrant-sshfs (1.3.0)

[bodyno]

Same issue

[StarWonder67]

It's not "windows bash" it's "git bash" :)

@henning-flmnn thanks for the clarification - would be nice if that worked too. If you have access to a windows 10 machine It would be interesting to know if this worked there. It would also still be good to know if you are using the latest version of vagrant-sshfs or a previous version.

Hi, I am facing the same issue. The vagrant-sshfs version i'm using is 1.3.3. SHould I report the issue somewhere?