vagrantのエラーについて


# vagrant 接続できません

「vagrant ssh」 は接続できるのにTeraTerm / MySQL Workbench / Tomcat から接続できなくなった

```
vagrant ssh
[vagrant@checkaddress ~]$ ifconfig
eth0      Link encap:Ethernet  HWaddr 08:00:27:4F:B8:06
          inet addr:10.0.2.15  Bcast:10.0.2.255  Mask:255.255.255.0
          inet6 addr: fe80::a00:27ff:fe4f:b806/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:653 errors:0 dropped:0 overruns:0 frame:0
          TX packets:499 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:66890 (65.3 KiB)  TX bytes:64437 (62.9 KiB)

lo        Link encap:Local Loopback
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:0 errors:0 dropped:0 overruns:0 frame:0
          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

# ↑ ↑ ↑ eth1がない！

# ファイルはある？
[vagrant@checkaddress ~]$ cat /etc/sysconfig/network-scripts/ifcfg-eth1
#VAGRANT-BEGIN
# The contents below are automatically generated by Vagrant. Do not modify.
NM_CONTROLLED=no
BOOTPROTO=none
ONBOOT=yes
IPADDR=192.168.33.13
NETMASK=255.255.255.0
DEVICE=eth1
PEERDNS=no
#VAGRANT-END

# ファイルはあるようなので、サービスをリスタートしよう
[vagrant@checkaddress ~]$  sudo service network restart
Shutting down interface eth0:  [  OK  ]

Shutting down loopback interface:  [  OK  ]

Bringing up loopback interface:  [  OK  ]

Bringing up interface eth0:
Determining IP information for eth0... done.
[  OK  ]

Bringing up interface eth1:  Determining if ip address 192.168.33.13 is already in use for device eth1...
[  OK  ]

```
つながりました。

# vagrant up エラー
エラー出力

``` bash
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: Adapter 2: hostonly
==> default: Forwarding ports...
    default: 3307 (guest) => 3307 (host) (adapter 1)
    default: 1337 (guest) => 1337 (host) (adapter 1)
    default: 8910 (guest) => 8910 (host) (adapter 1)
    default: 9134 (guest) => 9134 (host) (adapter 1)
    default: 22 (guest) => 2222 (host) (adapter 1)
==> default: Running 'pre-boot' VM customizations...
==> 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", "9e61ef5e-164d-4a1b-9e49-f815d402146f", "--type", "headless"]

Stderr: VBoxManage.exe: error: The virtual machine 'CheckAddress_default_1514155713339_28565' has te                             rminated unexpectedly during startup with exit code 1 (0x1).  More details may be available in 'C:\U                             sers\AYA\VirtualBox VMs\CheckAddress_default_1514155713339_28565\Logs\VBoxHardening.log'
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
```

VBoxHardening.log

```
624.1930: KnownDllPath: C:\Windows\system32
624.1930: supR3HardenedVmProcessInit: Opening vboxdrv...
624.1930: supR3HardenedWinReadErrorInfoDevice: 'NtQuerySystemInformation/SystemExtendedHandleInformation failed: 0xc0000004
'
624.1930: Error -35 in suplibOsInit! (enmWhat=1)
624.1930: Integrity error (0xe986ffdd/-35): NtQuerySystemInformation/SystemExtendedHandleInformation failed: 0xc0000004
26a8.410: supR3HardenedWinCheckChild: enmRequest=2 rc=-35 enmWhat=1 suplibOsInit: Integrity error (0xe986ffdd/-35): NtQuerySystemInformation/SystemExtendedHandleInformation failed: 0xc0000004

26a8.410: Error -35 in suplibOsInit! (enmWhat=1)
26a8.410: Integrity error (0xe986ffdd/-35): NtQuerySystemInformation/SystemExtendedHandleInformation failed: 0xc0000004
2644.1090: supR3HardNtChildWaitFor[1]: Quitting: ExitCode=0x1 (rcNtWait=0x0, rcNt1=0x0, rcNt2=0x103, rcNt3=0x103, 1898 ms, the end);
```

### 原因
不明

### 解消方法
時間を少しおいて、もう一度試したら普通に起動できた。