Closed davidshq closed 1 year ago
That's an error in vagrant itself, not sure what can be done from our end at the moment 🤔
Yeah...Looks like it is a known issue:
https://github.com/hashicorp/vagrant/issues/12277
And a fix has been merged...
https://github.com/hashicorp/vagrant/pull/12281
I'll see if I can figure out why I'm still seeing the issue...this will be an issue for anyone using latest Vagrant and Hyper-V I think.
When .16 comes out so will the fix, it's just a waiting game
Or...if you are impatient and don't want to downgrade you can edit:
C:\HashiCorp\Vagrant\embedded\gems\2.2.15\gems\vagrant-2.2.15\plugins\guests\linux\cap\mount_smb_shared_folder.rb
Line 23:
From:
mount_device = options[:plugin].capability(:mount_name, options)
To:
mount_device = options[:plugin].capability(:mount_name, name, options)
@davidshq If you are on Hyper-V on WIndows 10 Pro.
Please download Vagrant 2.2.14. do not use Vagrant 2.2.15. There's a problem with the 2.2.15 that's making the SMB stop working for some reason.
There's no need to change the mount options.
@davidshq
ohh i didn't see the last comment u you mention. i had a good feeling that they change the parameters from two to three in 2.2.15.
@benlumia007 @davidshq is this change still necessary for Hyper-V users? I haven't encountered this in my tests in the last year but I haven't been hyper vigilant on that front.
@tomjn Yea i haven't been either, it has been a while since vagrant version has change. so I don't know if this still irrevlant anymore.
did we make the change to the parameter count?
i don't remember, sorry
It's been quite a while since I've used Vagrant on Windows. If I did use it again Hyper-V wouldn't be installed. Hyper-V was only installed so I could use WSL and WSL2 no longer utilizes Hyper-V. Sorry.
I think we should just close this issue for now and if other people still have issues, we can always reopen.
agreed!
Expected Behavior
vagrant up --provider=hyperv
should launch an instance of VVV.Current Behavior
Initial stages of launch are successful. Requests domain username/password. Begins setting up SMB shares and then throws an error regarding "`mount_name': wrong number of arguments (given 2, expected 3) (ArgumentError0", full traceback below.
Possible Solution
Seems like somewhere a necessary argument is not being passed.
Steps to Reproduce (for bugs)
vagrant up --provider=hyperv
This occurs on both the stable and develop branches.
Your Environment
Platform: platform-mingw32 windows
HyperV-Admin HasWinAdminPriv
vagrant-goodhosts vagrant-vbguest monochrome-terminal shared_db_folder_disabled, VVV Path: "C:/vvv"
Vagrant: v2.2.15, VirtualBox: vN/A
Logs