How to Fix Proxmox stuck on "BdsDxe: starting Boot0001" During macOS Boot or Installation

How to Fix Proxmox stuck on "BdsDxe: starting Boot0001" During macOS Boot or Installation

Boot failures need a predictable pass through firmware, USB, storage, EFI and verbose logs before reinstalling macOS. Most installer stalls come from firmware settings, an invalid config.plist, wrong SSDTs, bad USB mapping or unsupported storage/controller settings.

Quick Checks

• Backup current state: Save a copy of your working EFI and run a full system backup before changing settings.
• Identify hardware components: Note down your exact CPU, GPU, Wi-Fi card, and motherboard/laptop model.
• Ensure utility alignment: Keep OpenCore, OCLP, and ProperTree updated.

Fix Steps

1. Create a rollback point: Make a Time Machine backup and keep a copy of your last working EFI folder before editing OpenCore, kexts or root patches.
2. Boot verbose: Add -v keepsyms=1 debug=0x100 so the final visible line gives a real clue.
3. Check firmware settings: Disable Secure Boot and Fast Boot, set SATA to AHCI, disable CFG Lock if possible, and use UEFI mode.
4. Validate OpenCore: Update OpenCore, Lilu and core kexts, then run ocvalidate or ProperTree clean snapshot.
5. Recreate the installer: Use a fresh USB installer and try another USB port; older Macs may need a USB 2.0 hub for input during setup.
6. Reset NVRAM: Reset NVRAM from the OpenCore picker before retrying the installer.

Do Not Continue If

• Do not continue if: you do not have a working EFI backup, a Time Machine backup, or another bootable macOS installer.
• Stop and capture evidence: if the machine stops booting, take a photo of the last verbose line before changing more settings.

Verify It Worked

• Verbose boot moves past the previous stopping line.
• The installer reaches Disk Utility and sees the target disk.
• Keyboard, mouse and USB remain active during recovery.
• OpenCore picker still loads after a cold boot.

Rollback

• Restore the last booting EFI folder.
• Use the officially supported macOS installer to recover the machine.
• Do not erase the internal disk until the installer can boot twice consistently.

Next Action

• Test now: reboot twice, reproduce the original problem, and confirm whether the same symptom returns.
• If it still fails: record the Mac model, macOS build, OpenCore or OCLP version, GPU, Wi-Fi/Bluetooth chipset, and the last visible error.
• Read next: use the related searches below for the nearest OpenCore or OCLP fix before making another change.

Related iATKOS Searches

• OpenCore · OCLP · EFI · kexts · config.plist · macOS troubleshooting

Original Question: "Proxmox stuck on "BdsDxe: starting Boot0001""

Hi, I've installed Proxmox on my IBM X3690 x5 (old thing, I know). The CPUs are Intel(R) Xeon(R) CPU E7- 2830, which is based on the Westmere architecture. I am running the osx-proxmox install script, which does not report any errors, however it gets stuck on this during boot: BdsDxe: starting Boot0001 "UEFI QEMU HARDDISK QM00001 " from PciRoot(0x0)/Pci(0x1F,0x2)/Sata(0x0,0xFFFF,0x0) https://preview.redd.it/hlurtjixmsxc1.png?width=2245&format=png&auto=webp&s=f7d136a9b6a544f023fbe1677280c48b45a26f24 The version of macos does not matter, they all give the same error I'm new to proxmox, so please let me know if there's anything more that could help. I appreciate any help. submitted by /u/Araliena [link] [comments]