Vagrant 1.7.4: Unable to mount shared folder

127 views
Skip to first unread message

Matthew Wilson

unread,
Aug 13, 2015, 10:26:14 AM8/13/15
to Vagrant

I'm using vagrant on windows 8, with the hyper-v provider starting a windows server 2012 box.

Before I updated to vagrant 1.7.4 I was on version 1.7.2, and everything worked.

But after updating I am getting an error when it is trying to mount the shared folder:


The following WinRM command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

cmdkey /add:xxx.xxx.xxx.xxx /user:DOMAIN\user /pass:Password

Stdout from the command:



Stderr from the command:

Exception calling "RegisterTaskDefinition" with "7" argument(s): "The user
name or password is incorrect. (Exception from HRESULT: 0x8007052E)"
At C:\tmp\vagrant-elevated-shell.ps1:58 char:1
+ $folder.RegisterTaskDefinition($task_name, $task, 6, $username, $password,
1, $n ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
~~~
+ CategoryInfo          : NotSpecified: (:) [], MethodInvocationException
+ FullyQualifiedErrorId : ComMethodTargetInvocation


I have replaced the details from the line:


cmdkey /add:xxx.xxx.xxx.xxx /user:DOMAIN\user /pass:Password


With placeholders for obvious reasons. I did try and run the command above in the VM and I get the following output:


CMDKEY: Credential added successfully.


So I assume it is working correctly. Is there something broken or changed between 1.7.2 and 1.7.4?

Alvaro Miranda Aguilera

unread,
Aug 13, 2015, 8:41:49 PM8/13/15
to vagra...@googlegroups.com
Can you share a Vagranfile to reproduce this?

I have seen people reporting this, however without a reproductable
test case is hard to get someone to review.

Thanks
Alvaro.
> --
> 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+...@googlegroups.com.
> To view this discussion on the web visit
> https://groups.google.com/d/msgid/vagrant-up/ecabcb5d-1b93-4ef8-9849-cc28df561b6a%40googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.

dragon788

unread,
Aug 14, 2015, 11:05:20 AM8/14/15
to Vagrant
They added WinRM support as a communicator directly in newer versions I thought, and they added it to Packer as well, so I'm not sure if that's what has changed, that it is trying to use WinRM rather than SSH and running into trouble. Like Alvaro mentioned, please share your Vagrantfile or the github repo with the Vagrantfile you modified to make yours.
Reply all
Reply to author
Forward
0 new messages