Since people keep asking...
This post contains detailed, step-by-step instructions to apply any Parallels Tools patch provided in this forum.
NOTE: Please know and understand that this process is not for the meek and expects the user to have a fairly good level of Linux administrative skills. It helps if you know what you're doing and what the implications are by performing each step. By following the instructions below, the reader/user accepts any and all risks, which include the possibility of rendering their version of Linux completely inoperable. By accepting these risks, neither the author of this post nor Parallels can be held responsible for any negative outcome, legally or otherwise.
1. Boot into Linux.
2. Ensure the Tools virtual CD is selected by Parallels by selecting it Devices -> CD/DVD -> prl-tools-lin.iso.
3. Become root user.
> su
> <enter superuser password>
4. Mount the Tools virtual CD in your Linux VM.
# mount /dev/cdrom /mnt
5. Copy the full CD to a local directory, and rename it something like *tools_cd* then enter it.
# cp -R /mnt .
# mv mnt tools_cd
# cd tools_cd
6. Navigate to the source code tarball
# cd kmods
7. Untar the source code.
# tar xvpf prl_mod.tar.gz
Can optionally change ownership:
# chown -R <owner>:<group> ../kmods
8. Move the current tar.gz out of the source tree to protect it in case of an error.
# mv prl_mod.tar.gz ../../
9. Apply the patch to the source code or edit the appropriate files manually.
To apply the patch:
# patch -p1 <patch filename>
Optionally, you can edit the individual files manually (what I prefer to do) using the stated file paths and line numbers in the diff as a guide.
Lines to remove are prefaced with a '-'.
Lines to add are prefaced with a '+'.
10. Re-tar/gzip the source tree.
# tar cvpf prl_mod.tar .
# gzip prl_mod.tar
11. If you are not in the new kernel, reboot into it.
# reboot
12. Once in the new kernel, become root user.
> su
> <superuser password>
13. Change to the directory where you copied the Tools CD.
# cd tools_cd
14. Run the installer and follow all installer directions to perform an *Upgrade* to continue.
# ./install
15. The installer will take a while to complete.
16. If the install is successful it will ask you to reboot. If it failed, it's likely that something in Step 9 was done incorrectly. Simply restart from Step 9, ensuring the changes to each file were made correctly. Worst case scenario, copy the saved copy of prl_mod.tar.gz back into tools_cd/kmods and restart from Step 7.
Note: In the event you upgrade your kernel you may fully rebuild Parallels Tools by simply starting from Step 12. There is something about the scripts that do not fully rebuild/install Tools whenever a kernel is updated via dnf.
Restarting from Step 12 can be done repeatedly until which time that Parallels (and hence, Tools) is ever updated again from Parallels. It assumed that Parallels-provided version of Tools will continue to work for a while. However, eventually it will break, in that case you must restart the entire process and apply a whole new patch once those fixes are determined.
This post contains detailed, step-by-step instructions to apply any Parallels Tools patch provided in this forum.
NOTE: Please know and understand that this process is not for the meek and expects the user to have a fairly good level of Linux administrative skills. It helps if you know what you're doing and what the implications are by performing each step. By following the instructions below, the reader/user accepts any and all risks, which include the possibility of rendering their version of Linux completely inoperable. By accepting these risks, neither the author of this post nor Parallels can be held responsible for any negative outcome, legally or otherwise.
1. Boot into Linux.
2. Ensure the Tools virtual CD is selected by Parallels by selecting it Devices -> CD/DVD -> prl-tools-lin.iso.
3. Become root user.
> su
> <enter superuser password>
4. Mount the Tools virtual CD in your Linux VM.
# mount /dev/cdrom /mnt
5. Copy the full CD to a local directory, and rename it something like *tools_cd* then enter it.
# cp -R /mnt .
# mv mnt tools_cd
# cd tools_cd
6. Navigate to the source code tarball
# cd kmods
7. Untar the source code.
# tar xvpf prl_mod.tar.gz
Can optionally change ownership:
# chown -R <owner>:<group> ../kmods
8. Move the current tar.gz out of the source tree to protect it in case of an error.
# mv prl_mod.tar.gz ../../
9. Apply the patch to the source code or edit the appropriate files manually.
To apply the patch:
# patch -p1 <patch filename>
Optionally, you can edit the individual files manually (what I prefer to do) using the stated file paths and line numbers in the diff as a guide.
Lines to remove are prefaced with a '-'.
Lines to add are prefaced with a '+'.
10. Re-tar/gzip the source tree.
# tar cvpf prl_mod.tar .
# gzip prl_mod.tar
11. If you are not in the new kernel, reboot into it.
# reboot
12. Once in the new kernel, become root user.
> su
> <superuser password>
13. Change to the directory where you copied the Tools CD.
# cd tools_cd
14. Run the installer and follow all installer directions to perform an *Upgrade* to continue.
# ./install
15. The installer will take a while to complete.
16. If the install is successful it will ask you to reboot. If it failed, it's likely that something in Step 9 was done incorrectly. Simply restart from Step 9, ensuring the changes to each file were made correctly. Worst case scenario, copy the saved copy of prl_mod.tar.gz back into tools_cd/kmods and restart from Step 7.
Note: In the event you upgrade your kernel you may fully rebuild Parallels Tools by simply starting from Step 12. There is something about the scripts that do not fully rebuild/install Tools whenever a kernel is updated via dnf.
Restarting from Step 12 can be done repeatedly until which time that Parallels (and hence, Tools) is ever updated again from Parallels. It assumed that Parallels-provided version of Tools will continue to work for a while. However, eventually it will break, in that case you must restart the entire process and apply a whole new patch once those fixes are determined.
