Hi again, VMWare says this on crashing hosts: Q: vmware-config.pl completed successfully, but each time I power on VMware, my Linux host crashes. A: We see this problem most commonly when a Linux vendor ships a Linux kernel distribution whose properties are kernel version x and normal symbols, then you install a heavily patched kernel (for example, a Mosix kernel) with the same version number and normal symbols. VMware ships pre-built modules with the same properties as the kernel distribution. For example, version x and normal symbols. After you install a heavily patched kernel, vmware-config.pl must be run again. Because neither kernel has the mangled symbols property, VMware prebuilt modules are viewed as compatible and loaded. In fact, the modules are incompatible and hence crash your machine at run time. The long-term solution to this problem is to ask that your distribution vendor always use the mangled symbols property when building a kernel. Mangled symbols reflect incompatible interface changes between kernels, and the VMware prebuilt modules for a particular Linux release would not be viewed as compatible with a heavily patched kernel release. The short-term solution is to run vmware-config.pl --compile, which will ignore VMware prebuilt modules and will force a build of modules for your heavily patched kernel. --- Ron Heron wrote:

Hello,

I, too have had huge problems with VMware hardlocking the system. My previous version 6.3, I had upgraded each time vmware had an upgrade, and it seems that the last version prior to 2.0 didn't crash my system. When I upgraded to 2.0 adn 2.01, I started having crashes again. I opened a ticket with VMware, and they told me to send my dmesg output. Well, on 90% of the crashes, it didn't write anything to the message log. Once, it wrote a "kernel dereferrence to a null pointer" message. But, VMware had already closed my case by then.

Now, I am on 6.4, and thought I would give VMware another try. I was halfway through loading Win2k, when I hard locked again. It may have something to do with networking, because there was a huge data transfer going on via Samba on the same nic.

I was actually a paid up customer on the old versions, but have since to take the plunge again, after the lockups. This last crash really killed my hd, and took almost 4 hours to recover! So, it's a shame, but I can't risk losing my hd for vmware. If anyone get's a solid answer or fix, I would love to hear it so I can use VMware again.

BTW - e2fsck -f -b 8193 /dev/hdxx doesn't work! For some reason, I had to go e2fsck -f -b 0 /dev/hdxx (Roman, try this)

Ron

--- David Herbison wrote:

...

On Mon, 7 Aug 2000, Derek Fountain wrote:

...

Are you using the network modules? Try it without if you are. Have you tried removing your preferences file (from $HOME/.vmware? Have you removed vmware and rerun the installation script? Does it crash if you run it as root?

I never run with the network modules. Tonight I'll try as root, and see what happens. What I don't understand is that it worked perfectly (albeit slowly) with the old hard drive, before I updated xshared. I haven't changed anything.

...

Er, that about all I can think of at the moment!

thanks for the tips.

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

__________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/

-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq

__________________________________________________ Do You Yahoo!? Kick off your party with Yahoo! Invites. http://invites.yahoo.com/ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/support/faq