Open an admin Powershell and type the following to disable Hyper-V:
- Code: Select all Expand viewCollapse view
bcdedit /set hypervisorlaunchtype off
Then restart your machine. `vagrant up` will now work with no problem.
bcdedit /set hypervisorlaunchtype off
gera_k wrote:In your .vbox file locate <ExtraData> section and add the following line:
So, do as it says, this is a lot safer:<!--
** DO NOT EDIT THIS FILE.
** If you make changes to this file while any VirtualBox related application
** is running, your changes will be overwritten later, without taking effect.
** Use VBoxManage or the VirtualBox Manager GUI to make changes.
-->
VBoxManage setextradata "<VM Name>" "VBoxInternal/NEM/UseRing0Runloop" 0
I have a couple of questions:/** @cfgm{/NEM/UseRing0Runloop, bool, true}
* Whether to use the ring-0 runloop (if enabled in the build) or the ring-3 one.
* The latter is generally slower. This option serves as a way out in case
* something breaks in the ring-0 loop. */
socratis wrote:I have a couple of questions:
socratis wrote:
- Where did you get that from? It's your first post in the forums and I'm kinda curious of how you got into this advanced level advice...
- You have to really go out of your way to disable a standard way of execution, in this case the ring-0 execution. See the source code reference below...
- Disabling ring-0 execution means that you have to translate the calls to ring-3. Have you measured the performance impact of this action?
gera_k wrote:I managed to make Vbox ver 6.0.10 work on Win1903 build 18362.239 with hyper-v enabled.
In your .vbox file locate <ExtraData> section and add the following line:
<ExtraDataItem name="VBoxInternal/NEM/UseRing0Runloop" value="0"/>
(VERR_NEM_MISSING_KERNEL_API).
VT-x is not available (VERR_VMX_NO_VMX).
Код ошибки: (Error code) E_FAIL (0x80004005)
Компонент: (Component) ConsoleWrap
Интерфейс: (Interface)IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).
Код ошибки: E_FAIL (0x80004005)
Компонент: ConsoleWrap
Интерфейс: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
Callfjor wrote:It took a while to find out everything, but I got VB and Hyper-V working together just fine.
WesleyRast wrote:Open an admin Powershell and type the following to disable Hyper-V:
- Code: Select all Expand viewCollapse view
bcdedit /set hypervisorlaunchtype off
Then restart your machine. `vagrant up` will now work with no problem.
Vasya Pupkin wrote:Not sure why VirtualBox fails to detect such a common issue and report it properly.
Return to VirtualBox on Windows Hosts
Users browsing this forum: Google [Bot], pt58, sterod and 39 guests