teratail header banner
teratail header banner
質問するログイン新規登録

質問編集履歴

6

2020/11/18 22:28

投稿

GHOST-CHERRY
GHOST-CHERRY

スコア2

title CHANGED
File without changes
body CHANGED
@@ -3,6 +3,7 @@
3
3
  Windows10にて、vagrant upをしてvirtualboxの仮想環境でRuby on Railsの動作確認をしていたのですが、
4
4
  急にvagrant upでエラーが出てしまうようになりました。
5
5
 
6
+
6
7
  該当する解決策が見当たらなかったので、分かる方教えてほしいです!
7
8
 
8
9
  (Windows10のプログラムを最新のものに更新してからなりました)

5

エラーメッセージ更新

2020/11/18 22:28

投稿

GHOST-CHERRY
GHOST-CHERRY

スコア2

title CHANGED
File without changes
body CHANGED
@@ -10,22 +10,11 @@
10
10
  ### 発生している問題・エラーメッセージ
11
11
 
12
12
  ```
13
- Bringing machine 'default' up with 'virtualbox' provider...
14
- ==> default: Clearing any previously set forwarded ports...
15
- Vagrant cannot forward the specified ports on this VM, since they
13
+ There was an error while executing `VBoxManage`, a CLI used by Vagrant
16
- would collide with some other application that is already listening
14
+ for controlling VirtualBox. The command and stderr is shown below.
17
- on these ports. The forwarded port to 3000 is already in use
18
- on the host machine.
19
15
 
20
- To fix this, modify your current project's Vagrantfile to use another
21
- port. Example, where '1234' would be replaced by a unique host port:
16
+ Command: ["startvm", "d8bb505c-4e85-4031-99e9-86a8e7a83615", "--type", "headless"]
22
17
 
23
- config.vm.network :forwarded_port, guest: 3000, host: 1234
24
-
25
- Sometimes, Vagrant will attempt to auto-correct this for you. In this
18
+ Stderr: VBoxManage.exe: error: Call to WHvSetupPartition failed: ERROR_SUCCESS (Last=0xc000000d/87) (VERR_NEM_VM_CREATE_FAILED)
26
- case, Vagrant was unable to. This is usually because the guest machine
27
- is in a state which doesn't allow modifying port forwarding. You could
19
+ VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
28
- try 'vagrant reload' (equivalent of running a halt followed by an up)
29
- so vagrant can attempt to auto-correct this upon booting. Be warned
30
- that any unsaved work might be lost.
31
20
  ```

4

エラーメッセージ更新

2020/11/16 15:55

投稿

GHOST-CHERRY
GHOST-CHERRY

スコア2

title CHANGED
File without changes
body CHANGED
@@ -11,26 +11,21 @@
11
11
 
12
12
  ```
13
13
  Bringing machine 'default' up with 'virtualbox' provider...
14
- ==> default: Resuming suspended VM...
15
- ==> default: Booting VM...
16
- ==> default: Waiting for machine to boot. This may take a few minutes...
14
+ ==> default: Clearing any previously set forwarded ports...
17
- default: SSH address: 127.0.0.1:2222
18
- default: SSH username: vagrant
19
- default: SSH auth method: private key
20
- Timed out while waiting for the machine to boot. This means that
21
- Vagrant was unable to communicate with the guest machine within
15
+ Vagrant cannot forward the specified ports on this VM, since they
22
- the configured ("config.vm.boot_timeout" value) time period.
16
+ would collide with some other application that is already listening
17
+ on these ports. The forwarded port to 3000 is already in use
18
+ on the host machine.
23
19
 
24
- If you look above, you should be able to see the error(s) that
20
+ To fix this, modify your current project's Vagrantfile to use another
25
- Vagrant had when attempting to connect to the machine. These errors
21
+ port. Example, where '1234' would be replaced by a unique host port:
26
- are usually good hints as to what may be wrong.
27
22
 
28
- If you're using a custom box, make sure that networking is properly
29
- working and you're able to connect to the machine. It is a common
30
- problem that networking isn't setup properly in these boxes.
23
+ config.vm.network :forwarded_port, guest: 3000, host: 1234
31
- Verify that authentication configurations are also setup properly,
32
- as well.
33
24
 
25
+ Sometimes, Vagrant will attempt to auto-correct this for you. In this
34
- If the box appears to be booting properly, you may want to increase
26
+ case, Vagrant was unable to. This is usually because the guest machine
27
+ is in a state which doesn't allow modifying port forwarding. You could
28
+ try 'vagrant reload' (equivalent of running a halt followed by an up)
35
- the timeout ("config.vm.boot_timeout") value.
29
+ so vagrant can attempt to auto-correct this upon booting. Be warned
30
+ that any unsaved work might be lost.
36
31
  ```

3

エラーメッセージ更新

2020/11/16 09:26

投稿

GHOST-CHERRY
GHOST-CHERRY

スコア2

title CHANGED
File without changes
body CHANGED
@@ -17,17 +17,20 @@
17
17
  default: SSH address: 127.0.0.1:2222
18
18
  default: SSH username: vagrant
19
19
  default: SSH auth method: private key
20
+ Timed out while waiting for the machine to boot. This means that
20
- The guest machine entered an invalid state while waiting for it
21
+ Vagrant was unable to communicate with the guest machine within
21
- to boot. Valid states are 'restoring, running'. The machine is in the
22
+ the configured ("config.vm.boot_timeout" value) time period.
22
- 'paused' state. Please verify everything is configured
23
- properly and try again.
24
23
 
25
- If the provider you're using has a GUI that comes with it,
24
+ If you look above, you should be able to see the error(s) that
26
- it is often helpful to open that and watch the machine, since the
25
+ Vagrant had when attempting to connect to the machine. These errors
27
- GUI often has more helpful error messages than Vagrant can retrieve.
26
+ are usually good hints as to what may be wrong.
28
- For example, if you're using VirtualBox, run `vagrant up` while the
29
- VirtualBox GUI is open.
30
27
 
28
+ If you're using a custom box, make sure that networking is properly
31
- The primary issue for this error is that the provider you're using
29
+ working and you're able to connect to the machine. It is a common
30
+ problem that networking isn't setup properly in these boxes.
31
+ Verify that authentication configurations are also setup properly,
32
+ as well.
33
+
32
- is not properly configured. This is very rarely a Vagrant issue.
34
+ If the box appears to be booting properly, you may want to increase
35
+ the timeout ("config.vm.boot_timeout") value.
33
36
  ```

2

エラーコード編集

2020/11/15 15:11

投稿

GHOST-CHERRY
GHOST-CHERRY

スコア2

title CHANGED
File without changes
body CHANGED
@@ -11,21 +11,23 @@
11
11
 
12
12
  ```
13
13
  Bringing machine 'default' up with 'virtualbox' provider...
14
- ==> default: Clearing any previously set forwarded ports...
15
- ==> default: Clearing any previously set network interfaces...
16
- ==> default: Preparing network interfaces based on configuration...
17
- default: Adapter 1: nat
18
- default: Adapter 2: hostonly
19
- ==> default: Forwarding ports...
14
+ ==> default: Resuming suspended VM...
20
- default: 3000 (guest) => 3000 (host) (adapter 1)
21
- default: 22 (guest) => 2222 (host) (adapter 1)
22
15
  ==> default: Booting VM...
16
+ ==> default: Waiting for machine to boot. This may take a few minutes...
17
+ default: SSH address: 127.0.0.1:2222
18
+ default: SSH username: vagrant
19
+ default: SSH auth method: private key
23
- There was an error while executing `VBoxManage`, a CLI used by Vagrant
20
+ The guest machine entered an invalid state while waiting for it
21
+ to boot. Valid states are 'restoring, running'. The machine is in the
24
- for controlling VirtualBox. The command and stderr is shown below.
22
+ 'paused' state. Please verify everything is configured
23
+ properly and try again.
25
24
 
25
+ If the provider you're using has a GUI that comes with it,
26
+ it is often helpful to open that and watch the machine, since the
27
+ GUI often has more helpful error messages than Vagrant can retrieve.
26
- Command: ["startvm", "d8bb505c-4e85-4031-99e9-86a8e7a83615", "--type", "headless"]
28
+ For example, if you're using VirtualBox, run `vagrant up` while the
29
+ VirtualBox GUI is open.
27
30
 
28
- Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).
29
- VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
31
+ The primary issue for this error is that the provider you're using
30
- VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
32
+ is not properly configured. This is very rarely a Vagrant issue.
31
33
  ```

1

エラーメッセージ更新

2020/11/15 13:00

投稿

GHOST-CHERRY
GHOST-CHERRY

スコア2

title CHANGED
File without changes
body CHANGED
@@ -12,15 +12,6 @@
12
12
  ```
13
13
  Bringing machine 'default' up with 'virtualbox' provider...
14
14
  ==> default: Clearing any previously set forwarded ports...
15
- ==> default: Vagrant has detected a configuration issue which exposes a
16
- ==> default: vulnerability with the installed version of VirtualBox. The
17
- ==> default: current guest is configured to use an E1000 NIC type for a
18
- ==> default: network adapter which is vulnerable in this version of VirtualBox.
19
- ==> default: Ensure the guest is trusted to use this configuration or update
20
- ==> default: the NIC type using one of the methods below:
21
- ==> default:
22
- ==> default: https://www.vagrantup.com/docs/virtualbox/configuration.html#default-nic-type
23
- ==> default: https://www.vagrantup.com/docs/virtualbox/networking.html#virtualbox-nic-type
24
15
  ==> default: Clearing any previously set network interfaces...
25
16
  ==> default: Preparing network interfaces based on configuration...
26
17
  default: Adapter 1: nat
@@ -34,6 +25,7 @@
34
25
 
35
26
  Command: ["startvm", "d8bb505c-4e85-4031-99e9-86a8e7a83615", "--type", "headless"]
36
27
 
37
- Stderr: VBoxManage.exe: error: The virtual machine 'vagrant_default_1593512268194_17479' has terminated unexpectedly during startup with exit code -1073741819 (0xc0000005)
28
+ Stderr: VBoxManage.exe: error: Failed to open/create the internal network 'HostInterfaceNetworking-VirtualBox Host-Only Ethernet Adapter #2' (VERR_INTNET_FLT_IF_NOT_FOUND).
29
+ VBoxManage.exe: error: Failed to attach the network LUN (VERR_INTNET_FLT_IF_NOT_FOUND)
38
- VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component MachineWrap, interface IMachine
30
+ VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole
39
31
  ```