Vagrant “如何修复”；“流浪者不起来”；Windows中的错误

以下是我在Windows中运行

vagrant up

时的日志：

There was a problem after restarting the server Launch logs

Bringing machine 'default' up with 'virtualbox' provider...
==> default: Checking if box 'ubuntu/xenial64' version '20190530.3.0' is up to date...
==> default: A newer version of the box 'ubuntu/xenial64' for provider 'virtualbox' is
==> default: available! You currently have version '20190530.3.0'. The latest is version
==> default: '20190731.0.0'. Run `vagrant box update` to update.
C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/plugins/providers/virtualbox/driver/version_5_0.rb:593:in `split': invalid byte sequence in UTF-8 (ArgumentError)
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/plugins/providers/virtualbox/driver/version_5_0.rb:593:in `read_used_ports'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/plugins/providers/virtualbox/action/prepare_forwarded_port_collision_params.rb:12:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/env_set.rb:19:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Users/dp/.vagrant.d/gems/2.4.6/gems/vagrant-hostmanager-1.8.9/lib/vagrant-hostmanager/action/update_all.rb:24:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/before_trigger.rb:23:in `call'        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/after_trigger.rb:26:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/warden.rb:50:in `call'
        from C:/Vagrant/embedded/gems/2.2.5/gems/vagrant-2.2.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'

---

这是一个众所周知的问题。请检查以下内容：

如果您有非拉丁字母的已注册VM（在virtualbox中）的图像文件路径，则会出现此错误。 这可能是一个您无法启动的图像，但它只是出现在Virtualbox中。在Virtualbox中，这些虚拟机将完美运行。所以这个问题不是针对Virtualbox，而是针对Vagrant/Ruby

因此，目前的解决办法是：

检查Virtualbox中的所有图像 并更正所有具有非拉丁/奇怪符号的路径。您可以选择删除这样的图像。 如上所述，您可以通过以下方式检查属性：

VBoxManage list vms
VBoxManage showvminfo <vm-guid> --machinereadable

VBoxManage列表虚拟机
VBoxManage showvminfo--机器可安装

这是一个已知的问题。请检查以下内容：

如果您有非拉丁字母的已注册VM（在virtualbox中）的图像文件路径，则会出现此错误。 这可能是一个您无法启动的图像，但它只是出现在Virtualbox中。在Virtualbox中，这些虚拟机将完美运行。所以这个问题不是针对Virtualbox，而是针对Vagrant/Ruby

因此，目前的解决办法是：

检查Virtualbox中的所有图像 并更正所有具有非拉丁/奇怪符号的路径。您可以选择删除这样的图像。 如上所述，您可以通过以下方式检查属性：

VBoxManage list vms
VBoxManage showvminfo <vm-guid> --machinereadable

VBoxManage列表虚拟机
VBoxManage showvminfo--机器可安装

如果您可以复制控制台输出并将其粘贴到此处而不是图像，阅读起来会更容易。剪贴板和屏幕阅读器用户也会对此表示感谢。添加了控制台输出，我运行“vagrant box update”，但在控制台中看到相同的输出。如果您可以复制控制台输出并将其粘贴到此处，而不是图像，则更容易阅读。剪贴板和屏幕阅读器用户也会对此表示感谢。添加了控制台输出，我运行“vagrant box update”，但在控制台中看到相同的输出