locked
How Do I Install Integration Services on Fedora Linux Distribution? RRS feed

  • Question

  • Hello,

    I've converted from my Fedora 14 virtual setup I used in VMware solution. Now I am stuck because I don't have any synthetic device on this virtual machine, and I need at least Network Interface Card.

    I downloaded Integration Services components for Linux but can't get it install on Fedora 14.

    Any clue on how it could be possible if so?

    Currently I only managed to get NIC by adding Legacy Network adapter to this Linux virtual machine.

    Thank you.


    Well this is the world we live in And these are the hands we're given...


    • Edited by Exotic Hadron Monday, August 27, 2012 3:01 PM
    • Moved by Nicholas Li Tuesday, August 28, 2012 2:00 AM (From:Windows 8 Virtualization)
    Monday, August 27, 2012 2:50 PM

Answers

  • First: Fedora 14 is End-of-Life, which means that you won't get any Bugfix or Security updates for this Distribution since December 2011.
    Definitely consider updating sooner than later if it anything production use.

    Short version:
    Upgrade your VM to a recent Fedora release and use the in-kernel Hyper-V support and forget about LIS.
    Same applies to Ubuntu, Debian and not directly supported by MS via extra packages.

    Long version:
    Although Fedora is the base for RedHat EL (6.x actually is based on F12), it doesn't mean binary drivers made for RHEL 6 will run on Fedora.
    Meanwhile RHEL 6 has derived heavily from Fedora 12 origins, being stabilized for getting 10y of maintenance. The kernel in RHEL6 is quite different from the Fedora 14 kernel you have.

    The LIS 3.x binary drivers released from Microsoft for RHEL6 are not meant to run on Fedora or any other distro MS doesn't say so.
    The only exception being "pure" RHEL clones, like CentOS or (not officially) Scientific Linux, possibly OEL when using the original RHEL kernel.

    What you want to use, are the in-kernel Hyper-V drivers declared stable since Linux kernel 3.4 (starting 3.2 I think they were already quite fine). F14 was using the 2.6.35 kernel, that's when the upstream Hyper-V driver was in early stages. Most distributions disabled the drivers in their builds because they were not production ready.

    • Proposed as answer by koffi2k Thursday, August 30, 2012 3:25 PM
    • Marked as answer by Exotic Hadron Friday, August 31, 2012 12:07 PM
    Thursday, August 30, 2012 3:25 PM

All replies

  • Hi,

    What did you mean by “can't get it install on Fedora 14”? Did you get any errors?

    By the way, when you download Integration Services, you should be able to find a guide to install Integration Services on Linux.

    Tuesday, August 28, 2012 4:57 AM
  • Hi, Vincent,

    Yes, exactly. The install shell script returns lots of kernel dependency errors.

    There's a guide but it speaks for RHEL and CentOS distributions. It's a well-known fact that RHEL is, I am citing: "Red Hat Enterprise Linux (or RHEL) is a commercially supported derivative of Fedora tailored to meet the requirements of enterprise customers. It is a commercial product from Red Hat which also sponsors Fedora as a community project. Fedora is upstream for Red Hat Enterprise Linux but there are several other Derived distributions  available too." So, technically, install script should work on Fedora distribution, but it does not. Possibly, I should manually choose a specific tarball with Integration Services? If so, which one should I use?

    Thank you for your help.


    Well this is the world we live in And these are the hands we're given...

    Tuesday, August 28, 2012 7:52 AM
  • Here is the excerpt from the list of errors I get when running ./install.sh bash script on either edition of Fedora starting from 14 though the latest 17 release (haven't tried on the unsupported R18):

    The PDF "Linux Integration Services v3.3 Read Me" Guide that comes with Integration Services distribution gives to information about what rpm package should be used when the ./install.sh failed to work.

    Honestly, I find the guide incomplete.

    Guidance to mount cdrom

    # mount /dev/cdrom /media 

    is quite okay although even myself I know how to mount devices in Linux being an absolute layman in Linux.

    I'd rather be interested in how do I use another rpm package. But I don't event know how does one package differ from another. There's no information provided in this guide!

    I'd appreciate any help.

    Thank you.


    Well this is the world we live in And these are the hands we're given...


    Thursday, August 30, 2012 1:12 PM
  • First: Fedora 14 is End-of-Life, which means that you won't get any Bugfix or Security updates for this Distribution since December 2011.
    Definitely consider updating sooner than later if it anything production use.

    Short version:
    Upgrade your VM to a recent Fedora release and use the in-kernel Hyper-V support and forget about LIS.
    Same applies to Ubuntu, Debian and not directly supported by MS via extra packages.

    Long version:
    Although Fedora is the base for RedHat EL (6.x actually is based on F12), it doesn't mean binary drivers made for RHEL 6 will run on Fedora.
    Meanwhile RHEL 6 has derived heavily from Fedora 12 origins, being stabilized for getting 10y of maintenance. The kernel in RHEL6 is quite different from the Fedora 14 kernel you have.

    The LIS 3.x binary drivers released from Microsoft for RHEL6 are not meant to run on Fedora or any other distro MS doesn't say so.
    The only exception being "pure" RHEL clones, like CentOS or (not officially) Scientific Linux, possibly OEL when using the original RHEL kernel.

    What you want to use, are the in-kernel Hyper-V drivers declared stable since Linux kernel 3.4 (starting 3.2 I think they were already quite fine). F14 was using the 2.6.35 kernel, that's when the upstream Hyper-V driver was in early stages. Most distributions disabled the drivers in their builds because they were not production ready.

    • Proposed as answer by koffi2k Thursday, August 30, 2012 3:25 PM
    • Marked as answer by Exotic Hadron Friday, August 31, 2012 12:07 PM
    Thursday, August 30, 2012 3:25 PM
  • Hello,

    Thank you for your response!

    As you might see from the screenshot attached, the install script has been run in Fedora 17 (which is the latest officially released excluding edition 18).

    That's why I wrote:

    Here is the excerpt from the list of errors I get when running ./install.sh bash script on either edition of Fedora

    starting from 14 though the latest 17 release (haven't tried on the unsupported R18)

    I've tried install scripts on all editions: 14, 15, 16, and 17 (all of i686 flavor). I did NOT work in either.

    Thank you for your help!


    Well this is the world we live in And these are the hands we're given...

    Thursday, August 30, 2012 8:46 PM
  • Thank you.
    Now everything is clear.

    To sum up:

    • Staring from Fedora Release 16 (any edition that includes kernel version 3.4.x or later) there's no need to install LIS (Linux Integration Services). Fedora provides for navtive Hyper-V support. You'll notice that by the fact that your mouse pointer will automatically jump from the VM window to the parent partition and back to child partition without you having to install LIS.
    • Despite the Red Hat claim that RHEL is mostly commercial flavor of community-orienter Fedora project, both kernels are quite different leading dependency errors to appera while compiling RHEL code on Fedora.

    Thank you, koffi2k, for your help.


    Well this is the world we live in And these are the hands we're given...

    Friday, August 31, 2012 1:40 PM
  • To sum up:

    Staring from Fedora Release XX  there's no need to install LIS (Linux Integration Services).

      Best var:

       there's no need to install LIS (Linux Integration Services) on Fedora _any_ version, because, as write koffi2k:

      ==

      The LIS 3.x binary drivers released from Microsoft for RHEL6 ( VVM: LIS v3.4 also RHEL58 + RHEL57) are not meant to run on Fedora or any other distro MS doesn't say so.
      The only exception being "pure" RHEL clones, like CentOS or (not officially) Scientific Linux, possibly OEL when using the original RHEL kernel.

      ==


    Friday, September 14, 2012 12:24 PM
  • To sum up:

      • Staring from Fedora Release 16 (any edition that includes kernel version 3.4.x or later)
      ==

     Facts:

    1)  See , for example,  http://distrowatch.com/table.php?distribution=fedora 

    2011/05/24  Fedora v15 (  lovelock )   kernel v2.6.38.6

    2011/11/08  Fedora v16 (  verne )   kernel v3.1

    2012/05/29  Fedora v17 ( beefy )   kernel v3.3.4

     2)

    In Fedora  do "enable HyperV drivers" _after_ 2012-04-12 :


    http://lists.fedoraproject.org/pipermail/test/2012-April/106870.html
    ===
    ...


     . . .
    kernel-3.4.0-0.rc2.git2.1.fc18
    ------------------------------
    * Thu Apr 12 2012

       . . .

    * Wed Apr 11 2012 Justin M. Forbes <jforbes at redhat.com>
    - enable HyperV drivers


     . . .


    ...
    ===

    i.e. _before_  2012-04-12 -- need recompile kernel, etc.

    Z)

    Total: _best_ wait Fedora 18

     Future / detail can found on

    http://vvm.blog.tut.by/2012/08/22/fedora-18-on-hyper-v/

    ~


    Friday, September 14, 2012 12:30 PM
  • 2012-01-13:

     See in my later message:

    ==

    IMHO,  Bug 883005 is minor issue related *-netinstall.iso ( in *LiveCD*.iso mouse work as need )

    ==

    2013-01-09:

    To All : please help me with communication with Fedora Development team

    http://vvm.blog.tut.by/2012/08/22/fedora-18-on-hyper-v/

    ==

     De-facto Bug 883005 is well-known problem Mouse Integration in Linux guest

       -- Sub-problem N1

    Fedora-18-development-x86_64-2013-01-08 problem Mouse Integration in Linux guest  

      Ok, as temporary solution do this:

    mouse work in Linux Guest without "MS Vmbus HID-compliant Mouse", if connect to it from Windows _directly_

    http://vvm.blog.tut.by/2011/02/22/hyper-v_mouse_in_linux/
    ==
    . . .
    Without "Microsoft Vmbus HID-compliant Mouse" ,
    mouse work in {Linux Guest without hid_hyperv} if connect to it from {Windows physical workstation} _directly_
    . . .
    ==

       -- and imm. after solve N1, we look Sub-problem N2 i.e.
    CTRL + ALT + Left Arrow to release the mouse

    http://blog.allanglesit.com/2010/05/ubuntu-and-hyper-v-the-paths-to-enlightenment/
    ==
     Mouse Integration

    When a user uses Hyper-V Management Console or System Center Virtual Machine Manager to connect to a VM [ with Linux without "MS Vmbus HID-compliant Mouse" ]
    and they begin to interact with the desktop via the mouse, they find themselves in an interesting situation where they are unable to reclaim their mouse pointer from the VM without entering a somewhat cryptic keystroke ctrl + alt + left arrow.
    ==

    Fedora-18-development-x86_64-2013-01-08 problem CTRL + ALT + Left Arrow to release the mouse

    >(In reply to comment #5)
    >> (In reply to comment #4)

    JB>>> The Fedora kernel builds and provides those modules,
    JB>>> but they aren’t included in the initramfs.
    VVM>> Yes
     
     
    JB>>> If they should be (and I have no idea),
    JB>>>then dracut probably needs to include them.
    VVM>> Do not worry :-) , they should be include

    N.Ch.> Why ?
    N.Ch.> I’m using Server2012 Eval x86_64 and at the end of the install, I have:

    {
    ==
    # lsmod | grep hyperv
    hid_hyperv 13059 0
    hv_vmbus 33752 4 hv_netvsc,hid_hyperv,hv_utils,hv_storvsc
    ==

    VVM 2013-01-09: It self this state of loading kernel modules is fine,
    but see later
    "at end of the install" -- is to late, need "at begin of the install"

    }

    N.Ch.> Despite thoses are not included in the initramfs,
    N.Ch.>they are probably not useful during the boot phase?
    N.Ch.>(maybe hv_storvsc should be made available thought).

    !) Mouse ( as phisical/material device) is used, primary, by end-user/sysadmin for work with user interface of Fedora installer

    Of course, if You use fully automated install mode ( for example, by script) worked state of mouse kernel module not important

    But in _interactive_ mode -- "worked state of mouse kernel module" is welcom!


    1) Of course,
    driver ( ok, "kernel module" ) for SCSI and IDE disks ( hv_storvsc) is more important, what driver for mouse ( hid_hyperv)

    2)"at end of the install" -- is to late, need "at begin of the install"

    2b)
     
     How exactly method:
     by
    -- "dracut needs to include hid_hyperv"
     Or by
    -- "hid_hyperv need be include in the initramfs"

    will be choice by Fedora Development team

    ==



    Wednesday, January 9, 2013 12:50 PM
  • Hi, Victor,

    Thank you for sharing this info.

    Could you please confirm that I understood this correctly? The issue now is that in R18 of Fedora the HID driver is not integrated in Linux core, correct? Or this integration does not work correctly? The fact that you need to press keyboard shortcut to get your mouse pointer released from the VM window signals that the VM HID driver does NOT work, right?


    Well this is the world we live in And these are the hands we're given...

    Sunday, January 13, 2013 3:17 PM
  •  The issue now is that in R18 of Fedora the HID driver is not integrated in Linux core, correct? Or this integration does not work correctly? The fact that you need to press keyboard shortcut to get your mouse pointer released from the VM window signals that the VM HID driver does NOT work, right?


    ~

     IMHO,  Bug 883005 is minor issue related *-netinstall.iso ( in *LiveCD*.iso mouse work as need )

    See later *.png with example _good_ work mouse driver , look on hid_hyperv in lsmod output

    ~

    How exactly Fedora Team fixed this issue , not principial for me

    ~

    ~

    ~

    ~

    ~

     About another, more dangerous bug:

    on 2013-01-13  IMHO, Bug 810040 is solved {

    ~

    ~

    2013-01-09  b) Bug 810040

      Problem is solved? or not?
    ==
    2012-12-21 10:23:59 EST http://cgit.freedesktop.org/libfprint/fprintd/patch/?id=9577b6db03115c78f90bb644348ef765f00d95d9 5) yum update *.rpm 6) telinit 3; telinit 5; No gnome-shell error 7) Reboot VM and verify no gnome-shell error Now for KVM guests via libvirt, disabling USB is not something most people will do. However xen and other virt platforms don't seem to add a USB bus by default so this bug makes fedora and gnome look pretty bad. halfline, hadess, can someone spin up F17 and F18 updates?
    I've tested the upstream patch, and it worksforme on F18. Here's my steps:
    
    1) Install F18 beta guest (w/ kvm + virt-manager), verify I can log into gnome shell, shutdown VM
    2) Edit VM XML to disable USB:
    * virsh edit <vmname>
    * remove <input type='tablet' bus='usb'/>
    * change <controller type='usb' index='0'> to <controller type='usb' index='0' model='none'>
    * save and exit
    
    3) start VM, verify you see the gnome shell fail screen
    4) build local F18 fprintd rpm adding this patch: 
     . . .
    2013-01-09 08:25:16 EST
    -1 blocker, this seems to be enough of a corner case to not warrant a release blocker.
    2013-01-08 18:21:29 EST 0/fprintd-pam-0.4.1-4.fc18.x86_64.rpm Tested with Success on Hyper-V Server 2012 x86_64 (Fedora-18 x86_64 Guest) I was able to login with gnome3. Why this was not added into the repo more early? This bug should have been considered as a blocker IMHO. (or NTH at least). This affect the ability to have a usable system at the end of a graphical install in order to later make updates.
    Scratch build implementing #c43 
    . . . 
    2013-01-08 19:00:48 EST
    fprintd-0.4.1-4.fc18 has been submitted as an update for Fedora 18.
    https://admin.fedoraproject.org/updates/fprintd-0.4.1-4.fc18
     . . .
     . . .

    ==



    2013-01-10 13-15 ( GMT +03 ):

      I'm think,

    adamwill.fedorapeople.org 20130109-prerc3-x86_64.iso on Hyper-V the fprintd bug fixed :

    ==

    adamwill.fedorapeople.org 20130109-prerc3-x86_64.iso on Hyper-V the fprintd bug fixed

    ==

    }

    ==

    Comment 98

    VVM> IMHO, Fedora 18 behavior on Hyper-V look like normal
    
     and for
    https://alt.fedoraproject.org/pub/alt/stage/18-RC4/Live/x86_64/Fedora-18-x86_64-Live-Desktop.iso

    ==

    ~

    ~

    ~

    ~

      Except:

    mouse work as need  in *LiveCD*.iso , but not in *-netinstall.iso

    tested with  Fedora 18-RC4

    https://alt.fedoraproject.org/pub/alt/stage/18-RC4/Fedora/x86_64/iso/Fedora-18-x86_64-netinst.iso 




    Monday, January 14, 2013 6:52 AM
  • 2013-10-18:

    Look like whate
    ==
    Bug 883005 is minor issue related *-netinstall.iso ( in *LiveCD*.iso mouse work as need )
    ==

    FIXed in Fedora 20 Alpha 4

    Friday, October 18, 2013 2:44 PM
  • Hello,

    I've converted from my Fedora 14 virtual setup I used in VMware solution. Now I am stuck because I don't have any synthetic device on this virtual machine, and I need at least Network Interface Card.

    I downloaded Integration Services components for Linux but can't get it install on Fedora 14.

    Any clue on how it could be possible if so?

    Currently I only managed to get NIC by adding Legacy Network adapter to this Linux virtual machine.

    Thank you.


    Well this is the world we live in And these are the hands we're given...


    I realise this is probably a few years late, and I hope everyone has already moved on to supported environments :), but for anyone trying to install Linux Integration Services on a legacy system resulting in the error (macro “INIT_WORK” passed 3 arguments, but takes just 2), here's a fix (see this thread for more details). This helped me install LIS v2.1 on Fedora Core 6 with kernel 2.6.20-1.2962.fc6. Obviously, this is an unsupported configuration and attempting it anyway is done at your own risk. Make backups/snapshots!

    mkdir -p /mnt/cdrom
    mount /dev/cdrom /mnt/cdrom
    cp -rp /mnt/cdrom /opt/linux_ic
    umount /mnt/cdrom
    cd /opt/linux_ic
    grep -RnE 'INIT_WORK\((.*),(.*),.*\)' src/*.c # print lines which will be modified by next command
    sed -ri 's/INIT_WORK\((.*),(.*),.*\)/INIT_WORK\(\1,\2\)/' src/*.c # remove third parameter to INIT_WORK calls
    make
    make install

    Regards,

    Valentijn de Pagter

    • Proposed as answer by VBdP Wednesday, July 9, 2014 9:42 AM
    Wednesday, July 9, 2014 9:41 AM