How to choose LIS Linux Integration Services on Hyper-V Linux VMS

Guide

Many engineers know that if you choose to run a Linux guest VM in Hyper-V, for the best experience, you must choose Linux Integration Services for the Linux distribution and usage scenarios you are using (Lis,linux integration service Services). Getting the best "linux experience in Hyper-V is tricky, and we'll cover it in detail to help you make the right choice for your situation.

Let's start by noticing that Microsoft delivers LIS to users through two separate channels. These two delivery channels are independent of each other, so you must first determine which channel is best for you.

Linux distributions built-in Lis

The first major Linux vendors, such as Red Hat, SUSE, Oracle, Canonical, and the Debian community, are the most straightforward delivery methods for Linux integration Services (LIS). Microsoft and Linux Community developers will submit large LIS updates to the Linux kernel mailing list and collect code reviews and feedback from the Linux community. When the feedback process is complete, the changes are incorporated into the Linux kernel that is responsible for the upstream Linus Torvalds and Linux community maintainers. When the acceptance is qualified, the Linux Distributor will migrate the Linux kernel to its own release version, and the Publisher will build and Test LIS as part of its product. When the test is complete, Microsoft will get an earlier version of the product and return its test results to the publisher. Currently, companies such as Red Hat, SUSE, Canonical, and Oracle maintain a collaborative process with Microsoft that includes RHEL, CentOS, SLES, Oracle Linux, and Ubuntu. Of course, the Debian community also maintains the same cooperation with Microsoft.

This LIS distribution channel is called "Built-in" by Microsoft, which means that you have built in Lis when you get the product from a Linux publisher. For example, when you upgrade from CentOS 7.0 to 7.1, you will get the CentOS 7.1 update for LIS. Note that Microsoft does not specify a version number for the built-in Lis, and when a user can get an LIS update depends entirely on when the publisher pulls and updates the Linux kernel from the upstream. The only disadvantage of this "built-in" approach is that users may not be able to get the latest LIS updates and new features in a timely manner, but joint testing between Linux vendors and Microsoft ensures that Linux systems are used stably in Hyper-V environments. Technical support for the built-in LIS depends solely on the support agreement and terms between the end user and the Linux Publisher, and Microsoft's direct customer can obtain Microsoft's official technical support under the terms of the Hyper-V support agreement. In both cases, the LIS code-level Bug is handled by Microsoft and the Linux Publisher, and is fixed by the Linux Publisher's update code or patch.

Microsoft Lis Standalone installation package

Another delivery channel for Linux integration Services is the LIS installation package that Microsoft provides directly to end users, which presumably is familiar to many Microsoft-oriented engineers, and is suitable for RHEL, CentOS, and other Red Hat cores and compatible ORACL Distribution of E Linux. As Azure continues to update and supports the new version of Hyper-V for Windows Server 2016, the standalone LIS maintains a certain amount of update frequency and speed. The emergence of the standalone LIS installation package allows the user to update the functionality and performance of the LIS without waiting for the official update of the Linux vendor. The Microsoft Standalone installation package is currently available in the LIS 4.1 and LIS 4.0 versions and can be downloaded and installed on your own.

It is important to note that a specific version of the Linux kernel is required to match with the standalone LIS version. For example, when using the LIS standalone package, the LIS package will not be updated after the system is updated from CentOS 7.0 to 7.1, and the LIS will need to be upgraded separately. If you update only the Linux kernel or the large version without upgrading the LIS, it could cause a two progress mismatch in the Linux kernel, which could cause the system to fail to boot. Microsoft will provide official technical support for Linux users who use the standalone LIS package in accordance with the Hyper-V support terms, and if you use an older version, Microsoft will ask for upgrades to the latest LIS version to see if the issue exists in the technical support. Because the LIS is primarily run on Linux kernel-level drivers, Microsoft only provides version updates and is unlikely to provide fixes.

Here's how to choose Linux Integration Services for Hyper-V Linux VMS to list a table for your reference only:

How to choose LIS Linux Integration Services on Hyper-V Linux VMS