Hi, I'm also running VMWare Workstation, and am experiencing the exact same issue. On Fedora 40, using the kernels 6.10.4, 6.10.5, and 6.10.6 result in an unbootable vm, and the last Fedora 40 kernel that worked was 6.10.3. Just to do some verification, I tried running an Arch Linux guest with kernel 6.10.6 using the same VMWare Workstation install, and that boots perfectly fine. So whatever this turns out to be, it's not just a simple 'VMWare needs to be updated for the latest kernel' issue: latest Arch seems to be doing something different here than Fedora 40, resulting in the fact that the same kernel will boot in Arch and not in Fedora (and this needs to be investigated). Either that or, I have made different configuration choices when creating these VM's (I cannot recall what choices I made during VM configuration for Arch). PS: For now, as a temporary workaround, you 'could' choose to add the following line to /etc/dnf/dnf.conf : exclude=kernel kernel-core kernel-devel kernel-modules kernel-modules-core kernel-modules-extra which will prevent dnf from updating the kernel when you do a 'sudo dnf update'. -- _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx Do not reply to spam, report it: https://pagure.io/fedora-infrastructure/new_issue
