Bug 2351559
| Summary: | Grub cannot boot Windows on a dual boot installation. | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Lukas Ruzicka <lruzicka> | ||||
| Component: | grub2 | Assignee: | Nicolas Frayer <nfrayer> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 42 | CC: | awilliam, kparal, lbrabec, lkundrak, lsandova, mlewando, nfrayer, pjanda, pjones, robatino | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | AcceptedBlocker | ||||||
| Fixed In Version: | Doc Type: | --- | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2025-03-27 20:46:23 UTC | Type: | --- | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 2291265 | ||||||
| Attachments: |
|
||||||
|
Description
Lukas Ruzicka
2025-03-12 11:08:18 UTC
Proposed as a Blocker for 42-final by Fedora user lruzicka using the blocker tracking app because: This violates the Windows Dual Boot criterion. https://fedoraproject.org/wiki/Fedora_42_Final_Release_Criteria#Windows_dual_boot Fix is on the way: https://bodhi.fedoraproject.org/updates/FEDORA-2025-22620dca9b The fix is now stable. Lukas, can you please verify whether it fixes your setup? I will give it a try. Will update when I am ready. Discussed during the 2025-03-17 blocker review meeting [1]: * AGREED: 2351559 - AcceptedBlocker (Final) - this is accepted as a violation of "The installer must be able to install into free space alongside an existing clean Windows installation. As long as the Windows installation does not have BitLocker enabled, the installer must also install a bootloader which can boot into both Windows and Fedora" [1] https://meetbot-raw.fedoraproject.org/blocker-review_matrix_fedoraproject-org/2025-03-17/f42-blocker-review.2025-03-17-16.00.log.html With the fix, I am still experiencing the issue on my EFI based VM. Unfortunately, I am not able to obtain any Linux logs because the system is not running per se. After I select to boot the Windows, I end up with a black screen with a white cursor. That situations stays for a long time. If I try and boot Fedora, it's ok. If I boot Windows from the EFI menu, it works, too. I just cannot boot from Fedora Grub. I have taken a screenshot of the grub entry that loads Windows in case you want to check that. I will try to run this on bare metal again and see how that goes. Created attachment 2080630 [details]
Screenshot of Grub entry
On bare metal, I am not experiencing any problems. Everything works as expected. It is just the VM that is affected. Hi Lukas, Just to leave an update here after our conversation: On a UEFI VM, I've installed Win10, resized the ntfs partition with the fedora installer and installed fedora with this ISO [0]. Windows and Fedora boot fine for me. I've verifier the grub version installed/used and it's the latest (grub2-2.12-26.fc42). I am not sure what could be the issue. Can you please enable some debug when you reach the grub menu by pressing 'e' on the entry you want to boot, then add "set debug=all" and finally press Ctrl+X to execute the entry ? Maybe we can spot something. Thanks, Nicolas [0] https://kojipkgs.fedoraproject.org/compose/branched/latest-Fedora-42/compose/Workstation/x86_64/iso/Fedora-Workstation-Live-42-20250317.n.0.x86_64.iso Sure. Where do I add it? Can I add it on an extra line below the set root? Or behind the set root command on the same line? You can add it at the top it's fine. We mostly care about bare metal here, so I'll set this as VERIFIED. Lukas, do you have time to add the VM debug output? To add my "discoveries"
I can reproduce failure with F42 used as a hypervizor. I cannot reproduce it on F40
I suspect some OVMF change causing chainloading in grub to fail.
what I tried
- install F40 with edk-ovmf-20241117-5.fc40.noarch
- use virt-manager to create a UEFI VM with 70GB HDD, firmware OVMF_CODE_4M.secboot.qcow2
- install W10Education edition VM
- reboot VM - Win boots
- shutdown VM
- start VM in a way it boots from F42 DVD
- install Fedora in VM, shrinking W10 partition to 50GB
- reboot
system starts into grub, when Windows is chosen it displays a white cursor in
left top corner, but also a spinner in middle bottom and boots correctly
- then I replaced content of /usr/share/edk2/ovmf by content from edk2-ovmf-20250221-8.fc42.noarch
- fedora in VM starts without any issues
- Windows is possible to start via bootmanager from firmware
- Windows start fails when chosen in the grub - white cursor in top left corner, black screen, nothing else.
It is similar in F42 hypervizor.
- with edk2-ovmf-20250221-8.fc42.noarch chainloading windows fails
- with edk-ovmf-20241117-5.fc40.noarch chainloading windows is successful
I'll create a bug to OVMF.
bug 2354064 is created to follow on EDK (OVMF) side as it does not look as a bug caused by a grub2 change since the update that fixed this is stable, it should be closed, not VERIFIED. closing. if I misunderstood and there is still an outstanding blocker issue here, please re-open. |