imo 9.0 is still not ready for prime time regarding vmware. or the other way around. i guess i will stay with 8.2 /vm 4.05 a bit longer. d. On Tuesday 06 January 2004 05:38, Kenneth Schneider wrote:
On Tue, 2004-01-06 at 09:45, Gary Gapinski wrote:
On Monday 05 January 2004 19:46, Ken Schneider wrote:
And speaking of a VMware install..
Why were the VMware modules left -out- of the .166 kernel update?!
The km_vmware piece of shit doesn't work and neither does the module complilation from VMware themselves. Going back to the .144 kernel till 2.6 becomes stable.
What problems are you encountering?
I've been running VMware-gsx-2.5.1-5336 on 2.4.21-166-smp4G (for a whopping 30 minutes or so) with no problems.
I did find that the vmware-config.pl compiled _and_ installed vmmon and vmnet modules, so I'm not using any pre-supplied ones. The -99 and -144 kernel versions included these modules, and I thought I had used the SuSE-supplied ones by telling the vmware-config.pl script to not install its own, but I was not presented with that option with the -166 kernel installed.
The -166 kernel did not come with pre-compiled modules hence you would not get a prompt to overwrite files that do not exist.
I have only performed the update at home and when I use vmware-config to create the modules I get a kernel oops when starting vmware (4.0.5 workstation on 9.0 pro). If I try to use the km_vmware addon to create the modules vmware will not start as it cannot load all of the modules.
-- Ken Schneider unix user since 1989 linux user since 1994 SuSE user since 1998 (5.2)