When starting vagrant, an error is reported: stderr: vboxmanage.exe: error: whvCapabilityCodeHypervisorPresent is false! make sure you have Enabled theWindows Hypervisor Platformfeature. (verr_nem_not_available).
1. When starting vagrant, an error is reported: stderr: vboxmanage.exe: error: whvCapabilityCodeHypervisorPresent is false! make sure you have enabled theWindows Hypervisor Platformfeature. (verr_nem_not_available).. as shown in Figure 1
Figure 1
$ vagrant up Bringing machinehomesteadup withvirtualboxprovider... ==> Homestead: Importing Base BoxLC/Homestead... ==> Homestead: Matching mac address for nat networking... ==> Homestead: checking if boxLC/Homesteadversion12.0.0is up to date... ==> Homestead: Setting the name of the VM: Homestead Vagrant is currently configured folders with The `SharedFoldersEnableSyMlinkScreate` Option Enabled. If the vagrant Guest is not trusted, you may want to disable this option. Information on this option, please refer to the virtualbox manual: https://www.virtualbox.org/manual/ch04.html#SharedFolders This option can be disabled globally with an environment variable: vagrant_disable_vboxsymlinkcreate=1 or on a per folder basis file: config.vm.synced_folder/host/path,/guest/path, sharedFoldersEnableSyMlinkScreate: False ==> Homestead: Clearing any previously set network interfaces... ==> Homestead: Preparing network interfaces based on configuration... Homestead: Adapter 1: NAT Homestead: adapter 2: hostonly ==> Homestead: forwarding ports... Homestead: 80 (guest) => 8000 (host) (adapter 1) Homestead: 443 (guest) => 44300 (host) (adapter 1) Homestead: 22 (guest) => 2222 (host) (adapter 1) ==> homestead: runningpre-bootVM Customizations... ==> Homestead: Booting VM... There was an error while executing `vboxmanage`, a cli used by vagrant For controlled virtualbox. The command and stderr is show below. command:["startvm", "d8b60154-c212-4335-a1ab-6e70cca5e165", "--type", "headless"] stderr: vboxmanage.exe: Error: whvCapabilityCodeHypervisorpresent is false! make sure you have enabled theWindows Hypervisor Platformfeature. (verr_nem_not_available). vboxmanage.exe: error: vt-x is not available (VERR_VMX_NO_VMX) vboxmanage.exe: error: details: code e_fail (0x80004005), component consolewrap, interface iconsole
2. Standard error: vboxmanage.exe: error: whvCapabilityCodeHypervisorPresent is false! Make sure you have the “Windows Hypervisor Platform” feature enabled. (verr_nem_not_available). Right-click the Windows button and select “Apps and Features”. Select “Programs and Functions” on the right under the relevant settings. Select “Turn on or off Windows Features”. Select the Windows Virtual Machine Monitoring Program Platform and click OK. as shown in Figure 2
Figure 2
3. After the installation is complete, the system will prompt you to restart the computer.
4. When vagrant is started again, an error will not be reported. as shown in Figure 3
Figure 3
$ vagrant up
==> vagrant: a new version of vagrant is available: 2.3.0 (Installed version: 2.2.19)!
==> vagrant: to upgrade visit: https://www.vagrantup.com/downloads.html
Bringing machinehomesteadup withvirtualboxprovider...
==> Homestead: checking if boxLC/Homesteadversion12.0.0is up to date...
==> Homestead: Clearing any previously set forwarded ports...
==> Homestead: Clearing any previously set network interfaces...
==> Homestead: Preparing network interfaces based on configuration...
Homestead: Adapter 1: NAT
Homestead: adapter 2: hostonly
==> Homestead: forwarding ports...
Homestead: 80 (guest) => 8000 (host) (adapter 1)
Homestead: 443 (guest) => 44300 (host) (adapter 1)
Homestead: 22 (guest) => 2222 (host) (adapter 1)
==> homestead: runningpre-bootVM Customizations...
==> Homestead: Booting VM...
==> Homestead: Waiting for machine to boot. This may take a few minutes...
Homestead: ssh address: 127.0.0.1:2222
Homestead: ssh username: vagrant
Homestead: SSH Auth Method: Private Key
Timed out while waiting for the machine to boot. This means that
Vagrant was unable to communicate with the guest within
The configured ("config.vm.boot_timeout" value) time period.
If you look above, you should be able to see the error(s) that
Vagrant had when attempting to connect to the machine. These errors
are usually good hints as to what may be wrong.
if youRe using a custom box, make sure that network is properly
working and youReable to connect to the machine. It is a common
Problem that networking isnT setup up properly in these boxes.
verify that authentication configurations are also setup properly,
as well.
If the box appeared to be booting properly, you may want to increase
the timeout ("config.vm.boot_timeout") value.
Administrator@PC mingw64 ~/homestead (v13.2.1)
$
