[Bug]: VirtualBox 7.2.22 fails before guest boot on Windows 11 ARM64 with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619)

Abierto
#951 1 comentario 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
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
12/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
c

Línea de trabajo

Start with the attached post-restart-VBox.log and search it for VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619) to find the host driver initialization step that fails. Compare it with issue #870, which reports the same error code. Done means the cause on Windows 11 ARM64 is identified and the reproduction is narrowed to a specific condition, such as Secure Boot or Memory Integrity.

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

Descripción

bug
Version

7.2.22 r175245 (native Windows ARM64)

Host OS Type

Windows

Host OS name + version

Windows 11 ARM64, build 26300.9818

Host Architecture

ARM

Guest OS Type

Linux

Guest Architecture

ARM

Guest OS name + version

Ubuntu 26.04.1 Desktop ARM64 (live ISO

Component

Unspecified

What happened?

VirtualBox 7.2.22 r175245 fails on a Windows 11 ARM64 host (build 26300.9818) with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619) during host driver initialization. I expected the Ubuntu live desktop to open. Instead, the VM stopped before Ubuntu started, and the failure persisted after a Windows restart. VBoxSup was running, and Secure Boot and Memory Integrity were enabled.

The error code also appears in issue #870. This report reproduces it on native Windows ARM64 with VirtualBox 7.2.22.

post-restart-VBox.log

How can we reproduce this?
  1. On Windows 11 ARM64 build 26300.9818, install native VirtualBox 7.2.22 r175245.
  2. Create an ARM64 Linux VM, attach the Ubuntu 26.04.1 Desktop ARM64 ISO, and disable all VM network adapters.
  3. Start the VM using the VirtualBox GUI. It fails before Ubuntu starts with VERR_SUP_VP_FOUND_EXEC_MEMORY (-5619).
  4. Restart Windows and retry. The same error occurs. The attached log is from this retry.

post-restart-VBox.log
Image

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
Métricas de merge de PR
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.