[Bug]: VirtualBox 7.2.22 Windows host: 2-vCPU UEFI boot stalls before DVD prompt (NEM / CpuMpPei)

Abierto
  • ¿Algo no está bien?
#949 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 6 días

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Área
operating-systems

Línea de trabajo

Start by reviewing the attached reproduction and redacted firmware/NEM excerpts, especially the baseline and x2APIC logs around DXE_AP and CpuMpPei.efi. Then investigate the EFI boot path for the two-vCPU configurations and compare it with the one-vCPU diagnostic control. Done means explaining the stall and identifying a supported remedy that reaches the DVD prompt with two vCPUs, or documenting why none is available.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

bug
Version

7.2.22

Host OS Type

Windows

Host OS name + version

Windows 11 Home 64-bit, build 26200.9818

Host Architecture

x86

Guest OS Type

Windows

Guest Architecture

x86

Guest OS name + version

Windows 11 Enterprise Evaluation 26H2 x64 installation media; Windows Setup has not been reached

Component

EFI

What happened?

Hello VirtualBox maintainers,

We are reporting a reproducible firmware-stage issue with VirtualBox 7.2.22r175245 on a Windows 11 64-bit host (build 26200.9818).

Observed behavior:

  • With 1 vCPU, firmware reaches cdboot.efi and displays the DVD boot prompt. This is only a diagnostic control, not a proposed Windows 11 configuration.
  • With the baseline 2-vCPU configuration, the framebuffer remains 0x0 and firmware stops after DXE_AP.
  • With 2 vCPUs and both CPU and firmware x2APIC enabled, the VM starts but framebuffer remains 0x0. The relevant firmware log ends after CpuMpPei.efi at 00:00:07.714980; no cdboot.efi or DVD prompt appears.

The host reports hardware virtualization and nested paging support. NEM reports 'Snail execution mode is active'. Could you advise whether this is a known issue or whether there is a supported configuration or release-level remedy that preserves Windows 11 requirements and host protections?

The attached diagnostic archive contains four intentionally redacted text files: the report, reproduction and firmware/NEM excerpts. It contains no VM disk, ISO, full VBox.log, VM identifier, MAC address, host name, user name, network address or credentials. Full logs are intentionally withheld for privacy; please let us know if a specific additional redacted excerpt is needed. This is not a crash report.

Archive SHA-256: 17ED20936998BCE3F6496BCF6F8F9A7CEBD12CC372DCE1E100629F48A5CDBCD3 (4,182 bytes).

AI-Centrum-VirtualBox-REPRO-PUBLIC-PROPOSAL-20261031.zip

How can we reproduce this?

Host: 4 physical cores / 8 logical processors, 16 GB RAM; hardware virtualization, long mode and nested paging supported. Extension Pack is not installed.

  1. Start with a powered-off test VM: 4 GB RAM, 2 vCPUs, EFI, Secure Boot, TPM 2.0, SATA DVD with official Windows 11 Enterprise Evaluation x64 ISO. Disconnect NIC1 (none). No shared folders, clipboard, USB or VRDE; do not send guest keyboard input.
  2. Baseline branch: APIC on, CPU x2APIC off, firmware APIC apic. Start the VM and observe firmware only. Framebuffer remains 0x0; log reaches DXE_AP after CpuDxe.efi / PciHostBridgeDxe.efi.
  3. x2APIC branch: 2 vCPUs, APIC on, CPU x2APIC on, firmware APIC x2apic, NIC still disconnected. Start headless. Framebuffer remains 0x0; log ends at CpuMpPei.efi (00:00:07.714980). No cdboot.efi or DVD prompt.
  4. Diagnostic control only: with 1 vCPU the same media reaches cdboot.efi and the DVD prompt (1024x768). No boot key was sent and no license or Windows Setup accepted.

Expected: a framebuffer and the DVD boot prompt with the required 2 vCPUs.
Actual: no framebuffer / prompt in either 2-vCPU branch.

After each test the VM is powered off and restored to the baseline. Host Hyper-V/VBS, Defender, Secure Boot and TPM protections have not been disabled. Redacted firmware timestamps are in the attached archive.

Did you upload all of your necessary log files, screenshots, etc.?
  • Yes, I've uploaded all pertinent files to this issue.
Lenguaje dominante
C
Estrellas
1.4k
Forks
219
Sin PR fusionados en 30 d

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de VirtualBox/virtualbox

Todos los issues de VirtualBox/virtualbox

Issues similares

Más issues de C

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.