質問編集履歴
6
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -5,6 +5,8 @@
|
|
|
5
5
|
Windows10にて、vagrant upをしてvirtualboxの仮想環境でRuby on Railsの動作確認をしていたのですが、
|
|
6
6
|
|
|
7
7
|
急にvagrant upでエラーが出てしまうようになりました。
|
|
8
|
+
|
|
9
|
+
|
|
8
10
|
|
|
9
11
|
|
|
10
12
|
|
5
エラーメッセージ更新
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -22,40 +22,18 @@
|
|
|
22
22
|
|
|
23
23
|
```
|
|
24
24
|
|
|
25
|
-
|
|
25
|
+
There was an error while executing `VBoxManage`, a CLI used by Vagrant
|
|
26
26
|
|
|
27
|
-
==> default: Clearing any previously set forwarded ports...
|
|
28
|
-
|
|
29
|
-
Vagrant cannot forward the specified ports on this VM, since they
|
|
30
|
-
|
|
31
|
-
|
|
27
|
+
for controlling VirtualBox. The command and stderr is shown below.
|
|
32
|
-
|
|
33
|
-
on these ports. The forwarded port to 3000 is already in use
|
|
34
|
-
|
|
35
|
-
on the host machine.
|
|
36
28
|
|
|
37
29
|
|
|
38
30
|
|
|
39
|
-
To fix this, modify your current project's Vagrantfile to use another
|
|
40
|
-
|
|
41
|
-
|
|
31
|
+
Command: ["startvm", "d8bb505c-4e85-4031-99e9-86a8e7a83615", "--type", "headless"]
|
|
42
32
|
|
|
43
33
|
|
|
44
34
|
|
|
45
|
-
|
|
35
|
+
Stderr: VBoxManage.exe: error: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)
|
|
46
36
|
|
|
47
|
-
|
|
48
|
-
|
|
49
|
-
Sometimes, Vagrant will attempt to auto-correct this for you. In this
|
|
50
|
-
|
|
51
|
-
case, Vagrant was unable to. This is usually because the guest machine
|
|
52
|
-
|
|
53
|
-
|
|
37
|
+
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
|
|
54
|
-
|
|
55
|
-
try 'vagrant reload' (equivalent of running a halt followed by an up)
|
|
56
|
-
|
|
57
|
-
so vagrant can attempt to auto-correct this upon booting. Be warned
|
|
58
|
-
|
|
59
|
-
that any unsaved work might be lost.
|
|
60
38
|
|
|
61
39
|
```
|
4
エラーメッセージ更新
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -24,48 +24,38 @@
|
|
|
24
24
|
|
|
25
25
|
Bringing machine 'default' up with 'virtualbox' provider...
|
|
26
26
|
|
|
27
|
-
==> default:
|
|
27
|
+
==> default: Clearing any previously set forwarded ports...
|
|
28
28
|
|
|
29
|
-
|
|
29
|
+
Vagrant cannot forward the specified ports on this VM, since they
|
|
30
30
|
|
|
31
|
-
|
|
31
|
+
would collide with some other application that is already listening
|
|
32
32
|
|
|
33
|
-
de
|
|
33
|
+
on these ports. The forwarded port to 3000 is already in use
|
|
34
34
|
|
|
35
|
-
default: SSH username: vagrant
|
|
36
|
-
|
|
37
|
-
|
|
35
|
+
on the host machine.
|
|
38
|
-
|
|
39
|
-
Timed out while waiting for the machine to boot. This means that
|
|
40
|
-
|
|
41
|
-
Vagrant was unable to communicate with the guest machine within
|
|
42
|
-
|
|
43
|
-
the configured ("config.vm.boot_timeout" value) time period.
|
|
44
36
|
|
|
45
37
|
|
|
46
38
|
|
|
47
|
-
|
|
39
|
+
To fix this, modify your current project's Vagrantfile to use another
|
|
48
40
|
|
|
49
|
-
|
|
41
|
+
port. Example, where '1234' would be replaced by a unique host port:
|
|
50
|
-
|
|
51
|
-
are usually good hints as to what may be wrong.
|
|
52
42
|
|
|
53
43
|
|
|
54
44
|
|
|
55
|
-
If you're using a custom box, make sure that networking is properly
|
|
56
|
-
|
|
57
|
-
working and you're able to connect to the machine. It is a common
|
|
58
|
-
|
|
59
|
-
|
|
45
|
+
config.vm.network :forwarded_port, guest: 3000, host: 1234
|
|
60
|
-
|
|
61
|
-
Verify that authentication configurations are also setup properly,
|
|
62
|
-
|
|
63
|
-
as well.
|
|
64
46
|
|
|
65
47
|
|
|
66
48
|
|
|
67
|
-
|
|
49
|
+
Sometimes, Vagrant will attempt to auto-correct this for you. In this
|
|
68
50
|
|
|
51
|
+
case, Vagrant was unable to. This is usually because the guest machine
|
|
52
|
+
|
|
53
|
+
is in a state which doesn't allow modifying port forwarding. You could
|
|
54
|
+
|
|
55
|
+
try 'vagrant reload' (equivalent of running a halt followed by an up)
|
|
56
|
+
|
|
69
|
-
t
|
|
57
|
+
so vagrant can attempt to auto-correct this upon booting. Be warned
|
|
58
|
+
|
|
59
|
+
that any unsaved work might be lost.
|
|
70
60
|
|
|
71
61
|
```
|
3
エラーメッセージ更新
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -36,30 +36,36 @@
|
|
|
36
36
|
|
|
37
37
|
default: SSH auth method: private key
|
|
38
38
|
|
|
39
|
-
T
|
|
39
|
+
Timed out while waiting for the machine to boot. This means that
|
|
40
40
|
|
|
41
|
-
|
|
41
|
+
Vagrant was unable to communicate with the guest machine within
|
|
42
42
|
|
|
43
|
-
|
|
43
|
+
the configured ("config.vm.boot_timeout" value) time period.
|
|
44
|
-
|
|
45
|
-
properly and try again.
|
|
46
44
|
|
|
47
45
|
|
|
48
46
|
|
|
49
|
-
If
|
|
47
|
+
If you look above, you should be able to see the error(s) that
|
|
50
48
|
|
|
51
|
-
|
|
49
|
+
Vagrant had when attempting to connect to the machine. These errors
|
|
52
50
|
|
|
53
|
-
|
|
51
|
+
are usually good hints as to what may be wrong.
|
|
54
|
-
|
|
55
|
-
For example, if you're using VirtualBox, run `vagrant up` while the
|
|
56
|
-
|
|
57
|
-
VirtualBox GUI is open.
|
|
58
52
|
|
|
59
53
|
|
|
60
54
|
|
|
61
|
-
|
|
55
|
+
If you're using a custom box, make sure that networking is properly
|
|
62
56
|
|
|
57
|
+
working and you're able to connect to the machine. It is a common
|
|
58
|
+
|
|
59
|
+
problem that networking isn't setup properly in these boxes.
|
|
60
|
+
|
|
61
|
+
Verify that authentication configurations are also setup properly,
|
|
62
|
+
|
|
63
|
+
as well.
|
|
64
|
+
|
|
65
|
+
|
|
66
|
+
|
|
63
|
-
|
|
67
|
+
If the box appears to be booting properly, you may want to increase
|
|
68
|
+
|
|
69
|
+
the timeout ("config.vm.boot_timeout") value.
|
|
64
70
|
|
|
65
71
|
```
|
2
エラーコード編集
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -24,38 +24,42 @@
|
|
|
24
24
|
|
|
25
25
|
Bringing machine 'default' up with 'virtualbox' provider...
|
|
26
26
|
|
|
27
|
-
==> default: Clearing any previously set forwarded ports...
|
|
28
|
-
|
|
29
|
-
==> default: Clearing any previously set network interfaces...
|
|
30
|
-
|
|
31
|
-
==> default: Preparing network interfaces based on configuration...
|
|
32
|
-
|
|
33
|
-
default: Adapter 1: nat
|
|
34
|
-
|
|
35
|
-
default: Adapter 2: hostonly
|
|
36
|
-
|
|
37
|
-
==> default:
|
|
27
|
+
==> default: Resuming suspended VM...
|
|
38
|
-
|
|
39
|
-
default: 3000 (guest) => 3000 (host) (adapter 1)
|
|
40
|
-
|
|
41
|
-
default: 22 (guest) => 2222 (host) (adapter 1)
|
|
42
28
|
|
|
43
29
|
==> default: Booting VM...
|
|
44
30
|
|
|
45
|
-
|
|
31
|
+
==> default: Waiting for machine to boot. This may take a few minutes...
|
|
46
32
|
|
|
33
|
+
default: SSH address: 127.0.0.1:2222
|
|
34
|
+
|
|
35
|
+
default: SSH username: vagrant
|
|
36
|
+
|
|
37
|
+
default: SSH auth method: private key
|
|
38
|
+
|
|
47
|
-
|
|
39
|
+
The guest machine entered an invalid state while waiting for it
|
|
40
|
+
|
|
41
|
+
to boot. Valid states are 'restoring, running'. The machine is in the
|
|
42
|
+
|
|
43
|
+
'paused' state. Please verify everything is configured
|
|
44
|
+
|
|
45
|
+
properly and try again.
|
|
48
46
|
|
|
49
47
|
|
|
50
48
|
|
|
49
|
+
If the provider you're using has a GUI that comes with it,
|
|
50
|
+
|
|
51
|
+
it is often helpful to open that and watch the machine, since the
|
|
52
|
+
|
|
53
|
+
GUI often has more helpful error messages than Vagrant can retrieve.
|
|
54
|
+
|
|
51
|
-
|
|
55
|
+
For example, if you're using VirtualBox, run `vagrant up` while the
|
|
56
|
+
|
|
57
|
+
VirtualBox GUI is open.
|
|
52
58
|
|
|
53
59
|
|
|
54
60
|
|
|
55
|
-
|
|
61
|
+
The primary issue for this error is that the provider you're using
|
|
56
62
|
|
|
57
|
-
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
|
|
58
|
-
|
|
59
|
-
|
|
63
|
+
is not properly configured. This is very rarely a Vagrant issue.
|
|
60
64
|
|
|
61
65
|
```
|
1
エラーメッセージ更新
test
CHANGED
|
File without changes
|
test
CHANGED
|
@@ -26,24 +26,6 @@
|
|
|
26
26
|
|
|
27
27
|
==> default: Clearing any previously set forwarded ports...
|
|
28
28
|
|
|
29
|
-
==> default: Vagrant has detected a configuration issue which exposes a
|
|
30
|
-
|
|
31
|
-
==> default: vulnerability with the installed version of VirtualBox. The
|
|
32
|
-
|
|
33
|
-
==> default: current guest is configured to use an E1000 NIC type for a
|
|
34
|
-
|
|
35
|
-
==> default: network adapter which is vulnerable in this version of VirtualBox.
|
|
36
|
-
|
|
37
|
-
==> default: Ensure the guest is trusted to use this configuration or update
|
|
38
|
-
|
|
39
|
-
==> default: the NIC type using one of the methods below:
|
|
40
|
-
|
|
41
|
-
==> default:
|
|
42
|
-
|
|
43
|
-
==> default: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
|
|
44
|
-
|
|
45
|
-
==> default: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
|
|
46
|
-
|
|
47
29
|
==> default: Clearing any previously set network interfaces...
|
|
48
30
|
|
|
49
31
|
==> default: Preparing network interfaces based on configuration...
|
|
@@ -70,8 +52,10 @@
|
|
|
70
52
|
|
|
71
53
|
|
|
72
54
|
|
|
73
|
-
Stderr: VBoxManage.exe: error:
|
|
55
|
+
Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).
|
|
74
56
|
|
|
57
|
+
VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
|
|
58
|
+
|
|
75
|
-
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component
|
|
59
|
+
VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
|
|
76
60
|
|
|
77
61
|
```
|