locked
LIS version 4.0.11 and RH Enterprise 6.6 (Santiago) RRS feed

All replies

  • The readme in the LIS download gives instructions on how to mount the ISO and it includes the RPMs necessary to be installed on RHEL 6.6.

    Joshua R. Poulson, Program Manager, Microsoft Open Source Technology Center

    Wednesday, November 25, 2015 6:26 PM
  • Hi Josh,

    The install.sh states:

    # Kernel version
    #  7.1    3.10.0-229
    #  7.0    3.10.0-123
    #  6.7    2.6.32-573
    #  6.6    2.6.32-504
    #  6.5    2.6.32-431
    #  6.4    2.6.32-358
    #  6.3    2.6.32-279
    #  6.2    2.6.32-220
    #  6.1    2.6.32-131.0.15
    #  6.0    2.6.32-71
    #  5.11   2.6.18-398
    #  5.10   2.6.18-371
    #  5.9    2.6.18-348
    #  5.8    2.6.18-308
    #  5.7    2.6.18-274
    #  5.6    2.6.18-238
    #  5.5    2.6.18-194
    #
    #  Other releases are not supported.

    We have tested LIS 4.0.11 on 6.7 and it still kernel panics on with kernel version 573, it appears to run fine on kernel 504 though.

    WARNING: /lib/modules/2.6.32-573.8.1.el6.x86_64/weak-updates/microsoft-hyper-v/hv_storvsc.ko needs unknown symbol vmbus_sendpacket_mpb_desc

    WARNING: /lib/modules/2.6.32-573.8.1.el6.x86_64/weak-updates/microsoft-hyper-v/hv_netvsc.ko needs unknown symbol vmbus_sendpacket_ctl
    WARNING: /lib/modules/2.6.32-573.8.1.el6.x86_64/weak-updates/microsoft-hyper-v/hv_netvsc.ko needs unknown symbol vmbus_sendpacket_pagebuffer_ctl

    Monday, November 30, 2015 2:44 AM
  • I have removed the hyperV RPM's and then updated the kernel. After a quick reboot, run ./install.sh again, and final reboot.

    I am not sure why the RPM's don't work seamlessly as the kernel is been updated. Just a waste of time really.

    Wednesday, June 1, 2016 7:47 PM
  • As of LIS 4.1.1, The RPM requirements ensure that they are being applied to the latest kernel and that it is also the kernel that is running when they are applied. There were occasions if this was not enforced then there would be conflicts between the LIS that is built into the Red Hat kernel and the same drivers in LIS.

    Sorry this has caused problems for you, but it was necessary to prevent situations where the VM wouldn't boot after LIS was installed.

    Thanks, --jrp


    Joshua R. Poulson, Program Manager, Microsoft Open Source Technology Center

    Wednesday, June 1, 2016 11:05 PM