F5F Stay Refreshed Software Operating Systems Assessing the feasibility of using a Windows 10 gaming VM on Linux Exploring performance and compatibility options

Assessing the feasibility of using a Windows 10 gaming VM on Linux Exploring performance and compatibility options

Assessing the feasibility of using a Windows 10 gaming VM on Linux Exploring performance and compatibility options

Pages (2): Previous 1 2
S
stevenpowerrr
Junior Member
49
07-20-2017, 06:43 AM
#11
I thought it might be more complicated than I realized. The easiest way to get what I need would be using two drives—one with Windows 10 and another with Linux—so I can pick which one to boot from the BIOS or have them separate. This isn’t perfect, since my motivation for switching comes from Windows network drivers not working well. Do you think Wine could reach near 100% compatibility?
S
stevenpowerrr
07-20-2017, 06:43 AM #11

I thought it might be more complicated than I realized. The easiest way to get what I need would be using two drives—one with Windows 10 and another with Linux—so I can pick which one to boot from the BIOS or have them separate. This isn’t perfect, since my motivation for switching comes from Windows network drivers not working well. Do you think Wine could reach near 100% compatibility?

M
mumustrak
Senior Member
729
07-22-2017, 01:06 AM
#12
Until Microsoft ceases its innovations or the open-source version of Windows continues (including DirectX), this situation will remain unchanged. If you prefer Linux, your top choices are either leveraging WSL on Windows 10 or setting up a dual-boot configuration. WSL enables you to run a Linux distribution alongside Windows, letting you execute Linux applications and access its Terminal within Windows—offering flexibility and seamless integration. You can switch between two distinct WSL versions at any time. WSL1 employs a Linux kernel translation layer, while WSL2 runs a custom kernel inside a lightweight Hyper-V environment. Each has pros and cons: WSL2 provides superior compatibility but may experience slower disk I/O when accessing files outside its Linux context (Windows disk performance drops only if you're on Linux). It also slightly reduces overall system speed, especially on older hardware—my machine being 12 years old is a prime example. WSL1 avoids this performance hit and doesn’t affect Windows disk operations, though it limits program compatibility; for instance, Docker isn’t supported there. If you’re aiming for software development or similar tasks, WSL2 is the better option. Currently, the main drawbacks are manual service management (with possible workarounds) and the absence of graphical user interface support—requiring an xServer like X410, which can be found at a reasonable price in the Windows Store. There are free alternatives available if you’re curious. Alternatively, you might wait for Microsoft to add GUI support, which they have been developing but haven’t released yet, with no confirmed timeline.
M
mumustrak
07-22-2017, 01:06 AM #12

Until Microsoft ceases its innovations or the open-source version of Windows continues (including DirectX), this situation will remain unchanged. If you prefer Linux, your top choices are either leveraging WSL on Windows 10 or setting up a dual-boot configuration. WSL enables you to run a Linux distribution alongside Windows, letting you execute Linux applications and access its Terminal within Windows—offering flexibility and seamless integration. You can switch between two distinct WSL versions at any time. WSL1 employs a Linux kernel translation layer, while WSL2 runs a custom kernel inside a lightweight Hyper-V environment. Each has pros and cons: WSL2 provides superior compatibility but may experience slower disk I/O when accessing files outside its Linux context (Windows disk performance drops only if you're on Linux). It also slightly reduces overall system speed, especially on older hardware—my machine being 12 years old is a prime example. WSL1 avoids this performance hit and doesn’t affect Windows disk operations, though it limits program compatibility; for instance, Docker isn’t supported there. If you’re aiming for software development or similar tasks, WSL2 is the better option. Currently, the main drawbacks are manual service management (with possible workarounds) and the absence of graphical user interface support—requiring an xServer like X410, which can be found at a reasonable price in the Windows Store. There are free alternatives available if you’re curious. Alternatively, you might wait for Microsoft to add GUI support, which they have been developing but haven’t released yet, with no confirmed timeline.

Pages (2): Previous 1 2