Carlos E. R. wrote:
At first this meant that I had to take a bit more care during kernel updates, no really big deal. Then kernel updates made impossible my usage of VMware Server 1 -- after that I stopped applying kernel updates at all...
You have to re-run the vmware setup program after a kernel update. This recompiles some modules, asks some silly questions, and then the server works as always.
It would be great if the problem would be as trivial as that. VMware Server 1.x kernel modules do not compile with kernel 2.6.27+ out of the box; one has to use some patches. (These are not the ubiquitous vmware-any-any patches which dropped support for Server 1.x.) Up to and including 2.6.27.7-9-pae this worked more or less decent; with the only problem that VMware time synchronization doesn't work in Windows clients and needs to be done extra. (Probably a problem with clocksources and/or hpet timer, it has not been important enough for a full investigation.) Starting with kernel package 2.6.27.19-9.1, VMware instances with Windows clients grab 100% of the host's CPU time when started. This is what was meant when I wrote "made my usage of VMware Server 1 impossible". The patched VMware kernel modules still compile, but between 2.6.27.7 and 2.6.27.19 several kernel config options have been changed by SUSE that are related to virtualization and idle handling, maybe it's one of those. OTOH, I also don't know if the problem would disappear if I switch to VMware Workstation 6.x. (VMware Server 2 is not relevant owing to its Web browser-based console interface and very heavy resource usage.) That's not easy to test either as one cannot install both Server 1.x and Workstation 6.x on the same system. It's a drag, and not even related to getting real work done... Joachim -- =-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=- Joachim Schrod Email: jschrod@acm.org Roedermark, Germany -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org