Mirror/server RFE: Do not remove old kernel from updates. (vmware)

[Gilboa Davara]

On Mon, 2007-04-09 at 15:59 +0300, Gilboa Davara wrote:
> Hello all,
> 
> During the last couple of weeks 2.6.19 and 2.6.20 were pushed to
> fc6-updates. 
> With the push, all older kernel updates (2.6.18-xxx) were removed from
> the main, and mirror servers.
> Due to lack of sleep I removed the old 2.6.18 kernel I had on my
> development machine (rpm -e $(rpm -qa | grep 2.6.18) should not be done
> @5am... ;)) - just to find out that vmware-server dies a horrible death
> (taking the host with it) when combined with kernels >= 2.6.19.
> Now, I'm left with a problem, I cleared the yum cache and there are no
> 2.6.18 RPMs available  from any official source (beyond the initial
> -core RPMs), and using 2.6.19/20 will most likely send me to the loony
> bin. (Eating my software raid5 with it)

Just to reduce the number of vmware-related comments - the problem is
not config.h, vmmon/compat-kernel.h or vmnet/checksum or anything
vmware-config.pl...
The vmware's vmmon kernel module seems to crash and burn when combined
with new(er) kernels. Read: The vmmon kernel modules dies, taking the
host system with it.
Applying vmware-any-to-any patch may get the vmmon/vmnet compiled again
(I rather do it by hand - but that's me), but it stop it from crash the
host system's kernel.

- Gilboa