locked
Install Integration Component 2.1 on CentOS 6: Error 2 RRS feed

  • Question

  • Hi all,

    I'm trying to install IC v2.1 on to CentOS 6 without any result.

    I followed this link: http://www.howtoforge.com/installing-linux-integration-services-v2.1-hyper-v-r2-on-centos-5

    So, when I run the make command the following errors was returned:


    /ic/src/osd.c: In function ‘WaitEventSet’:
    /ic/src/osd.c:341: error: ‘TASK_INTERRUPTIBLE’ undeclared (first use in this function)
    /ic/src/osd.c:341: error: (Each undeclared identifier is reported only once
    /ic/src/osd.c:341: error: for each function it appears in.)
    /ic/src/osd.c: In function ‘WaitEventWait’:
    /ic/src/osd.c:349: error: ‘TASK_INTERRUPTIBLE’ undeclared (first use in this function)
    /ic/src/osd.c:349: error: implicit declaration of function ‘signal_pending’
    /ic/src/osd.c:349: error: implicit declaration of function ‘schedule’
    /ic/src/osd.c: In function ‘WaitEventWaitEx’:
    /ic/src/osd.c:360: error: ‘TASK_INTERRUPTIBLE’ undeclared (first use in this function)
    /ic/src/osd.c:360: error: implicit declaration of function ‘schedule_timeout’
    /ic/src/osd.c:469:41: error: macro "INIT_WORK" passed 3 arguments, but takes just 2
    /ic/src/osd.c: In function ‘WorkQueueQueueWorkItem’:
    /ic/src/osd.c:469: error: ‘INIT_WORK’ undeclared (first use in this function)
    /ic/src/osd.c:487:41: error: macro "INIT_WORK" passed 3 arguments, but takes just 2
    /ic/src/osd.c: In function ‘QueueWorkItem’:
    /ic/src/osd.c:487: error: ‘INIT_WORK’ undeclared (first use in this function)
    make[2]: *** [/ic/src/osd.o] Error 1
    make[1]: *** [_module_/ic/src] Error 2
    make: *** [all] Error 2

    make -C /lib/modules/2.6.32-71.29.1.el6.x86_64/build SUBDIRS=/ic/src modules
    make[1]: Entering directory `/usr/src/kernels/2.6.32-71.29.1.el6.x86_64'
    CC [M] /ic/src/osd.o
    make[1]: Leaving directory `/usr/src/kernels/2.6.32-71.29.1.el6.x86_64'

    Can you help me?

    tnx
    Andrea Gail
    Monday, July 18, 2011 12:55 PM

Answers

  • LIC 2.1 only work with SLES10 and RHEL5 & not officially supported on clones like Scientific Linux 5.x or CentOS 5.x. (soon CentOS might be added to the MS-supported Guest OSes)
    Yet, there is neither (true) support from RedHat, nor Microsoft for RHEL 6.x (and clones) on Hyper-V, no integrated modules (RH disabled them), no additional module from Microsoft.

    Currently you have 3 choices if you want a acceptably performing RHEL/CentOS-based VM:

    • Use RHEL5 with LIC 2.1 (recommended read: http://support.microsoft.com/kb/2387594) = Supported by both MS and RH
    • Use RHEL6 with modules from ELRepo.org (See mentioned in this thread) = not supported, but might work for you
    • Use RHEL6 without any accelerated VMBus modules = legacy 100Mbit NIC, slow IDE controller, 1 vCPU, no timesource, integrated powerdown etc.

     


    • Marked as answer by NGC7771 Wednesday, July 20, 2011 6:41 AM
    Tuesday, July 19, 2011 9:25 PM

All replies

  • LIC 2.1 only work with SLES10 and RHEL5 & not officially supported on clones like Scientific Linux 5.x or CentOS 5.x. (soon CentOS might be added to the MS-supported Guest OSes)
    Yet, there is neither (true) support from RedHat, nor Microsoft for RHEL 6.x (and clones) on Hyper-V, no integrated modules (RH disabled them), no additional module from Microsoft.

    Currently you have 3 choices if you want a acceptably performing RHEL/CentOS-based VM:

    • Use RHEL5 with LIC 2.1 (recommended read: http://support.microsoft.com/kb/2387594) = Supported by both MS and RH
    • Use RHEL6 with modules from ELRepo.org (See mentioned in this thread) = not supported, but might work for you
    • Use RHEL6 without any accelerated VMBus modules = legacy 100Mbit NIC, slow IDE controller, 1 vCPU, no timesource, integrated powerdown etc.

     


    • Marked as answer by NGC7771 Wednesday, July 20, 2011 6:41 AM
    Tuesday, July 19, 2011 9:25 PM
  • Or compile a new kernel with the staging drivers. From 2.6.39, they are much stable than before.

    Just don't forget to leave out the libata drivers.

    Wednesday, July 20, 2011 11:12 AM
  • That's indeed true and even far better with ewhat is coming in with 3.0 (and even > 3.0 in staging-next), but normally that is what people don't want to do with an Enterprise Linux: Compiling own kernels and keep tracking latest upstream releases. ;)

    Wednesday, July 20, 2011 2:01 PM
  • Andrea,  did you install virtualization as an option during the config of the CentOS kernel? That can cause problems.  Also are you sure you installed the "development tools"?  Then rebooted?  I would also reccomend running yum update as well prior to putting on IC v2.1.  I have been able to install IC v2.1 on CentOS v5.6 without error without Kernel\Virtualization and once the dev tools and updates were successfully installed and rebooted prior to the IC install.  Hope that helps.

    Question, were you able to install IC on CentOS 5?  I will try 6.

     

    Wednesday, July 20, 2011 5:37 PM
  • uta8: Forget about installing the Microsoft-provided Linux IC 2.1 on EL6-based distros. These modules were coded for the 2.6.18 based kernel (which has its origins in  late 2006!) even though Enterprise Linux Kernels contain tons of backports lots of things have changed on insides to 2.6.32 on which EL6 is based (Dec. 2009 + tons of backports from later kernels).

    To many things have changed since then, you'd be possibly luckier to take the sources from a 3.0 kernel and try backporting them EL6 - currently that's what MS guys are planning. They are fixing the upstream code and plan to backport it then afterwards to EL6 and other Enterprise Kernels.

    Friday, July 22, 2011 9:00 PM
  • Thx koffi2k.  I tried 6 on an R2 server, it has so many problems you really can't get to the point where you can install IC2.1.    Thanks for posting the cause above.
    Monday, July 25, 2011 8:06 PM
  • Good timing: Linux Integrations Services 3.1 for RedHat 6 and CentOS 6 (yes, not reading wrong) have been released today Aug. 27th. (not for RHEL5 BTW)

    They now come as ISO which requires you to install 2 rpm packages to be installe. Installing a RPM packages for these driver are really a much easier approach than re-compiling or fiddling yourself with DKMS ;-)

    Get them here: http://www.microsoft.com/download/en/details.aspx?id=26837

    • Proposed as answer by koffi2k Wednesday, July 27, 2011 8:49 PM
    Wednesday, July 27, 2011 8:49 PM