This is really a bug in the messages produced by vmware products. vmware-modules, when being emerged, issues messages vmware-player when failing to start issues similar messages They suggest 1) re-emerging vmware modules 2) re-running the configuration utility. This is not enough when one has just switched kernels, even in the slightest. One also has to ensure the symlink "/usr/src/linux" is correctly pointing to the kernel that _will be_ used. It seems to be that the emergence of vmware-modudules has to be done with the symlink set right, and running under that kernel. The messages don't mention any of this. It's an easy thing to do and I suggest the wording: "If you have switched kernels, or are about to do so, you must adjust the symlink '/usr/src/linux' and re-emerge vmware-modules once you are running the new kernel. You can use the command emerge --oneshot vmware-modules You may also need to re-run /opt/vmware/player/bin/vmware-config.pl" Depending on how these messages are generated, you may have to fiddle with the wording, of course.
This is the case with *any* external kernel module; really fail to see why should this deserve a special warning.
