虚拟机无法启动情况一：
E:\work\wily64>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
There was an error while executing `VBoxManage`, a CLI used by Vagrant
for controlling VirtualBox. The command and stderr is shown below.
Command: ["startvm", "8ccab16c-34bb-4fae-8772-231ef763c71d", "--type", "headless"]
Stderr: VBoxManage.exe: error: The virtual machine 'work_default_1538812794432_81642' has terminated unexpectedly during startup with exit code 1 (0x1). More details may be available in 'C:\Users\liubeibei\VirtualBox VMs\work_default_1538812794432_81642\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
虚拟机无法启动情况二：
E:\work\wily64>vagrant up
Bringing machine 'default' up with 'virtualbox' provider...
==> default: Clearing any previously set forwarded ports...
==> default: Clearing any previously set network interfaces...
==> default: Preparing network interfaces based on configuration...
default: Adapter 1: nat
==> default: Forwarding ports...
default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Booting VM...
==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.
If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.
The primary issue for this error is that the provider you're using
is not properly configured. This is very rarely a Vagrant issue.
Win10下安装VirtualBox，要么可以打开VirtualBox却启动不了虚拟机，要么就打不开VirtualBox，说是NIDS6的bug问题，参考了他们的解决方法https://stackoverflow.com/questions/33725779/failed-to-open-create-the-internal-network-vagrant-on-windows10，没有解决我的问题，最后安装vagrant_2.1.5_x86_64.msi + VirtualBox-5.2.18-124319-Win.exe完美解决问题。