1. Windows 10 host, VMWare Workstation 17.5, Fedora 40 guest - kernel upgrade from 6.8.7-300 to 6.8.8-300 broke the ability of the kernel to detect the VMWare display configuration (sees only one instead of two). 2. What is the Version-Release number of the kernel: 6.8.8-300 3. Did it work previously in Fedora? If so, what kernel version did the issue *first* appear? 6.8.7-300 4. Can you reproduce this issue? If so, please provide the steps to reproduce the issue below: Yes - boot and see VMWare 'Cycle Multiple Monitors' fail or run 'xrandr' and see only one display where there are 2 physical displays and the VM is configured to have 2. 5. Does this problem occur with the latest Rawhide kernel? To install the Rawhide kernel, run ``sudo dnf install fedora-repos-rawhide`` followed by ``sudo dnf update --enablerepo=rawhide kernel``: haven't tried it. 6. Are you running any modules that not shipped with directly Fedora's kernel?: no 7. Please attach the kernel logs. You can get the complete kernel log for a boot with ``journalctl --no-hostname -k > dmesg.txt``. If the issue occurred on a previous boot, use the journalctl ``-b`` flag. Reproducible: Always
Created attachment 2031139 [details] dmesg output from journalctl -b
sorry, the problem initially appeared in 6.8.8-300 and worked in 6.8.7-300.
6.8.9 flowed out last night. the problem still exists in 6.8.9
This message is a reminder that Fedora Linux 40 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora Linux 40 on 2025-05-13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a 'version' of '40'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, change the 'version' to a later Fedora Linux version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see it. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora Linux 40 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora Linux, you are encouraged to change the 'version' to a later version prior to this bug being closed.
Fedora Linux 40 entered end-of-life (EOL) status on 2025-05-13. Fedora Linux 40 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora Linux please feel free to reopen this bug against that version. Note that the version field may be hidden. Click the "Show advanced fields" button if you do not see the version field. If you are unable to reopen this bug, please file a new report against an active release. Thank you for reporting this bug and we are sorry it could not be fixed.