Virtualbox on Asus PZ13 Win ARM doesn't start

[Juhis000]

So tried everything I could, and didn't get it even to Oracle screen. Changed paravirtualization Interface, tried 7.2.2 and even nightly (7.2.3_170726_)
Machine: Asus PZ13
Processor: Snapdragon X plus
Mem: 16GB
Windows 11 home 24H2
Tried multiple Ubuntu ARM distros without success.

Log attached and screenshot where it stops:

[ender1]

Try setting the graphic adapter to QemuRAMFB, then change it back to VBoxSvga or VMWareSVGA once install finishes.

[Juhis000]

Try setting the graphic adapter to QemuRAMFB, then change it back to VBoxSvga or VMWareSVGA once install finishes.

Doesn't work

[Melissa]

Hi I am the same.
HP laptop, WIndows 11, Snapdragon x, arm-based processor and I can't get it passed that first screen.

Just sits on the black screen. I'm having a feeling they says it's supported but don't think it's fully functional yet

I have tried to change so many settings and different arm isos with no luck.

Might look at returning the laptop to be honest

[OliverL]

The same is true for an ASUS Vivobook 14, Snapdragon X126100, Windows on Arm 11 25H2, newest patch level,
VirtualBox 7.2.6a.

If I start a VM the screen remains black - no disk or CPU activity. I configured 3 VMs for
debian-13.2.0-arm64-netinst.iso
ubuntu-25.10-live-server-arm64.iso
Windows 11 on Arm

Even without mounting any ISO I should see anything - at least more than a black client screen with all the icons in the bottom row (looking normal).

[klaus]

How did you configure the VMs? I've seen that the very first VM start can take very long until the VirtualBox logo is shown, indicating that he VM's UEFI firmware has started. The general rule applies: if you don't follow the troubleshooting advice (in the sticky posts, in the VirtualBox User Guide, ...) to provide VBox.log then we can't say much.

[OliverL]

I did not find the Sticky Notes in https://bing.com/search?q=virtualbox+user+guide and did not want to bother with my personal log because the problem seems generally occuring to me.
But I added a log now for my Ubuntu VM - generated with absolute default values using the GUI. I just gave 2 instead of 1 vCPU.

An I just started this VM again and waitet 15+ minutes - no change- only a black window.

Thank you for your support.

[OliverL]

VirtualBox 7.2.14 still does not start an e. g. empty created VM with default values - black screen remains, tested with VBoxSVGA (default) and QemuRamFB. Both logs attached. Any idea?

Could anybody start a VM on a any Windows on ARM host with Snapdragon X 1-26-100?

[klaus]

Your VM has a pretty odd config: 16MB VRAM and 3D enabled. Not that UEFI BIOS knows how to use 3D acceleration, but it clearly doesn't get off the ground entirely (never produces any graphics), which could have 2 causes: either it gets stuck before reaching the graphics setup, or something sabotages graphics setup.

You could try a few things: disable 3D and set VRAM to say 32 MB (not to the maximum, that's known to cause trouble with VirtualBox on ARM due to how the PCI resources are allocated). And finally you could rename the VM's .nvram file so that it isn't found. Corrupted NVRAM files have caused very early UEFI hangs before.

[OliverL]

Thank you very much for your answer.
"pretty odd config"? Well, this is the default config. I just create a new VM, select "windows 11 on ARM" and OK.
As you can see from the two screenshots - I even just created a new Test2 VM - VRAM is 128 MB, 3D is off or even disabled (when I test with QemuRamFB).
I changed to 32 MB and re-tested - same result, VM starts, screen remains black. VBoxSVGA or QemuRamFB with 32 MB.

Sorry for the German screenshots . I also added one further Vbox.log with one of these settings. I see the 32 MB VRAM in it.