Parallels Tools Breaks in Fedora 20 Kernel 3.17.2

Discussion in 'Linux Virtual Machine' started by Mark Fine, Nov 12, 2014.

  1. Mark Fine

    Mark Fine Pro

    Messages:
    482
    ...and trying to reinstall Parallels Tools under 3.16.* breaks the graphics engine. If that happens, need to use the attached instructions.
    Would have typed them in the body of this post but got a "Use English" error after trying to post it, ffs.
     

    Attached Files:

  2. Mark Fine

    Mark Fine Pro

    Messages:
    482
    Did some investigating under kernel 3.17.3 and found a problem in the pvmnet module: macro alloc_netdev added an extra third argument ("name_assign_type") before "setup". Make.log (renamed "make.txt") attached.
     

    Attached Files:

  3. Mark Fine

    Mark Fine Pro

    Messages:
    482
    Fixed!
    Apply the attached simple changes to "pvmnet.c" and run "dkms install parallels-tools/9.0.24251.1052177" all as root.
    The changes basically add the argument for 3.17 kernels. That's all that was needed.
     

    Attached Files:

    Daniel Rodrigue likes this.
  4. rhoekstra

    rhoekstra Junior Member

    Messages:
    10
    Not everyone is perhaps too inclined with patching files, so I politely try to add some information..

    In short, follow these few steps:
    - Boot into old (previously working, 3.16) kernel (in my case, that one was also non graphical this time)
    - mount Parallels Tools cd and install tools
    - Download, correct and apply patch file
    - Reboot to new (3.17) kernel

    When back on older kernel (3.16.x) which worked before, select 'reinstall tools' from the actions menu in parallels. (you will have a non-graphic vm at this point, as I did. you can SSH into the system or (perhaps) enter the local login as described in attachment of OP.

    mount cd (create a dir under /mnt called 'cd' and execute 'mount /dev/cdrom /mnt/cd', run install and the install _should_ succeed (as was in my case).
    Then, go to /usr/src/parallels-<latest-version>, assuming you have the latest version of parallels tools installed now.
    descend to the subdirectory prl_eth/pvmnet directory (so in my case: /usr/src/parallels-tools-10.1.1.28614/prl_eth/pvmnet)
    now make sure you have 'patch' installed for the patch to be applied. (yum install patch)

    To use patch, the above provided diff.txt file needs to have the correct format. For me it was not in the right format when I downloaded it. I had to enter vi and execute the next command:
    ':%s/^M/^M/g' (^M obtained by the sequence Ctrl-V Ctrl-M, both times)
    ':wq' (to save and exit the file)

    Then, from the above mentioned pvmnet directory (remember where you stored the diff.txt file mentioned above), execute 'patch -n -p0 <pvmnet.c.diff.txt'. It will ask which file to patch, enter 'pvmnet.c' and if all is set fine, it'll show it successfully applied the patch.

    Now all I did was reboot and boot into the newest kernel. The dkms applies the driver automatically to the new kernel and because of the patch we just applied it will succeed this time.

    My two cents to aid in resolving a non-graphical 3.17 kernel VM in Parallels Desktop
     
    Daniel Rodrigue likes this.
  5. Mark Fine

    Mark Fine Pro

    Messages:
    482
    Thanks for expanding on the procedure. I should also point out that you might not have to mount the Tools CD virtually. Might want to check either of the following (replacing 9.0.24252.1052177, below, with your version of Parallels):
    /var/lib/dkms/parallels-tools/9.0.24251.1052177/source/prl_eth/pvmnet/pvmnet.c
    /usr/src/parallels-tools/9.0.24251.1052177/source/prl_eth/pvmnet/pvmnet.c
    The source code might already be there.
     
  6. rhoekstra

    rhoekstra Junior Member

    Messages:
    10
    True, though in my situation it wasn't. Perhaps because Parallels got updated in the last period without updating the tools, so that could be it. In that case, that step can be skipped:)
     

Share This Page