virtualbox Raw-mode is unavailable courtesy of Hyper-V windows 10

后端 未结 20 1752
清酒与你
清酒与你 2020-12-07 07:28

issues:

Failed to open a session for the virtual machine ubuntu.

Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).

Resul         


        
相关标签:
20条回答
  • 2020-12-07 07:38

    You may need to disable the hypervisor.

    So, follow the next steps:

    1) Open command prompt as Administrator

    2) Run bcdedit to check hypervisor status:

    bcdedit
    

    3) Check hypervisor launch type:

    4) If is set to auto then disable it:

    bcdedit /set hypervisorlaunchtype off
    

    5) Reboot host machine and launch VirtualBox again

    0 讨论(0)
  • 2020-12-07 07:38

    Finally I can fix the issue now.

    At first, we need to identify or understand the problem which mostly people not really findout, my VM is came with guest OS of Ubuntu 64-bits but after import, we check on that VM it shows only 32-bits OS.

    When we start the VM, we got error as:

    Failed to open a session for the virtual machine ERPNext-Develop-20180331192506.
    
    Raw-mode is unavailable courtesy of Hyper-V. (VERR_SUPDRV_NO_RAW_MODE_HYPER_V_ROOT).
    
    Result Code: E_FAIL (0x80004005)
    Component: ConsoleWrap
    Interface: IConsole {872da645-4a9b-1727-bee2-5585105b9eed}
    

    I did try above solutions, somehow not really work or I might miss something.

    Then I notice the point above (32-bits OS) so I think the problem might be with this one.

    With some posts around the Internet, it could explain that Windows 10 also comes with the Hyper-V which is conflict with Oracle VM VirtualBox.

    So solution I did...

    1. Disable Virtualization Based Security in group policy

    • Start Run application and start: gpedit.msc
    • Go to Computer configuration > Administrative Template > Device Guard

    1. Disable Microsoft Hyper-V

      • Start Run application and start: OptionalFeatures.exe
      • Untick: Hyper-V
      • Restart the PC

    Then we can use the VM, it's started. Among the two steps above, I believe that step 2 is really solved.

    Anyway, please try it and let's know if it helps.

    0 讨论(0)
  • 2020-12-07 07:38

    Run CMD in administrator mode 1.bcdedit 2.bcdedit /set hypervisorlaunchtype off 3.Reboot system

    This worked for me!!

    0 讨论(0)
  • 2020-12-07 07:39

    This would be the easiest way.

    1) go and download the Device Guard and Credential Guard hardware readiness tool here- https://www.microsoft.com/en-us/download/details.aspx?id=53337

    2) Find the folder path of "DG_Readiness_Tool_v3.5.ps1" of downloaded content and run the below command after enable Powershell "unrestricted". "./DG_Readiness_Tool_v3.5.ps1 -Disable -AutoReboot"

    3) When rebooting the machine press F3 to confirm to disable the features

    0 讨论(0)
  • 2020-12-07 07:40

    You need to disable the windows Hyper-V feature and bcd. Then Virtual Box will run in latest Windows 10 versions (Jan-Mar 2018). Windows 10 Hyper-V is having clash on VirtualBox features.

    I have resolved this by following steps-

    1. bcdedit /set hypervisorlaunchtype off
    2. Disable-WindowsOptionalFeature -Online -FeatureName Microsoft-Hyper-V-All
    3. Restart your windows

    Detailed discussion on this are available at - https://forums.virtualbox.org/viewtopic.php?f=6&t=87237

    Alternatively you can install linux (Ubuntu) in Windows 10 from the latest bash command - https://www.windowscentral.com/how-install-bash-shell-command-line-windows-10

    0 讨论(0)
  • 2020-12-07 07:44

    I wanted learn how to use vagrant with virtualbox, when I got the error message 'Raw-mode is unavailable courtesy of Hyper-V'. To fix this issue, I think I made all of the suggested changes above (thank you guys), and some more.

    Let me summarize:

    ( cmd: optionalfeatures )
    Turn off 'Hyper-V'
    Turn off 'Containers'
    Turn off 'Windows Subsystem for Linux'

    cmd: bcdedit /set hypervisorlaunchtype off

    ( cmd: gpedit.msc )
    Local Computer Policy -> Computer Configuration -> Administrative Templates -> System -> Device Guard ->
    Disable 'Turn On Virtualization Based Security'

    Settings -> Update & Security -> Windows Security -> Device Security -> Core isolation details -> Memory integrity -> Off

    0 讨论(0)
提交回复
热议问题