Sign in
 

none
RedHat 6.3 Integration Service installation failed

 > 

    Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    i want to setup a redhat-6.3 machine on wour hyper-v cluster but i can´t install the integration tools (3.3) completly cause of this error

    failed dependencies:

    kernel(clocksource_register) = 0xd88be65d is needed by kmod-microsft-hyper-vrhel63.3-4.20120605.x86_64

    KMOD RPM installation failed, Exiting.

    Any ideas to this failure?

    Kind regards

    ACID1943


    • Edited by ACID1943 Friday, June 29, 2012 7:44 AM
    Friday, June 29, 2012 7:44 AM
    |

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    HI

    I have the same problem.
    Did you find a solution for it?

    Thanks.

    Friday, July 6, 2012 8:20 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi

    no i don´t find a solution, i´m waiting for a microsoft statement here ;-)

    regards

    ACID1943

    Friday, July 6, 2012 9:12 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    +1

    I'm also getting this error.

    Looking for a solution (eyeballs Microsoft).

    Monday, July 9, 2012 7:26 PM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    Linux Integration Services V3.3 For Hyper-V

    Version 3.3 of the Linux integration components was just released with support

    for Windows 8 and Windows Server 2012.

    It supports the following versions of Hyper-V:

      Windows Server 2008 Standard, Windows Server 2008 Enterprise, and Windows

      Server   2008 Datacenter

      Microsoft® Hyper-V Server 2008

      Windows Server 2008 R2 Standard, Windows Server 2008 R2 Enterprise, and

      Windows    Server 2008 R2 Datacenter

      Microsoft Hyper-V Server 2008 R2

      Windows 8 Release Preview

      Windows Server 2012

    See those last two?  Windows 8 and Windows Server 2012 are supported.

    The supported guest OS’s are:

      Red Hat Enterprise Linux 6.0-6.2 x86 and x64 (Up to 4 vCPU)

      CentOS 6.0-6.2 x86 and x64 (Up to 4 vCPU)

      Red Hat Enterprise Linux 6.0-6.2 x86 and x64 (Up to 32 vCPU when used on a

      Windows 8 Release Preview or Windows Server 2012 host)

      CentOS 6.0-6.2 x86 and x64 (Up to 32 vCPU when used on a Windows 8 Release

      Preview or Windows Server 2012 host)

    RHEL 6.2 and CentOS 6.2 were added to the list in v3.3. SLES and RHEL 5.x use

    version 2.1 of the Linux Integration Services.

    Notice that RHEL and Centos support up to 32 virtual CPUs on Windows Server 2012

    or Windows 8???  Nice scalable Linux workloads on Hyper-V   OK let’s talk

    turkey.

    Once you start adding lots of vCPUs to Linux, you have a few concerns:

      Bear in mind that I’m a Linux noob and forgive me for lack of details, but

      Linux has issues where it needs some work to have more than 8 vCPUs in a VM. 

      One fix is to use Linux Kernel 3.4 or later.

      With lots of vCPUs you need to handle NUMA nodes, and your Linux guest will be

      NUMA hardware aware on WS2012 with Linux Kernel 3.4 or later.

    Kalpesh Patel If you find these posts answered your question or issue, please click on "Mark as answer". If a post contained helpfull information, please be click on the "Vote as helpful" button


    Tuesday, July 10, 2012 5:59 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    This DOES NOT WORK. This is a simplistic guide to "NEXT, NEXT, NEXT" through a RHEL install. It nearly makes no difference how you answer the setup prompts. At all. The issue is Microsoft does not know how to make modules that have proper abstraction with specific kernel versions.

    Please people, before posting answers, try it out. We are talking about VMs here. its not hard to test.

    The issue is quite simple. The kmod RPM has symbols in it that are NOT in the RHEL 6.2/6.3 kernels.

    I ran into this, Hyper-V 2012 with RHEL 6.3 in a VM.

    Here is the issue:

    -r-xr-xr-x. 1 root root   1547 Jul  9 15:34 install.sh
    -r--r--r--. 1 root root 920348 Jul  9 15:34 kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    -r--r--r--. 1 root root  18092 Jul  9 15:34 LICENSE_GPL
    -r--r--r--. 1 root root  28036 Jul  9 15:34 microsoft-hyper-v-debuginfo-rhel63.3-4.20120605.x86_64.rpm
    -r--r--r--. 1 root root  90326 Jul  9 15:34 microsoft-hyper-v-rhel63.3-4.20120605.src.rpm
    -r--r--r--. 1 root root  10944 Jul  9 15:34 microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    -r--r--r--. 1 root root  90322 Jul  9 15:34 microsoft-hyper-v-rhel63.3-4.20120606.src.rpm
    -r-xr-xr-x. 1 root root   1317 Jul  9 15:34 upgrade.sh

    # rpm --test -Uvh *.rpm
    warning: kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 6a39758c: NOKEY
    error: Failed dependencies:
            kernel(clocksource_register) = 0xd88be65d is needed by kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64

    Simple. The symbols are not there.

    Here is the error if you try to insmod the ko manually:

    rpm2cpio kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm | cpio -ivd

    cd lib/modules/2.6.32-71.el6.x86_64/extra/microsoft-hyper-v

    THERE IT IS, a VERSION SPECIFIC module.

    This is the RHEL 6.0 release kernel. its ancient. and it has lots of bugs. Microsoft needs to update its kernel support in a major way.

    If you try to insmod it you get:

    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_driver_unregister
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_sendpacket
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_prep_negotiate_resp
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_close
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_recvpacket
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_open
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol __vmbus_driver_register

    So , what you have to do is DOWNGRADE your kernel:

    GET kernel-2.6.32-71.el6.x86_64.rpm

    rpm -i kernel-2.6.32-71.el6.x86_64.rpm

    (rpm says this is dumb because its putting in an older kernel,  it is dumb, but it works).

    rpm -i --force kernel-2.6.32-71.el6.x86_64.rpm

    reboot.

    now:

    [root@localhost LIS33]# ./install.sh
    Installing the Linux Integration Services for Microsoft Hyper-V...
    warning: kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 6a39758c: NOKEY
    Preparing...                ########################################### [100%]
       1:kmod-microsoft-hyper-v ########################################### [100%]
    ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-71.el6.x86_64.conf:6: hwcap index 1 already defined as nosegneg
    ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-71.el6.x86_64.conf:6: hwcap index 1 already defined as nosegneg
    warning: microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 6a39758c: NOKEY
    Preparing...                ########################################### [100%]
       1:microsoft-hyper-v      ########################################### [100%]
    ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-71.el6.x86_64.conf:6: hwcap index 1 already defined as nosegneg
    Saving old initramfs
    Installing new initramfs
     Linux Integration Services for Hyper-V has been installed. Please reboot your system.

    reboot.

    Works. I got the LIS33 to install on an old, broken, insecure outdated kernel. Microsoft, get your stuff together. I could fix this for you, I've lead engineering teams doing much harder things than this.

    dmesg | grep -i hv
    hv_vmbus: Hyper-V Host OS Build:8432-6.2-0-0.0
    hv_vmbus: child device vmbus_0_1 registered
    hv_vmbus: child device vmbus_0_2 registered
    hv_vmbus: child device vmbus_0_3 registered
    hv_vmbus: child device vmbus_0_4 registered
    hv_vmbus: child device vmbus_0_5 registered
    hv_vmbus: child device vmbus_0_6 registered
    hv_vmbus: child device vmbus_0_7 registered
    hv_vmbus: child device vmbus_0_8 registered
    hv_vmbus: child device vmbus_0_9 registered
    hv_vmbus: child device vmbus_0_10 registered
    hv_vmbus: child device vmbus_0_11 registered
    hv_vmbus: child device vmbus_0_12 registered
    hv_vmbus: registering driver hv_storvsc
    hv_vmbus: registering driver hv_netvsc
    hv_netvsc: hv_netvsc channel opened successfully
    hv_netvsc vmbus_0_10: Device MAC xx:x:xx:xx:xx:xx link state up
    hv_timesource: Registering HyperV clock source
    hv_vmbus: registering driver hid_hyperv
    hv_utils: Registering HyperV Utility Driver
    hv_vmbus: registering driver hv_util
    hv_utils: KVP: user-mode registering done.

    I may try to hackup a good verison.

    Microsoft, why not supply SRPMs for this stuff if you arent going to properly support the OS?

    • Proposed as answer by BrianEhMVP Wednesday, July 25, 2012 8:18 PM
    Tuesday, July 10, 2012 6:18 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    The kmod is version specific. It basically only supports the rhel release kernel, 2.6.32-71.el6.

    Someone needs to transmogrify, hack or tease this thing into working on the current released version, 2.6.32-279.

    Posting images and faq-text doesnt make this happen.

    Tuesday, July 10, 2012 6:20 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    The issue is quite simple. The kmod RPM has symbols in it that are NOT in the RHEL 6.2/6.3 kernels.

    I ran into this, Hyper-V 2012 with RHEL 6.3 in a VM.

    Here is the issue:

    -r-xr-xr-x. 1 root root   1547 Jul  9 15:34 install.sh
    -r--r--r--. 1 root root 920348 Jul  9 15:34 kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    -r--r--r--. 1 root root  18092 Jul  9 15:34 LICENSE_GPL
    -r--r--r--. 1 root root  28036 Jul  9 15:34 microsoft-hyper-v-debuginfo-rhel63.3-4.20120605.x86_64.rpm
    -r--r--r--. 1 root root  90326 Jul  9 15:34 microsoft-hyper-v-rhel63.3-4.20120605.src.rpm
    -r--r--r--. 1 root root  10944 Jul  9 15:34 microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    -r--r--r--. 1 root root  90322 Jul  9 15:34 microsoft-hyper-v-rhel63.3-4.20120606.src.rpm
    -r-xr-xr-x. 1 root root   1317 Jul  9 15:34 upgrade.sh

    # rpm --test -Uvh *.rpm
    warning: kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 6a39758c: NOKEY
    error: Failed dependencies:
            kernel(clocksource_register) = 0xd88be65d is needed by kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64

    Simple. The symbols are not there.

    Here is the error if you try to insmod the ko manually:

    rpm2cpio kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm | cpio -ivd

    cd lib/modules/2.6.32-71.el6.x86_64/extra/microsoft-hyper-v

    THERE IT IS, a VERSION SPECIFIC module.

    This is the RHEL 6.0 release kernel. its ancient. and it has lots of bugs. Microsoft needs to update its kernel support in a major way.

    If you try to insmod it you get:

    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_driver_unregister
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_sendpacket
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_prep_negotiate_resp
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_close
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_recvpacket
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol vmbus_open
    Jul  9 15:56:35 localhost kernel: hv_utils: Unknown symbol __vmbus_driver_register

    So , what you have to do is DOWNGRADE your kernel:

    GET kernel-2.6.32-71.el6.x86_64.rpm

    rpm -i kernel-2.6.32-71.el6.x86_64.rpm

    (rpm says this is dumb because its putting in an older kernel,  it is dumb, but it works).

    rpm -i --force kernel-2.6.32-71.el6.x86_64.rpm

    reboot.

    now:

    [root@localhost LIS33]# ./install.sh
    Installing the Linux Integration Services for Microsoft Hyper-V...
    warning: kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 6a39758c: NOKEY
    Preparing...                ########################################### [100%]
       1:kmod-microsoft-hyper-v ########################################### [100%]
    ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-71.el6.x86_64.conf:6: hwcap index 1 already defined as nosegneg
    ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-71.el6.x86_64.conf:6: hwcap index 1 already defined as nosegneg
    warning: microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm: Header V3 DSA/SHA1 Signature, key ID 6a39758c: NOKEY
    Preparing...                ########################################### [100%]
       1:microsoft-hyper-v      ########################################### [100%]
    ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-71.el6.x86_64.conf:6: hwcap index 1 already defined as nosegneg
    Saving old initramfs
    Installing new initramfs
     Linux Integration Services for Hyper-V has been installed. Please reboot your system.

    reboot.

    Works. I got the LIS33 to install on an old, broken, insecure outdated kernel. Microsoft, get your stuff together. I could fix this for you, I've lead engineering teams doing much harder things than this.

    dmesg | grep -i hv
    hv_vmbus: Hyper-V Host OS Build:8432-6.2-0-0.0
    hv_vmbus: child device vmbus_0_1 registered
    hv_vmbus: child device vmbus_0_2 registered
    hv_vmbus: child device vmbus_0_3 registered
    hv_vmbus: child device vmbus_0_4 registered
    hv_vmbus: child device vmbus_0_5 registered
    hv_vmbus: child device vmbus_0_6 registered
    hv_vmbus: child device vmbus_0_7 registered
    hv_vmbus: child device vmbus_0_8 registered
    hv_vmbus: child device vmbus_0_9 registered
    hv_vmbus: child device vmbus_0_10 registered
    hv_vmbus: child device vmbus_0_11 registered
    hv_vmbus: child device vmbus_0_12 registered
    hv_vmbus: registering driver hv_storvsc
    hv_vmbus: registering driver hv_netvsc
    hv_netvsc: hv_netvsc channel opened successfully
    hv_netvsc vmbus_0_10: Device MAC xx:x:xx:xx:xx:xx link state up
    hv_timesource: Registering HyperV clock source
    hv_vmbus: registering driver hid_hyperv
    hv_utils: Registering HyperV Utility Driver
    hv_vmbus: registering driver hv_util
    hv_utils: KVP: user-mode registering done.

    I may try to hack up a good verison.

    Microsoft, why not supply SRPMs for this stuff if you arent going to properly support the OS?

    Tuesday, July 10, 2012 6:20 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Note to all. These LIS 3.3 tools are totally unusable in the real world. in fact, they are useless to even test with, as the kernel they work with is so old its irrelevant.
    Tuesday, July 10, 2012 6:22 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Note to microsoft, in the redhat support model, there is no 6.0/6.1/6.2/6.3. Redhat is now on a continuous release. The point releases are simply rollups. Its like Service pack levels at this point.
    Tuesday, July 10, 2012 6:28 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    more keyword fodder for better SEO

    hv_utils  Unknown symbol vmbus_driver_unregister  vmbus_sendpacket vmbus_prep_negotiate_resp vmbus_close  vmbus_recvpacket vmbus_open __vmbus_driver_register


    Also, microsoft, metro is so bad on a server. I had to install firefox and start8 from stardock right away, its impossible to find stuff.

    Tuesday, July 10, 2012 6:35 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    I got it working. Kind of cheesy, but it works.

    - Take RHEL 6.3. Install it. Use the legacy driver and do whatever you need to do before you install the rpm to support the better driver.

    - Get the LIS 3.3 ISO. Mount it. I copied the files off into a dir and unmounted the CD.

    - Downgrade the kernel. get the 6.0 release kernel (do not use -Uvh).

    rpm -i kernel-2.6.32-71.el6.x86_64.rpm

    - reboot. things should work.

    - install the LIS tools with ./install.sh:

    install.sh
    kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    microsoft-hyper-v-debuginfo-rhel63.3-4.20120605.x86_64.rpm
    microsoft-hyper-v-rhel63.3-4.20120605.src.rpm
    microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    microsoft-hyper-v-rhel63.3-4.20120606.src.rpm
    upgrade.sh

    - reboot.

    - now upgrade the kernel back to the current version:

    rpm -ivh --nodeps --replacepkgs kernel-2.6.32-279.el6.x86_64.rpm

    check grub for proper kernel as default.

    reboot.

    everything *seems* to work.

    eg, the modules are in memory, and the ethernet (modern one, not legacy) works.

    [root@localhost ~]# dmesg | grep -i hv
    hv_vmbus: Hyper-V Host OS Build:8432-6.2-0-0.0
    hv_vmbus: child device vmbus_0_1 registered
    hv_vmbus: child device vmbus_0_2 registered
    hv_vmbus: child device vmbus_0_3 registered
    hv_vmbus: child device vmbus_0_4 registered
    hv_vmbus: child device vmbus_0_5 registered
    hv_vmbus: child device vmbus_0_6 registered
    hv_vmbus: child device vmbus_0_7 registered
    hv_vmbus: child device vmbus_0_8 registered
    hv_vmbus: child device vmbus_0_9 registered
    hv_vmbus: child device vmbus_0_10 registered
    hv_vmbus: child device vmbus_0_11 registered
    hv_vmbus: child device vmbus_0_12 registered
    hv_vmbus: registering driver hv_storvsc
    hv_netvsc module is older than RHEL 6.2 ... applying fixups
    hv_vmbus: registering driver hv_netvsc
    hv_netvsc: hv_netvsc channel opened successfully
    hv_netvsc vmbus_0_11: Device MAC 00:15:5d:cc:70:00 link state up
    hv_vmbus: registering driver hid_hyperv
    hv_utils: Registering HyperV Utility Driver
    hv_vmbus: registering driver hv_util
    hv_utils: KVP: user-mode registering done.
    [root@localhost ~]# lsmod | grep -i hv
    hv_utils                6085  0
    hv_netvsc              23141  0
    hv_storvsc             10372  2
    hv_vmbus               93781  4 hv_utils,hid_hyperv,hv_netvsc,hv_storvsc
    [root@localhost ~]# ethtool -i eth0   
    driver: tulip
    version: 1.1.15
    firmware-version:
    bus-info: 0000:00:0a.0

    root@localhost ~]# uname -a
    Linux localhost 2.6.32-279.el6.x86_64 #1 SMP Fri Jun 22 12:19:21 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

    Its not perfect, but it seems to work.

    • Proposed as answer by Sole Sysadmin Friday, July 13, 2012 12:49 PM
    Tuesday, July 10, 2012 7:10 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Can you show me how to get the proper kernel?  I tried

    rpm -i kernel-2.6.32-71.el6.x86_64.rpm

    But since I don't have that source RPM on the filesystem I don't know where to get it from or where to put it.  I have IP connectivity to the Guest VM running CentOS6.3

    Thursday, July 12, 2012 8:31 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I had the same problem when installing CentOS 6.3 with Integration Services 3.3 on Windows 8 Release Preview in Hyper-V.

    failed dependencies:

    kernel(clocksource_register) = 0xd88be65d is needed by kmod-microsft-hyper-vrhel63.3-4.20120605.x86_64

    KMOD RPM installation failed, Exiting.

    You can still install Integration Services 3.3 on CentOS 6.3 with the following procedure. I tried it on my own installation and it worked. I have installed CentOS using Minimal installation CD.

    1. Create your VM with a Legacy Network Adapter
    2. Boot your VM and note MAC@ of your Legacy Network Adapter
    3. Install CentOS 6.2 - Minimal Installation
    4. Check if legacy network adapter has been correctly installed - ifconfig -a
    5. Install Microsoft Integration Services 3.3
    6. Shutdown your VM
    7. Delete Legacy Network Adapter
    8. Add Network Adapter with static MAC@ you noted above
    9. Boot your VM and configure your Network Adapter. DHCP did not worked in my installation, however add a static IP@ worked perfectly
    10. Update your VM with latest packages.
    11. Reboot and you should see that you are in CentOS 6.3

    I hope this little 11 steps will help installing Centos 6.3. I for my part did not understand why you could upgrade an CentOS 6.2 Installation to 6.3 and there will be no problems with Microsoft Integration Services, but if you install CentOS 6.3 from scratch, you will not be able to install Microsoft Integration Services.

    Bye, bye

    Gillato

    • Proposed as answer by Gillato Thursday, July 12, 2012 9:29 PM
    Thursday, July 12, 2012 9:29 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    Instead of trying to get the 6.3 install to work, I just installed 6.1 as I did in the past (with the 3.0 integration components) and updated RHEL to 6.3 via yum. That has worked well and seems to be the easiest path (at least for me). 
    Monday, July 16, 2012 2:34 PM
    |
  • Question
    Sign in to vote
    21
    Sign in to vote

    Good evening,

         I found that the quickest way to get the Hyper-V Linux Integration Services 3.3 installed on RedHat / CentOS 6.3 was to use the --nodeps parameter for rpm, which disables the dependency check for that package.  You must install both packages manually rather than using the install.sh script, but afterwards, everything seems to work just fine.  This way you can install CentOS 6.3 without reverting to an older version and also allows you to upgrade an existing system with the new services.  So, the commands would be:

    rpm -Uvh --nodeps kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm
    rpm -Uvh --nodeps microsoft-hyper-v-rhel63.3-4.20120605.x86_64.rpm

        Be sure to install the kmod package first, then the hyper-v package.  Also, until a newer package is released that doesn't complain about the misplaced register, you will get warnings when using yum to update, but even with a kernel update the services remain functional.  Hope this helps.



    Update:  The Hyper-V Linux Integration Services 3.4 have been released by Microsoft and resolve the issue for which this workaround was created.  Please use the v3.4 services instead of the v3.3 services for successful Linux deployment in Hyper-V.  As an FYI, I tested this on Windows Server 2012 as well and it works great and is correctly recognized by SCVMM.  The v3.4 services can be downloaded here.

    • Proposed as answer by DuaneBV Tuesday, July 17, 2012 1:58 AM
    • Unproposed as answer by DuaneBV Tuesday, July 17, 2012 1:58 AM
    • Proposed as answer by DuaneBV Tuesday, July 17, 2012 1:59 AM
    • Edited by DuaneBV Sunday, September 16, 2012 11:33 PM
    Tuesday, July 17, 2012 1:56 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    DuaneBV,

    Good post, really helpful.

    To moderators,

    Could you delete couple completely useless posts from KalpeshPatel.ce on the top, please?

    Apparently, his has no idea what he is talking about, probably copy-pasting something.

    Saturday, July 28, 2012 5:00 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Good evening,

    thank you DuaneBV for your post. It is way easier to do than my recommandation and you can do it on a fresh install of RedHat / CentOS 6.3. I will try it when I am back from vacation.

    Bye

    Gillato

    Monday, July 30, 2012 10:11 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    DuaneBV I think you just saved my evening. Thanks.

    Edit: Ok now I KNOW you just saved my evening. I have a mouse in my Virtual Machine yay!

    • Edited by J.Helman Monday, July 30, 2012 10:33 PM
    Monday, July 30, 2012 10:32 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the post DuaneBV

    However, it dos not with the 32-bit version i386 of CentOS 6.3: after manually installing Linux IC 3.3, the VM hangs on Mounting local filesystems (I had to disable the quiet mode of Grub to see where it hangs)

    But it works as charm with the 64-bit x86_64!!!

    • Edited by SvetPaperov Wednesday, August 1, 2012 12:23 PM
    Tuesday, July 31, 2012 7:52 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    DuaneBV

    After these steps, I lost my cdrom (centos .. / dev) .. how to get it back now?

    Wednesday, August 8, 2012 6:56 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the post DuaneBV

    However, it dos not with the 32-bit version i386 of CentOS 6.3: after manually installing Linux IC 3.3, the VM hangs on Mounting local filesystems (I had to disable the quiet mode of Grub to see where it hangs)

    But it works as charm with the 64-bit x86_64!!!

    I've just been messing with this for the last few hours but with Scientific Linux i386. Looks like it just wont work with the 2.6.32-279 (6.3) kernel. Looking back at the docs, Microsoft have only explicitly said 6.0-6.2 will work with the v3.3 Hyper-V tools.

    If you go back to the 2.6.32-220 (6.2) kernel it works fine, so clearly something has changed in between. Mucking around with the SRPMs might net some success but I'll probably just stick it out on the 6.2 kernel for now.

    Thursday, August 9, 2012 11:40 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    Michael60,

         With the Hyper-V Integration Components Installed, you will not, by default, see the /dev/sr0 device.  In order to make the CDROM device available again with the services installed, you will need to run the following command to enable the appropriate kernel module:

    # insmod /lib/modules/$(uname -r)/kernel/drivers/ata/ata_piix.ko

    This is detailed in the following forum post:

    Centos 6.0, LIC 3.1, No CDROM

    Hope this helps you out.


    • Edited by DuaneBV Tuesday, August 14, 2012 7:16 PM
    Tuesday, August 14, 2012 7:15 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    DuaneBV

    Thank you!
    I've seen this solution, but it did not work for some reason,then, obviously I was wrongin the syntax
    Now, all happened

             
    Tuesday, August 14, 2012 8:00 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Running into the same issues but mainly I have now problems updating to security-related Kernel udpates from RedHat because of this - is there any way a soluition to this issue - it basically means that I have to massage our RedHat VMs at every freaking Kernel update because of this Package dependeny and/or removed symbols.

    I should add that Scientifix Linux dev VMs (while unsupported for LIS) run happily so the SL developers must have fixed this somehow themselves but our production run RHEL...

    • Edited by koffi2k Friday, August 17, 2012 11:39 AM
    Friday, August 17, 2012 11:28 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    This beginning to be really a pain for daily system maintenance:

    ERROR with rpm_check_debug vs depsolve:
kernel(clocksource_register) = 0xd88be65d is needed by (installed) kmod-microsoft-hyper-v-rhel63.3-4.20120605.x86_64
Transaction encountered a serious error.

    Please Microsoft:
    Release some updated packages for Enterprise Linux 6.3 that fix this problem, it's annoying that I need to force dependency ignorance or remove/reinstall the Hyper-V integration at every Kernel update from RedHat ATM.

    If there is a better way to omit this, I'd be happy to know about but currently it's just beginning to turn into a real annoyance.

    Saturday, August 25, 2012 7:31 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Thanks for the post DuaneBV

    However, it dos not with the 32-bit version i386 of CentOS 6.3: after manually installing Linux IC 3.3, the VM hangs on Mounting local filesystems (I had to disable the quiet mode of Grub to see where it hangs)

    But it works as charm with the 64-bit x86_64!!!

    I encounter the same issue with CentOS, is there any other tried workaround besides what is already described ?

    My initial system was running IC 3.0 with 2.6.32-71.29.1.el6.i686

    I have tried so far:

    1) Installing IC 3.3 on 2.6.32-71.29.1.el6.i686, upgrading kernel to 2.6.32-279.5.2.el6.i686. Booting 2.6.32-71.29.1.el6.i686 works, booting 2.6.32-279.5.2.el6.i686 hangs at Mounting local filesystems

    2) Booting with 2.6.32-71.29.1.el6.i686 (2.6.32-279.5.2.el6.i686 installed on system) tried rpm -Uvh --force --nodeps kmod-microsoft-hyper-v-rhel63.3-4.20120606.i686 and rpm -Uvh --force --nodeps microsoft-hyper-v-rhel63.3-4.20120606.i686. Booting old kernel works, new kernel hangs at the same point

    3) Completely removing IC 3.3 in order to boot with 2.6.32-279.5.2.el6.i686 and force install IC 3.3 had catastrophic results

    I am trying to figure out a possible sequence of events - workarounds in order to end up with IC 3.3 with a recent 32 bit kernel

    Downgrading to IC 3.0 could be the part of another workaround ? Or IC 3.0 has the same (or worse) problems with recent 32 bit kernels ?

    Thanks


    • Edited by spirosk Wednesday, September 5, 2012 12:12 PM
    Wednesday, September 5, 2012 12:11 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    this worked for me, thanks.

    Microsoft, This is why we are a VMWare shop. I only use Hyper-V on my smaller clients that cannot afford VMWare.

    Sunday, September 9, 2012 6:32 PM
    |
  • Question
    Sign in to vote
    5
    Sign in to vote

    Just as a heads up, v3.4 of the integration services is now out and available here,

    Installed them yesterday on to a 64bit CentOS 6.3 VM without a problem.

    • Proposed as answer by nickpl Monday, September 10, 2012 3:02 PM
    Monday, September 10, 2012 6:56 AM
    |
  • Question
    Sign in to vote
    1
    Sign in to vote

    It also seems that it contains update LIS for RHEL5.x - including additional (official) support for CentOS 5.7 and 5.8

    I just installed 3.4 on a test VM on both Scientific Linux 6.3 (officially unsupported, but works here) and real RHEL 6.3, so far, so good.
    Finally, this situation made me quite grumpy though, running and fixing broken dependencies after every kernel update ends (till 6.4?). ;)

    Tuesday, September 11, 2012 12:40 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Just as a heads up, v3.4 of the integration services is now out and available here,

    Installed them yesterday on to a 64bit CentOS 6.3 VM without a problem.

    Thanks a lot.
    Thursday, September 13, 2012 3:58 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote
    I tested the v3.4 services on both 6.x and 5.x CentOS 64-bit distributions and they both work great.  Nice to see that it has finally been resolved.
    Sunday, September 16, 2012 11:29 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    Not for me.

    -bash-4.1# rpm -qa | grep microsoft
    kmod-microsoft-hyper-v-rhel63.3.4-1.20120727.x86_64
    microsoft-hyper-v-rhel63.3.4-1.20120727.x86_64
    -bash-4.1# rpm -qa | grep kernel
    dracut-kernel-004-284.el6_3.noarch
    kernel-2.6.32-279.9.1.el6.x86_64
    kernel-firmware-2.6.32-279.9.1.el6.noarch
    kernel-2.6.32-220.23.1.el6.x86_64

    -bash-4.1# modprobe hv_netvsc
    FATAL: Error inserting hv_netvsc (/lib/modules/2.6.32-279.9.1.el6.x86_64/weak-updates/microsoft-hyper-v/hv_netvsc.ko): Connection timed out
    -bash-4.1# lsmod | grep hv
    -bash-4.1# 

    Thursday, September 27, 2012 8:19 AM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Because I have limited VM RAM and thus used the text installer, I had to manually enable networking by following the tail end of this post to create the required configuration files:

    RHEL/CentOS 6.2 on Hyper-V 2008 R2 with LIC v3.2

    Specificall, the portions under "When VM is rebooted you will notice that there is no network connectivity to your VM. Follow steps below for configuring network connectivity"

    Friday, October 5, 2012 5:36 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    Finally Microsoft has LIS3.4 that fixed all the problems.  Make sure you follow the PDF instructions.  If you have the network problem like I do, find the solution in page 10.

    http://www.microsoft.com/en-us/download/details.aspx?id=34603

    • Edited by hattedbey Sunday, December 2, 2012 6:02 PM
    • Proposed as answer by hattedbey Sunday, December 2, 2012 6:02 PM
    Sunday, December 2, 2012 6:01 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    i have the same problem.

    do as you say, degrade the kernel to 2.6.32-71.el6, then it works.

    thanks very much :)

    but what's mean "ldconfig: /etc/ld.so.conf.d/kernel-2.6.32-71.el6.x86_64.conf:6: hwcap index 1 already defined as nosegneg"


    • Edited by LiuLe Saturday, December 8, 2012 3:34 PM
    Saturday, December 8, 2012 3:34 PM
    |
  • Question
    Sign in to vote
    0
    Sign in to vote

    1. Install CentOS 6.3

    2. Download Linux Integration Disk 3.4 for HyperV

    3. Mount the ISO Image file.

    mount /dev/cdrom/media

    4. Run INSTALL.sh under Linux Integration Services CD's RHEL63 Folder.

    /media/RHEL63/install.sh

    5. Create IFCFG-ETH0 file.

    nano /etc/sysconfig/network-scripts/ifcfg-eth0

    6. Insert following lines

    DEVICE=eth0
    BOOTPROTO=dhcp
    ONBOOT=yes

    7. SAVE and QUIT

    8. Edit or Create Network File

    nano /etc/sysconfig/network

    9. Insert following lines

    NETWORKING=yes
    HOSTNAME=server-name.company.lan

    10. Restart and now you can ping out


    • Edited by Torsten Jahnke Monday, March 25, 2013 11:08 AM
    • Proposed as answer by AnthonyDa Saturday, October 31, 2015 12:35 PM
    Monday, March 25, 2013 11:06 AM
    |