Chakra 2011.04-r2
With the latest releases of Parallels Build 6.0.12094 and Chakra 2011.04-r2 I took the time to figure out how to get the latest Parallels Tools to install.
I started with a new fresh VM, created from the x86_64 .iso. This version of Chakra actually has lib64 directories, but many files, including the X11 ones, are still located in the lib structure. This required a tweak to the detect-xserver.sh install script (see below).
Additionally, as Chakra 2011.04-r2 is based on Linux 2.6.39, code has to be physically patched to resolve API changes in the core API. This affected 3 source files.
1) pacman -S gcc make
2) ln -s /etc/rc.d /etc/init.d
3) mkdir /etc/init (directory required for the prl-x11 configuration)
4) mount the Parallels Tools
5) copy the Parallels Tools to a working directory
6) unzip and untar the prl_mod.tar.gz in kmods directory
7) Patch files as shown in attached diff file
7b) Manually edit installer/install-tools.sh:
- Comment out "$REGISTER_SERVICE" --install "$TOOLSD"
- Comment out "$REGISTER_SERVICE" --install "$XTOOLS"
8) Run the installer in your working directory
9) We commented out registration, so manually edit /etc/rc.conf file:
- Add 'prl_tg prl_pv prl_fs prl_fs_freeze prl_eth' to the end of the MODULES list
- Add 'prl-x11 prltoolsd' to the end of the DAEMONS list
10) Reboot
In the attached diff report 'parallels_tools' is my working directory and 'parallels_tools_orig' is a copy of the original install files.
I believe I've documented all the important steps, but it has been a few days since I did this so I apologize if I left out any steps. Hopefully this should provide enough information for anyone interested in trying out the latest Chakra inside a Parallels 6 VM.
I've also attached an image showing my Chakra VM accessing the Parallels Shared Folders, showing my Home (which is on MacOS Lion).
Edit: I've applied the patch correction noted below to the attachment.
Edit: I've tweaked the instructions to make sure that the full install succeeds. The failure were happening because the script tried to automatically register services and components. These failures prevented the script from completing properly.
-
- File size:
- 499 KB
- Views:
- 189
-
- File size:
- 3.2 KB
- Views:
- 749
Last edited: Aug 23, 2011