We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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 version: 2.4.3 Host OS: Windows 10
Target Hypervisor: Hyper-V + ESXi Target VM: Windows 10
Communicator type: WinRM
Multiple users are encountering issues connecting to VMs using WinRM. I think the issue is caused by the new version of the dependency WinRM.
Vagrant should try to establish a WinRM connection according to the parameters provided in vagrant file (timeout, retries,...).
Vagrant exists with the error:
An error occurred executing a remote WinRM command. Shell: Cmd Command: hostname Message: Blocking operation timed out!
# not relevant in this use-case --> no special config required
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Vagrant version: 2.4.3
Host OS: Windows 10
Target Hypervisor: Hyper-V + ESXi
Target VM: Windows 10
Communicator type: WinRM
Debug output
Multiple users are encountering issues connecting to VMs using WinRM. I think the issue is caused by the new version of the dependency WinRM.
Expected behavior
Vagrant should try to establish a WinRM connection according to the parameters provided in vagrant file (timeout, retries,...).
Actual behavior
Vagrant exists with the error:
Steps to reproduce
Vagrantfile
# not relevant in this use-case --> no special config required
The text was updated successfully, but these errors were encountered: