This message is really aimed at the Parallels development team, but I could find no contact information to send an email directly. The instructions are useful to anyone setting up a Debian Wheezy virtual machine in Parallels Desktop (possibly other platforms as well). I have had quite a problem getting Debian Wheezy working with Parallels Tools. I recently figured out the cause of the problem and was hoping you could either patch Parallels Tools (specifically `/etc/init.d/prl-x11`) or at least distribute documentation regarding these steps to other customers. Debian Wheezy has switched to the insserv boot chainloader, and the format of the /etc/init.d files now requires additional comments for it to parse and maintain order. Without these comments it will fail to run all commands. This creates a problem for anyone installing new packages that have nothing to do with parallels. Additionally, the graphics acceleration is broken because the script does not get executed. Fortunately the fix for the prl-x11 script is quite easy. In your install pacakge the file located at ./installer/prl-x`11.sh, add these lines after your copyright: # Add LSB insserv Compatibility ### BEGIN INIT INFO # Provides: prl-x11 # Required-Start: $remote_fs # Required-Stop: $remote_fs # Default-Start: 2 3 4 5 # Default-Stop: 0 1 6 # Short-Description: x11 guest driver extension # Description: prl-x11 is a parallels service that configures X11 # for guest virtual machines. ### END INIT INFO The other factor is the Accelerated graphics. Even with the above patch applied prior to installing or upgrading off the local machine, the script is never started, and therefore the accelerated graphics are never loaded in. I have not looked into specifically where in the installer the script is called and why it fails (or if it is in fact called). For now post reboot I am manually running `sudo service prl-x11 start`, which seems to do the trick for future logins. I hope this information helps and that it will soon be patched.