

The WSL product repo issues enables you to: File an issue, bug report, feature request The kernel also divides processes that require long computing times into smaller components, which are then scheduled and processed accordingly.We have covered some common troubleshooting scenarios associated with WSL below, but please consider searching the issues filed in the WSL product repo on GitHub as well. The Linux kernel features real-time extensions that allow VM-based apps to run at lower latency with better prioritization (compared to bare metal). In KVM, this includes the completely fair scheduler, control groups, network name spaces, and real-time extensions. The Linux scheduler allows fine-grained control of the resources allocated to a Linux process and guarantees a quality of service for a particular process. In the KVM model, a VM is a Linux process, scheduled and managed by the kernel. KVM allows the most demanding application workloads to be virtualized and is the basis for many enterprise virtualization setups, such as datacenters and private clouds (via OpenStack®). KVM inherits the performance of Linux, scaling to match demand load if the number of guest machines and requests increases. KVM also saves a VM's current state so it can be stored and resumed later. The VM remains powered on, network connections remain active, and applications continue to run while the VM is relocated. KVM supports live migration, which is the ability to move a running VM between physical hosts with no service interruption. The memory of a VM can be swapped, backed by large volumes for better performance, and shared or backed by a disk file. KVM inherits the memory management features of Linux, including non-uniform memory access and kernel same-page merging. Because hardware vendors regularly contribute to kernel development, the latest hardware features are often rapidly adopted in the Linux kernel. KVM can use a wide variety of certified Linux-supported hardware platforms.

Disk images support thin provisioning, allocating storage on demand rather than all up front. KVM also supports shared file systems so VM images may be shared by multiple hosts. Multipath I/O may be used to improve storage and provide redundancy. KVM is able to use any storage supported by Linux, including some local disks and network-attached storage (NAS). sVirt extends SELinux’s capabilities, allowing Mandatory Access Control (MAC) security to be applied to guest VMs and preventing manual labeling errors. SELinux establishes security boundaries around VMs. KVM uses a combination of security-enhanced Linux (SELinux) and secure virtualization (sVirt) for enhanced VM security and isolation. But there are specific features that make KVM an enterprise’s preferred hypervisor.
