On Tuesday 18 November 2003 07:53, Bruce Marshall wrote:
I just went through this hell this afternoon... and I do believe I now have it working... (but only a little time will tell)
ditto
1) I did a fresh install of 9.0. 2) I loaded vmware 4.0.5 from the rpm VMware provides. (what I had prev. been using on 8.2) 3) When it did the compile of the modules during vmware_config.pl, and asked if it could overwrite the modules, I went into the /lib/modules/ <kernel---->/misc/ directory and renamed both the vmmon.o and vmnet.o modules. Then I let the config overwrite those files.
4) VMware fired up but within a minute the entire VMW machine hung. Not just the guest but the VMWARE process. Killed it.
Mine died when I tried to re-size the screen. Killed it but vmware still believed the processes were there. It wouldn't let me re-start the machine, (not enough RAM) Nor would it let me re-start the vmware daemons, with/etc/init.d/vmware restart, (processes still running) So I had to reboot each time.
5) I then went and switched the modules from the compiled ones to the ones that came with 9.0. 6) VMWare fired up but again hung within a minute or so of running.
Yes, that's the short version, but yes.
At this point I was left with only boot parms being a possible answer. (and I had been trying to get VMW to run on two different machines, one scsi and Athlon based and the other Intel P4 and IDE based.)
I tried the following parms:
apic apm=off nosmp acpi=off
Of those, I think apic was already on the boot line and I added the last 3. Of the last three, I suspect the acpi=off is the important one.
Saying just "apic" on the boot line seemed to work for me. But as you say, only time will tell. michaelj PS: Does VMware still require an SMP machine be downgraded from the smp kernel to p_smp? -- Michael James michael.james@csiro.au System Administrator voice: 02 6246 5040 CSIRO Bioinformatics Facility fax: 02 6246 5166