| 1 |
do you have module unloading compiled into your kernel? |
| 2 |
if not this is needed because of how the /etc/vmware/init.d/vmware script works |
| 3 |
|
| 4 |
also a debug check list |
| 5 |
first check for your vm modules |
| 6 |
lsmod |
| 7 |
|
| 8 |
this should show you your vmmon / vmnet modules |
| 9 |
|
| 10 |
also check your /dev folder for your vm files |
| 11 |
ls -l /dev/vm* |
| 12 |
|
| 13 |
this should show you vmmon / vmnet / vmnet0 and so on |
| 14 |
|
| 15 |
lastly if you find that you have module unloading support and all the above check out fine do |
| 16 |
|
| 17 |
rc-update add vmware default |
| 18 |
|
| 19 |
then just reboot |
| 20 |
|
| 21 |
****a very windows approach to this i know but im lzy and it will do 2 things... 1) shows you that your install is goin good (if u reboot and vmware does'nt work then it aint a good install) 2) deals with any modules that may be loaded in as perment, im sure there may be a better way but ... im lzy =)**** |
| 22 |
|
| 23 |
as you reboot you should see the vm services load with the typical [ok] |
| 24 |
|
| 25 |
login then run your vmware as you would normally. |
| 26 |
-- |
| 27 |
View this message in context: http://www.nabble.com/vmware-workstation-daemon-problem-t720417.html#a2386900 |
| 28 |
Sent from the gentoo-user forum at Nabble.com. |
Archives