Re: VMWare not working anymore

Did you rebuild the Vmware kernel module(s) from scratch?  Make sure you
do so each time you update to a newer kernel version, as it's important
the data structures referenced by the module be the same version as the
ones referenced by the kernel you're running.  I've seen precisely this
output when my kernel module has been out of sync, previously.  If it's in
sync, well, I guess it's a different problem :-)

Robert N M Watson             FreeBSD Core Team, TrustedBSD Projects
robert_at_fledge.watson.org      Network Associates Laboratories

On Mon, 30 Jun 2003, Eirik Oeverby wrote:

> Hi,
> 
> As of yesterday (I think), VMWare 3.2.1 is no longer working on my
> 5-CURRENT box. When I try to start it, I get
> 
> =============================
> [ltning_at_ranger] ~$ vmware
> Setting TMPDIR=/var/tmp.
> 
> 
> VMware Workstation Err
> 
> VMware Workstation Error:
> Version mismatch with vmmon module: expecting 30.0, got 0.0.
> You have an incorrect version of the `vmmon' kernel module.
> Try reinstalling VMware Workstation.
> 
> Press "Enter" to continue...
> 
> 
> 
> ^C
> =============================
> 
> A ps shows some parts are still running:
> 
> [ltning_at_ranger] ~$ ps ax | grep vmw
>   652  p1  W      0:00.10 vmware-ui -A 7 -B 4 -S -L
> /var/tmp/vmware-ltning-651.
>   653  p1  W      0:00.08 vmware-mks -A 8 -B
> 5 -S -L /var/tmp/vmware-ltning-651  663  p1  S+     0:00.01 grep vmw
> =============================
> 
> And kldstat shows the vmmon module(s) are indeed loaded:
> 
> [ltning_at_ranger] ~$ kldstat
> Id Refs Address    Size     Name
>  1   16 0xc0100000 3f5758   kernel
>  2    1 0xc04f6000 4930c    acpi.ko
>  3    1 0xc406c000 5000     linprocfs.ko
>  4    3 0xc42a2000 18000    linux.ko
>  5    1 0xc41f5000 8000     vmmon_up.ko
>  6    1 0xc41f1000 2000     vmnet.ko
>  7    4 0xc437a000 11000    netgraph.ko
>  8    2 0xc42be000 4000     ng_ether.ko
>  9    1 0xc4361000 5000     ng_bridge.ko
> 10    1 0xc42ba000 4000     ng_socket.ko
> =============================
> 
> Anyone else seeing this? Anyone have an idea how to solve it? This is
> pretty bad, as I've just managed to get rid of my last Windows
> workstation, which I only used to run a development SQLServer. Guess
> where that DBMS (should be/is) running now.. :-/
> 
> 
> /Eirik
>