- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Struggling to enable Hyper-V on Ryzen and Windows 10 Pro
Hi!
My setup:
- Gigabyte Aorus X470 Gaming 7 WIFI
- AMD Ryzen 2700X
- Windows 10 Pro 64-bit v. 1903
- BIOS F31
- AMD Chipset driver v. 19
I'm trying to run Docker natively, without VirtualBox. When I try to set it up with Kitematic, it says:
I have enabled SVM
and IOMMU
in the BIOS. I have installed Hyper-V
in Windows components. Uninstalled VirtualBox.
I'm running msinfo32
and expect to see four items related to Hyper-V. Instead, I see: "A hypervisor has been detected. Features required for Hyper-V will not be displayed."
Kitematic is not detecting native capabilities. Docker is not working, fails with a cryptic error.
How do I enable Hyper-V??
Solved! Go to Solution.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Starting Hyper-V Manager and setting up a virtual machine has proved that Hyper-V is working correctly.
After that, Docker started working! Not sure if it's a coincidence.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
lolmaus, I do not know what you mean here: "I have installed Hyper-V
in Windows components." MS has good instructions for doing this but if I post a link to it, my reply will be delayed for minutes to days. So please: open Control Panel - click Uninstall a program - click Turn Windows features on or off - find Hyper-V and select it - using the + expand it and make sure all sub-items are also selected (checked). A Restart will be needed. Enjoy, John.
EDIT: Your MSinfo32 message seems to be saying a Hypervisor is installed, so make sure all other Hypervisors (VirtualBox) are uninstalled.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Starting Hyper-V Manager and setting up a virtual machine has proved that Hyper-V is working correctly.
After that, Docker started working! Not sure if it's a coincidence.
