4 ms·
Windows basically always runs inside a hyper-v VM these days.
by patmorgan23 2y ago
Windows basically always runs inside a hyper-v VM these days.
- naikrovek 2y agoOnly if Hyper-V is enabled and/or WSL2 is installed. And Hyper-V is a prerequisite for WSL2. If hyper-V is not enabled, then you’re running on metal. You may notice a longer than normal reboot time when enabling or disabling Hyper-V compared to a normal reboot, and this is why; you’re moving from running on silicon to running in a privileged management VM or vice versa.
- terinjokes 2y agoVirtualization (Hyper-V) can also be enabled, without enabling the Hyper-V Manager or WSL2 Windows Components, if the "Core Isolation" security setting is enabled.
- NikkiA 2y agoThe biggest telltale for me is that hyper-v and wsl breaks anything that uses the ethernet mac as part of a host-id, and mobaxterm is unable to run it's X11 server because something about the hyper-v virtual ethernet screws it
- pjmlp 2y agoOr enabled the security features anyone should be running in first place, thus yeah since Windows 11, it is for all practical purposes. Same applies to XBox Windows flavour.
- intelVISA 2y agoIOMMU is my borrow checker