[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSo
[Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
Wed, 05 Dec 2018 11:32:50 -0000
Could it be related to:
Author: Eric Auger <address@hidden>
Date: Fri Jun 22 13:28:37 2018 +0100
hw/arm/virt: Use 256MB ECAM region by default
With this patch, virt-3.0 machine uses a new 256MB ECAM region
by default instead of the legacy 16MB one, if highmem is set
(LPAE supported by the guest) and (!firmware_loaded || aarch64).
Indeed aarch32 mode FW may not support this high ECAM region.
As far as I can tell the only real differences between virt-2.12 and
later at the size of the ECAM region and the max number of CPUs it
static void virt_machine_2_12_options(MachineClass *mc)
VirtMachineClass *vmc = VIRT_MACHINE_CLASS(OBJECT_CLASS(mc));
vmc->no_highmem_ecam = true;
mc->max_cpus = 255;
** Tags added: aarch64 acpi
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
Status in QEMU:
When I emulate a virt-3.0 machine, Windows 10 BSoD on boot, with the
error code being ACPI_BIOS_ERROR(0x000000A5), virt-2.12 boots fine.
Windows Build: 10.0.17134.1
QEMU version: 3.0.0
Commandline: qemu-system-aarch64 -M virt -accel tcg,thread=multi -cpu
cortex-a57 -smp 2 -m 2048 -bios QEMU_EFI.fd -device ramfb -device nec-usb-xhci
-device usb-kbd -device usb-tablet -hda disk.vhd -vnc :0
By the way, the patch to add DBG2 table discussed here
works (although minor change is required to adapt to the qemu 3.0.0
code), the table is accepted by Windows (Windows require both DBG2 and
SPCR to be valid for serial kernel debugging to work), so it may help
further diagnosing this issue.
To manage notifications about this bug go to: