Closed mwalczak closed 10 years ago
Hi,
Same error for me ("vagrand reload" work if "nfs" value set to false in VagrantFile...):
vagrant.exe reload
The capability 'nfs_installed' could not be found. This is an internal error that users should never see. Please report a bug.
VagrantFile:
#config.vm.share_folder("symfony", "/vagrant", "./", :nfs => (RUBY_PLATFORM =~ /linux/ or RUBY_PLATFORM =~ /darwin/))
config.vm.share_folder("symfony", "/vagrant", "./", :nfs => true)
Box setup: https://github.com/irmantas/symfony2-vagrant
Os : Win 8.0 x64 Vagrant : v1.5.1
Same error here, but with Win7 - vagrant 1.5.1
I have the same error on Windows 8, Vagrant 1.5.1
At the moment I have no Win 8, could you try it with a lower vagrant version, maybe the problem is not the OS, but the vagrant version.
Thanks, it really works with Vagrant 1.4.3. You think you can fix it for 1.5.1?
Thanks for your feedback I will see that I fix it.
i can confirm the issue. i had the plugin working on 1.4.3 and when I updated to 1.5.1 it stopped working with the same error. Reinstalling the plugin did not help.
OS is Win7 and I don't think the OS Version is the problem.
Confirming:
Windows 7 Home Premium x64 - worked like a charm with vagrant 1.4.3. After update to 1.5.1 it stopped...
UPD: 1.5.0 doesn't work also
Bad news, I can't reproduce the issue. It works for me with version 1.5.1 and 1.5.2dev on Windows 7. Could somebody provide some more information? Maybe then I'm able to find it.
One detail to this is that I cannot see flickering winnfsd window anymore, when using 1.5. I can install it again together with the plugin and test if a process winnfsd is beaing created...
Yeah that would be good. Thanks.
Alex, please check your vagrant version... 1.4.3: https://github.com/mitchellh/vagrant/tree/v1.4.3/plugins/hosts/windows 1.5.1: https://github.com/mitchellh/vagrant/tree/v1.5.1/plugins/hosts/windows
There's new a function called nfs_installed in cap/nfs.rb on the 1.5.1 version... (in linux hosts there are lots of other new functions related to nfs too)
C:\dev>vagrant plugin install vagrant-winnfsd
Installing the 'vagrant-winnfsd' plugin. This can take a few minutes...
Installed the plugin 'vagrant-winnfsd (1.0.5)'!
C:\dev>vagrant up
Bringing machine 'core-01' up with 'virtualbox' provider...
The capability 'nfs_installed' could not be found. This is an internal error
that users should never see. Please report a bug.
My vagrantfile is the one at https://github.com/coreos/coreos-vagrant with uncommented synced_folder line...
Alex, I'm getting the 'nfs_installed' message using the default Vaprobash script on 1.5.2 on Windows 8.1
Same stuff with vagrant 1.5.3 on windows 8.1 x64 machine:
"The capability 'nfs_installed' could not be found. This is an internal error that users should never see. Please report a bug."
Same issue. Windows 8, vagrant 1.5.4
Same issue, vagrant 1.5.1, Win 8.1 x64
Maybe just a stupid idea, but did the author maybe test with Win7/8/8.1 Ultimate? Because in that case we're f***d anyways :)
hi, @GM-Alex , I'm having the same issue The capability 'nfs_installed' could not be found.
:(
Win 8.1 pro x64 vagrant 1.5.3 and
Win 7 enterprise x64 vagrant 1.5.4
how can I help you to fix this? thanks
looks like removing vagrant.d
folder in user's home solves this problem.
but nfs on windows isn't so fast. it's way too behind linux one's :(
actually it's almost equals standard smb performance... or I'm doing something wrong?
You have to check if winnfsd.exe is running in your processes. To check out if it works really start the winnfsd manually (described here: https://bitbucket.org/jankowfsky/winnfsd), connect to the VM via SSH and mount the nfs folder. So you can test it.
@GM-Alex , thanks! you were right. winnfsd.exe was not started.
I made clean vagrant and your plugin installation.
For me it works fine with Vagrant 1.4.3 on win 7 and 8.1
But clean install of Vagrant 1.5.4 and plugin still returns The capability 'nfs_installed' could not be found.
@e-moe So, vagrant 1.5+ is not working, right? @GM-Alex Is this working for you on vagrant 1.5+?
@hurrycaner , yep
1.5.4 not working for me. And 1.6 I think has a bug cause it wants bsdtar on windows.
I also have this issue with 1.5.4 on Windows 7.
+1 confirmed for vagrant 1.6.2
Bug confirmed for vagrant 1.6.2 here too.
\ UPDATE ** I have managed to get the share to work by:
I will try to see if I can further narrow down the problem.
Having the same issue. Vagrant 1.6.2
Please try the now version which has released right now.
Working perfectly now, thanks.
@pgcd Glad to hear that. Are you using Windows 8?
No, Windows 7 but the symptoms were identical to those reported by the others.
@pgcd Could you specify the release type? Win 7 Professional or Win 7 Ultimate?
Thanks a bunch
I'm on Windows 8.1 pro and can confirm the new version seems to be working.
@wmdbMattes Win 7 Pro - as far as I understand, Win 7 Ultimate should have NFS support out-of-the-box, so there might be some difference there due to that, but I'm afraid I can't help with that.
thanks mate
win 8.1 pro x64 working correctrly, thanks!
Win 7 Ultimate should have NFS support out-of-the-box
@pgcd , as far as I know it have only NFS client, not server.
I'v set the nfs_setting in my VagrantFile to test for the plugin existence, and it does. But then, at "Mounting NFS shared folders...", it freezes.
nfs_setting = RUBY_PLATFORM =~ /darwin/ || RUBY_PLATFORM =~ /linux/ || Vagrant.has_plugin?("vagrant-winnfsd")
config.vm.synced_folder "project/", "/var/www/", :nfs => nfs_setting
Seems to me that this is the bug described here. My System : Windows 8.1 Professional, up-to-date. @GM-Alex I don't know how all of this work, but I'd be proud to help if I can with some tests, do not hesitate to ask.
Hi, I've tried to start this plugin working under windows 8, but with no success. On win7 there are files added to vagrant/embedded/bin path, but under win8 files are in user/vagrant.d dir. I don't know whether that's the case, but when I try to enable nfs for my vagrant/puphpet project nfs fails to start with: The capability 'nfs_installed' could not be found. This is an internal error that users should never see. Please report a bug.
Can you help me to solve this problem?