“vagrant up”打印以“==>默认值”开头的数百行：

Question

编辑：我似乎只需要等待。但我仍然想知道这个输出是否对人类有任何意义。

Windows 8.1主机。

我用Git命令行界面取代了cmd，所以我可以使用我熟悉的linux CLI命令。我只是跑以下两个命令，其中第一个跑了没有错误，且其第二似乎依然做的事情：

$ vagrant init ubuntu/trusty64-juju 
$ vagrant up 

第一个命令发生迅速，没有错误。但在第二个命令后，虽然虚拟机启动并在虚拟框中运行（我用user/pass“vagrant”登录），但在Windows Git CLI中，我得到的似乎是无限的输出，如下所示。起初我想也许有些配置还在发生，所以我等了。但30分钟后，它仍在继续。

==> default: : 
==> default: 2 
==> default: 9 
==> default: : 
==> default: 2 
==> default: 3 
==> default: 
==> default: 
==> default: 0 
==> default: : 
==> default: 0 
==> default: 9 
==> default: : 
==> default: 0 
==> default: 5 
==> default: 
==> default: 8 
==> default: 8 
==> default: 2 
==> default: 1 
==> default: 7 

好了哇，几分钟后终于有些事情似乎是发生：

==> default: 6 
==> default: 3 
==> default: k 
==> default: Bootstrapping Juju... 
==> default: Bootstrapping environment "local" 
==> default: Starting new instance for initial state server 
==> default: Building tools to upload (1.25.3.1-trusty-amd64) 
==> default: Installing Juju agent on bootstrap instance 
==> default: Logging to /home/vagrant/.juju/local/cloud-init-output.log on remote host 
==> default: Installing package: curl 
==> default: Installing package: cpu-checker 
==> default: Installing package: bridge-utils 
==> default: Installing package: rsyslog-gnutls 
==> default: Installing package: cloud-utils 
==> default: Installing package: cloud-image-utils 
==> default: Installing package: tmux 
==> default: Bootstrapping Juju machine agent 
==> default: Starting Juju machine agent (juju-agent-vagrant-local) 
==> default: Bootstrap agent installed 
==> default: -> local 
==> default: Waiting for API to become available 
==> default: Waiting for API to become available 
==> default: Waiting for API to become available 
==> default: Bootstrap complete 
==> default: Taking a nap to let state server come up... 
==> default: Added charm "cs:trusty/juju-gui-48" to the environment. 
==> default: Setting up Juju GUI dependencies...this may take a minute. 
==> default: You can find the log in /var/log/juju-setup.log 
==> default: You have not informed bzr of your Launchpad ID, and you must do this to 
==> default: write to Launchpad or access private data. See "bzr help launchpad-login". 
==> default: Branched 25 revisions. 
==> default: Taking a nap to let Juju Gui get setup 
==> default: 
==> default: Setting up transparent redirect for Juju-Gui 
==> default: Redirecting localhost:6079 to 10.0.3.49:80 
==> default: 
==> default: Executing: sudo iptables -t nat -A PREROUTING -p tcp --dport 6079 -j DNAT --to 10.0.3.49:80 
==> default: 
==> default: From your browser on your hosts, you should be able to 
==> default: access the GUI by going to: http://127.0.0.1:6080 
==> default: 
==> default: Your password is: mACsz/qM 
==> default: juju-gui start/running, process 20170 
==> default: juju-gui start/running, process 20170 

我只是不明白UX哲学那里，在用户不知道发生了什么。我以前怎么理解这个输出？

Answer 1

这可能是由于框的作者或者a）以这种方式配置它，或b）没有考虑到将设备输出到终端的特定设置（例如，也许他们希望盒子被引导从POSIX环境而不是Windows Git CLI）。

正如对问题的评论中所建议的那样，与箱主联系或选择其他方框将有助于缩小问题的范围。通常没有问题的常见盒子是由hashicorp（Vagrant的制造商）或标准和流行的Ubuntu或Debian盒子（如ubuntu/trusty64）推出的盒子。