locked
After installing Linux Integration Service 3.4 on CentOS 6.3 It Dies, after it crashes into a Kernel Panic RRS feed

  • Question

  • After installing Linux Integration Service 3.4 on CentOS 6.3 It Dies, after it crashes into a Kernel Panic

    Situation:

    1. We have a CentOS 6.3 guest (kernel version 2.6.32-279.22.1.el6.i686) on a Windows server 2012 Hyper V.
    2. The LIS 3.4 installation takes some time but it finish succesfully via ./install.sh script.
    3. Then it tell us to reboot the CentOS guest and we do.
    4. During boot up, the CentOS box dies in a kernel panic. See attachement below.

    However, when I use the stock version of the kernel  2.6.32-279.el6.i686 and install LIS 3.4, it works. This is the original kernel from the CentOS 6.3 netinstall iso. BUT THIS IS NOT WHAT WE WANT!!! 

    Are we the only organization that facing this issue?

    If not, can someone, perhaps from MICROSOFT look into this ISSUE please?


    Wednesday, February 20, 2013 2:16 PM

Answers

  • I think I had the same problem and my solution was to follow this post and install the src rpm and then build my own from the 3.4 IC iso.  The kernel panic only happens to me on i686.  x86_64 works just fine with the prebuilt rpm.

    This account is unverified so I cannot post links, but google this string to find the reference blueonyx.it/msg04625.html

    Relevant text part included for convenience

    This is "fixed".
    If you're using an i686 kernel, you have to rebuild the Hyper-V components
    against the 2.6.32-279.11.1.el6 kernel.
    Don't know why it wasn't necessary with the x86_64 kernel.
    
    prerequisites :
    - remove the hyper-v components
    - boot using the latest kernel (2.6.32-279.11.1.el6)
    - if necessary, add a legacy network card for remote access (facilitates
    operations).
    
    Steps to rebuild :
    - setup a working rpmbuild infrastructure
    - install the kernel-devel package
    - from the LinuxICv34 iso and as a normal user, install the src.rpm package
    (rpm -ivh microsoft-hyper-v-rhel63.3.4-1.20120727.src.rpm)
    - this will install an hyper-v.spec file into your ~/rpmbuild/SPECS
    directory
    - as a normal user, cd to ~/rpmbuild/SPECS and run 'rpmbuild -bb
    microsoft-hyper-v.spec'
    - this will compile the hyper-v components agains your current kernel and
    build the related rpm packages.
    - install the new RPMs, first kmod-microsoft-hyper-v and after
    microsoft-hyper-v (rpm -ivh .).
    
    The issue is related to the ata_piix driver, when the hyper-v components are
    working, this driver is removed and replaced with the hv_storvsc driver
    (/etc/modprobe.d/hyperv_pvdrivers.conf : install ata_piix  { /sbin/modprobe
    hv_storvsc 2>&1 || /sbin/modprobe --ignore-install ata_piix; }
    
    I wasted some time because my first approach was to patch the ata_piix
    driver, but it turns out to be quite unsuccessful (i even try to backport
    some code from the 3.6 branch, guess what happened.).
    So the obvious fix is to rebuild the hyper-v components.

    • Marked as answer by samvirtual Sunday, February 24, 2013 8:35 PM
    Thursday, February 21, 2013 2:23 AM
  • Fixed the kernel panic  of the particular CentOS 6.3 box on of my last post above (Feb 21th 2013).

    I had to remove some boot parameters "clock=pit nosmp noapic nolapic" from the /etc/grub.conf.

    These parameters were added as solution to keep the time synchronized in the VMWare Server 1.0.x, where this guest is migrated from. The “clock=pit” prevents the clock from running too quickly and “nosmp noapic nolapic” prevents the clock from running too slowly. (google"clock=pit nosmp noapic nolapic"). So now I have to carefully monitor LIS3.4 time synchronization feature. Hopefully that is suffient.... I will mark both yackol1 's post and this one as answer of my original question.


    • Marked as answer by samvirtual Sunday, February 24, 2013 8:35 PM
    Sunday, February 24, 2013 8:35 PM

All replies

  • I think I had the same problem and my solution was to follow this post and install the src rpm and then build my own from the 3.4 IC iso.  The kernel panic only happens to me on i686.  x86_64 works just fine with the prebuilt rpm.

    This account is unverified so I cannot post links, but google this string to find the reference blueonyx.it/msg04625.html

    Relevant text part included for convenience

    This is "fixed".
    If you're using an i686 kernel, you have to rebuild the Hyper-V components
    against the 2.6.32-279.11.1.el6 kernel.
    Don't know why it wasn't necessary with the x86_64 kernel.
    
    prerequisites :
    - remove the hyper-v components
    - boot using the latest kernel (2.6.32-279.11.1.el6)
    - if necessary, add a legacy network card for remote access (facilitates
    operations).
    
    Steps to rebuild :
    - setup a working rpmbuild infrastructure
    - install the kernel-devel package
    - from the LinuxICv34 iso and as a normal user, install the src.rpm package
    (rpm -ivh microsoft-hyper-v-rhel63.3.4-1.20120727.src.rpm)
    - this will install an hyper-v.spec file into your ~/rpmbuild/SPECS
    directory
    - as a normal user, cd to ~/rpmbuild/SPECS and run 'rpmbuild -bb
    microsoft-hyper-v.spec'
    - this will compile the hyper-v components agains your current kernel and
    build the related rpm packages.
    - install the new RPMs, first kmod-microsoft-hyper-v and after
    microsoft-hyper-v (rpm -ivh .).
    
    The issue is related to the ata_piix driver, when the hyper-v components are
    working, this driver is removed and replaced with the hv_storvsc driver
    (/etc/modprobe.d/hyperv_pvdrivers.conf : install ata_piix  { /sbin/modprobe
    hv_storvsc 2>&1 || /sbin/modprobe --ignore-install ata_piix; }
    
    I wasted some time because my first approach was to patch the ata_piix
    driver, but it turns out to be quite unsuccessful (i even try to backport
    some code from the 3.6 branch, guess what happened.).
    So the obvious fix is to rebuild the hyper-v components.

    • Marked as answer by samvirtual Sunday, February 24, 2013 8:35 PM
    Thursday, February 21, 2013 2:23 AM
  • Hi yackol1,

    Thanks. Your answer works perfectly. We have no two CentOS machines running LIS3.4 on 2.6.32-279.11.1.el6 without a problem.

    Actually before we posted this issue, we did a rebuild with the src.rpm package against the 2.6.32-279.11.1.el6 kernel. That was not working probably caused by the fact that we had rebuild it as root, while your answer explicitely say as non-root

    HOWEVER we still have trouble with one CentOS box (also running 2.6.32-279.11.1.el6 kernel). This one still keep go into kernel panic. See picture below [hmm my account does not allow me place pictures]. On boot screen it is only showing a blinking cursor _ and nothing like "udev...." is showing up. after blinking like 30 seconds the system stops with the kerne panic.

    Does anyone here has a clue??? 

     

    Thursday, February 21, 2013 2:56 PM
  • Fixed the kernel panic  of the particular CentOS 6.3 box on of my last post above (Feb 21th 2013).

    I had to remove some boot parameters "clock=pit nosmp noapic nolapic" from the /etc/grub.conf.

    These parameters were added as solution to keep the time synchronized in the VMWare Server 1.0.x, where this guest is migrated from. The “clock=pit” prevents the clock from running too quickly and “nosmp noapic nolapic” prevents the clock from running too slowly. (google"clock=pit nosmp noapic nolapic"). So now I have to carefully monitor LIS3.4 time synchronization feature. Hopefully that is suffient.... I will mark both yackol1 's post and this one as answer of my original question.


    • Marked as answer by samvirtual Sunday, February 24, 2013 8:35 PM
    Sunday, February 24, 2013 8:35 PM
  • What is your suggestion if the only user on the machine is root?  Its a customized CentOS 6.3 install (PBX in a Flash) so I do not have a normal user.
    Thursday, February 28, 2013 8:00 PM
  • I am not familliar with pbx in a flash,

    maybe you are allowed to create a normal user named  builder

    adduser builder

    Then login as the new user, and do your rpmbuild

    sudo builder

     
    Monday, March 4, 2013 1:18 PM
  • Hi Sam,

    I'm having the exact same issue as you. I'm trying to get LIS on my Centos 6.3 i686. Do you mind sending me your rebuilt LIS? I can't seem to google the string provided by yackol1 above for the fix.

    Thanks!


    Tuesday, May 23, 2017 7:33 PM
  • Hi Shaun,

    Were you able to get LIS on your CentOS 6.3? I'm trying to do the same.

    Thanks!

    Tuesday, May 23, 2017 7:35 PM