The installer doesn't set up the /etc/init.d stuff, so the drivers don't get loaded. Running the parallels-config script doesn't fix that, but it has the side-effect of loading the drivers right at the end!
A workaround is to edit the launch command script /usr/bin/parallels so that the second line reads:
/usr/lib/parallels/autostart/drivers_start
While you're there, you may as well add an extra line at the bottom:
/usr/lib/parallels/autostart/drivers_stop
If I recall correctly, those 2 scripts use illegal syntax for /bin/sh. So to get them to actually work, you need to edit drivers_start and drivers_stop, and change line 1 in each case from #!/bin/sh to #!/bin/bash (and install bash on your box if it ain't there already).
I think I had to change the parallels-config script to use /bin/bash before that would run without errors.
All things considered, it's amazing that such a highly technical product works so well once it's up and running, but has silly little errors in some trivial scripts! I can only speculate that the parallels guys tested on a Linux distro that has subtly different behaviour from Ubuntu, so presumably the installation and start-up scripts worked with no problems, whereas they run into little snags on ubuntu/kubuntu edgy and feisty.
Did you get the sound working in Feisty BTW?
Cheers
Bookmarks