启动 vagrant 时，报错：Stderr: VBoxManage.exe: error: WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the ‘Windows Hypervisor Platform’ feature. (VERR_NEM_NOT_AVAILABLE).
1、启动 vagrant 时，报错：Stderr: VBoxManage.exe: error: WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the ‘Windows Hypervisor Platform’ feature. (VERR_NEM_NOT_AVAILABLE).。如图1
图1
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | $ vagrant upBringing machine 'homestead' up with 'virtualbox' provider...==> homestead: Importing base box 'lc/homestead'...==> homestead: Matching MAC address for NAT networking...==> homestead: Checking if box 'lc/homestead' version '12.0.0' is up to date...==> homestead: Setting the name of the VM: homesteadVagrant is currently configured to create VirtualBox synced folders withthe `SharedFoldersEnableSymlinksCreate` option enabled. If the Vagrantguest is not trusted, you may want to disable this option. For moreinformation on this option, please refer to the VirtualBox manual:This option can be disabled globally with an environment variable: VAGRANT_DISABLE_VBOXSYMLINKCREATE=1or on a per folder basis within the Vagrantfile: 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: Running 'pre-boot' VM customizations...==> homestead: Booting VM...There was an error while executing `VBoxManage`, a CLI used by Vagrantfor controlling VirtualBox. The command and stderr is shown below.Command: ["startvm", "d8b60154-c212-4335-a1ab-6e70cca5e165", "--type", "headless"]Stderr: VBoxManage.exe: error: WHvCapabilityCodeHypervisorPresent is FALSE! Make sure you have enabled the 'Windows Hypervisor Platform' feature. (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、标准错误：VBoxManage.exe：错误：WHvCapabilityCodeHypervisorPresent 为假！ 确保您已启用“Windows Hypervisor Platform”功能。 （VERR_NEM_NOT_AVAILABLE）。右键单击 Windows 按钮并选择“应用和功能”。选择相关设置下右侧的“程序和功能”。选择“打开或关闭 Windows 功能”。选择“Windows 虚拟机监控程序平台”，然后单击“确定”。如图2
图2
3、安装完成后，系统会提示你重新启动计算机。
4、再次启动 vagrant 时，不再报错。如图3
图3
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 | $ 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.htmlBringing machine 'homestead' up with 'virtualbox' provider...==> homestead: Checking if box 'lc/homestead' version '12.0.0' is 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: Running 'pre-boot' VM 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 keyTimed out while waiting for the machine to boot. This means thatVagrant was unable to communicate with the guest machine withinthe configured ("config.vm.boot_timeout" value) time period.If you look above, you should be able to see the error(s) thatVagrant had when attempting to connect to the machine. These errorsare usually good hints as to what may be wrong.If you're using a custom box, make sure that networking is properlyworking and you're able to connect to the machine. It is a commonproblem that networking isn't setup properly in these boxes.Verify that authentication configurations are also setup properly,as well.If the box appears to be booting properly, you may want to increasethe timeout ("config.vm.boot_timeout") value.Administrator@PC MINGW64 ~/Homestead (v13.2.1)$ |
近期评论