Skip to content
New issue

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

Hyper-v launch fails with foreign characters in virtual switch name #9451

Closed
fredrikbaberg opened this issue Feb 6, 2018 · 2 comments
Closed

Comments

@fredrikbaberg
Copy link

fredrikbaberg commented Feb 6, 2018

Vagrant version

Vagrant 2.0.2

Host operating system

Edition: Windows 10 Pro
Version: 1709
OS Build: 16299.214

Language: Swedish

Guest operating system

bento/Ubuntu-16.04

Vagrantfile

# Copy-paste your Vagrantfile here (but don't include sensitive information such as passwords, authentication tokens, or email addresses)
Vagrant.configure("2") do |config|
  config.vm.box = "bento/ubuntu-16.04"
end

Debug output

https://gist.github.com/fredrikbaberg/6192b350f5136fad96a69e2fb5b38552

Expected behavior

Machine should start.

Actual behavior

Machine did not start, due to "Hyper-V was unable to find a virtual switch with name ..."

Steps to reproduce

  1. Have Hyper-V virtual switch with foreign character in name. Note: in Swedish the name of the default switch, which can't be changed, is Standardväxel, which does not seem to be an allowed name.
  2. Create new machine with vagrant init --box bento/ubuntu-16.04
  3. Run vagrant up --provider=hyperv
  4. Creating another switch with similar name gives the same result, creating with only "normal" characters works.

References

chrisroberts added a commit to chrisroberts/vagrant that referenced this issue Apr 27, 2018
Keep track of selected Hyper-V switch using the ID instead of name
to prevent any encoding issues that may occur switching between
PowerShell and Ruby. With the IDs staying consistent, the switch
name can be fetched from the provided ID.

Fixes hashicorp#9679 hashicorp#8794 hashicorp#9451
@chrisroberts
Copy link
Member

Fixed by #9747. Cheers!

@ghost
Copy link

ghost commented Mar 30, 2020

I'm going to lock this issue because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active issues.

If you have found a problem that seems similar to this, please open a new issue and complete the issue template so we can capture all the details necessary to investigate further.

@ghost ghost locked and limited conversation to collaborators Mar 30, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

No branches or pull requests

3 participants