Difference between revisions of "How to Get VMware Player to Work on the New 3.1.x Linux Kernel!"
Jump to navigation
Jump to search
(Created page with "Make sure the kernel headers and kernel source for the currently running 3.1.x version of the Linux kernel are installed. <br> To check your currently running Linux kernel with t...") |
|||
| Line 4: | Line 4: | ||
<br> | <br> | ||
<br> | <br> | ||
| + | <pre style="color:blue"> | ||
[root@fusion16 etc]# uname -r | [root@fusion16 etc]# uname -r | ||
| − | |||
3.1.9-1.fc16.x86_64 | 3.1.9-1.fc16.x86_64 | ||
| + | </pre> | ||
<br> | <br> | ||
<br> | <br> | ||
Revision as of 05:54, 19 January 2012
Make sure the kernel headers and kernel source for the currently running 3.1.x version of the Linux kernel are installed.
To check your currently running Linux kernel with the "uname -r" command(using my machine below as an example):
[root@fusion16 etc]# uname -r 3.1.9-1.fc16.x86_64
Install the latest vmware-player-x.x.x.bundle as root.
Check to see if "/etc/vmware/not_configured" exists. If it exists, VMware Player will refuse to run with an
error is hasn't been configured correctly for the currently running kernel, and refuse to run with a protection error.
If it does, delete it, and then run "vmplayer" as the root user from the console to configure, build, and set it up.