On Mon, Jul 31, 2017 at 05:59:24PM +0200, Walter H. wrote: > > No, this wasn't really a Fedora issue, it's a VMWare issue. > doesn't really help me, the upgrade killed my VMware Workstation It still doesn't stop it from being a VMWare issue. VMware has kernel modules that need to be compiled against the running kernel. If you ran VMWare on an enterprise distro, you might be able to use the previous kernel's modules through the weak-modules feature, but upgrading from one Fedora release to the next is likely to introduce a large kernel jump, and Fedora makes no attempts to be ABI-compatible between releases. This is extremely common for 3rd-party kernel modules. I know first-hand, since I maintain OpenAFS kernel module packages for Fedora and quite often they break mid-release of fedora because they track the new kernels. It happens. And if you really wanted to provide feedback about kernel updates, Fedora has a feedback mechanism here: https://bodhi.fedoraproject.org/updates/?packages=kernel -- Jonathan Billings <billings at negate.org>