"rmmod" the modules, then run vmware-config.pl BillK
On Mon, 2003-10-06 at 23:16, a_k_b wrote: > hi there, > > i got the following problem: > once these days my vmware started, but the vm was hanging, so i had to kill the > vmware process. but now, after killing it, the vmmon module doesnt get free to > unload it. i think it hanged because the modules had to be recompiled for my new > kernel. so it seems like the wrong kernel version module is loaded (shouldnt be, but > seems like its like that). > now that i've killed vmware, i have to unload the modules manually (or > /etc/init.d/vmware stop/restart), but this doesnt work. the vmmon module still has > two references, so it cant be unloaded. but the lsmod command does only show the > number of running references, not their names or something. > > any idea how to solve this without a reboot? i already tried to kill all types of > lock-files related to vmware and so on, nothing worked. i cant recompile the modules > neither restart the init process, because both of them look at the references at the > loaded vmmon module... and then quit with a message like "still having a running > vmware instance". > > :-( > > Arne > > -- > [EMAIL PROTECTED] mailing list -- William Kenworthy <[EMAIL PROTECTED]> -- [EMAIL PROTECTED] mailing list
