Information and announcements from Program Managers, Product Managers, Developers and Testers in the Microsoft Virtualization team.
Hyper-V customers are running both SUSE Linux Enterprise Server and Red Hat Enterprise Linux as guests. We have provided Linux integration components for SUSE Linux Enterprise Server, but customers did not have the same level of performance with Red Hat Enterprise Linux as a guest since the IC’s were not supported for RHEL.
We are excited to announce the availability of Linux integration components for Red Hat Enterprise Linux (RHEL 5.2, 5.3, and 5.4) which provides synthetic network and storage drivers enabling RHEL to work with the optimized devices provided by Hyper-V. We’ve already submitted these drivers to the upstream Linux kernel in July 2009 (read here for more information) and are looking forward to these being integrated with a future version of RHEL. In the meantime, Microsoft will provide full support for these drivers. Red Hat provides best effort support for these components. Customers interested in understanding how these are supported by Red Hat prior to their inclusion natively into to their distribution can read the details at the Red Hat Knowledge Base article.
To download this new version of the Linux Integration Components, visit this link on the Microsoft Download Center.
Hyper-V Program Manager, Microsoft
This is great! Are there any plans to allow CPUs > 1 for linux guests?
I have a question related to Linux Update, we hosted Linus 5.4 as a guest OS on hyper V, do we need to include kernal in Yum Updates or will it create any problem by updating Linux to 5.5
As of today, 06.15.2010 - Do not run Kernel Updates, the modules are dependant on the running kernel and will kernel panic your guest linux VM if you try to update the kernel while LIC/LIS is attached to the running kernel.
what is LIC/LIS? I can't update kernel but not sure how to proceed?
When booting the machine with a kernel where no Linux Integration Components has been installed for, you will have to edit the kernel parameters in the grub startup screen so it uses the standard (slow) emulated IDE implementation.
Here you will have to remove the values containing hda=noprobe hdb=noprobe (or ide0=noprobe ide1=noprobe for RHEL 5.5).
Now the kernel is able to access the disks again, so you can build/install the drivers. After you installed the drivers you will be able to boot again *with*
the parameters "ide0=noprobe ide1=noprobe".
I found, that you must remember to disable Integration Services on the WM, when you boot the new kernel until the Integration Components are re-applied.