* [Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:29 [Qemu-devel] [Bug 1804961] [NEW] qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0 GH Cao
@ 2018-11-24 20:36 ` GH Cao
2018-11-26 12:14 ` Igor Mammedov
2018-11-28 19:25 ` GH Cao
` (5 subsequent siblings)
6 siblings, 1 reply; 10+ messages in thread
From: GH Cao @ 2018-11-24 20:36 UTC (permalink / raw)
To: qemu-devel
** Description changed:
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
- https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg02550.html
+ https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
New
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:36 ` [Qemu-devel] [Bug 1804961] " GH Cao
@ 2018-11-26 12:14 ` Igor Mammedov
0 siblings, 0 replies; 10+ messages in thread
From: Igor Mammedov @ 2018-11-26 12:14 UTC (permalink / raw)
To: GH Cao; +Cc: qemu-devel
On Sat, 24 Nov 2018 20:36:54 -0000
GH Cao <1804961@bugs.launchpad.net> wrote:
> ** Description changed:
>
> 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
> - https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg02550.html
> + https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
> 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.
>
if you are able to attach a debugger early before guest BSODs,
you can try to use AMIL Debugger
https://docs.microsoft.com/en-us/windows-hardware/drivers/debugger/the-amli-debugger
to find out what windows doesn't like in ACPI tables.
^ permalink raw reply [flat|nested] 10+ messages in thread
* [Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:29 [Qemu-devel] [Bug 1804961] [NEW] qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0 GH Cao
2018-11-24 20:36 ` [Qemu-devel] [Bug 1804961] " GH Cao
@ 2018-11-28 19:25 ` GH Cao
2018-12-04 12:43 ` Igor Mammedov
2018-11-29 4:57 ` GH Cao
` (4 subsequent siblings)
6 siblings, 1 reply; 10+ messages in thread
From: GH Cao @ 2018-11-28 19:25 UTC (permalink / raw)
To: qemu-devel
@imammedo:
I am new to kernel debugging, but I managed to get some traces, hope that will help you.
https://pastebin.com/shWUC1Pk
https://pastebin.com/n0gnSaVx
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
New
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
^ permalink raw reply [flat|nested] 10+ messages in thread* [Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:29 [Qemu-devel] [Bug 1804961] [NEW] qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0 GH Cao
2018-11-24 20:36 ` [Qemu-devel] [Bug 1804961] " GH Cao
2018-11-28 19:25 ` GH Cao
@ 2018-11-29 4:57 ` GH Cao
2018-12-05 11:32 ` Alex Bennée
` (3 subsequent siblings)
6 siblings, 0 replies; 10+ messages in thread
From: GH Cao @ 2018-11-29 4:57 UTC (permalink / raw)
To: qemu-devel
And the namespace objects tree of virt-2.12 is this.
https://pastebin.com/GybigJ9r
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
New
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
^ permalink raw reply [flat|nested] 10+ messages in thread* [Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:29 [Qemu-devel] [Bug 1804961] [NEW] qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0 GH Cao
` (2 preceding siblings ...)
2018-11-29 4:57 ` GH Cao
@ 2018-12-05 11:32 ` Alex Bennée
2018-12-05 11:57 ` GH Cao
` (2 subsequent siblings)
6 siblings, 0 replies; 10+ messages in thread
From: Alex Bennée @ 2018-12-05 11:32 UTC (permalink / raw)
To: qemu-devel
Could it be related to:
commit 17ec075a651a3f9613429c2d97018fce459ed943
Author: Eric Auger <eric.auger@redhat.com>
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
supports:
static void virt_machine_2_12_options(MachineClass *mc)
{
VirtMachineClass *vmc = VIRT_MACHINE_CLASS(OBJECT_CLASS(mc));
virt_machine_3_0_options(mc);
SET_MACHINE_COMPAT(mc, VIRT_COMPAT_2_12);
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.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
New
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
^ permalink raw reply [flat|nested] 10+ messages in thread* Re: [Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:29 [Qemu-devel] [Bug 1804961] [NEW] qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0 GH Cao
` (3 preceding siblings ...)
2018-12-05 11:32 ` Alex Bennée
@ 2018-12-05 11:57 ` GH Cao
2020-12-01 10:37 ` Thomas Huth
2021-01-31 4:17 ` Launchpad Bug Tracker
6 siblings, 0 replies; 10+ messages in thread
From: GH Cao @ 2018-12-05 11:57 UTC (permalink / raw)
To: qemu-devel
Yeah it seems to be. Windows boots fine after I disable hi ECAM region.
---Original---
From: "Alex Bennée"<alex.bennee@linaro.org>
Date: 2018/12/5 19:41:40
To: "driver1998"<driver1998@foxmail.com>;
Subject: [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
Could it be related to:
commit 17ec075a651a3f9613429c2d97018fce459ed943
Author: Eric Auger <eric.auger@redhat.com>
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
supports:
static void virt_machine_2_12_options(MachineClass *mc)
{
VirtMachineClass *vmc = VIRT_MACHINE_CLASS(OBJECT_CLASS(mc));
virt_machine_3_0_options(mc);
SET_MACHINE_COMPAT(mc, VIRT_COMPAT_2_12);
vmc->no_highmem_ecam = true;
mc->max_cpus = 255;
}
** Tags added: aarch64 acpi
--
You received this bug notification because you are subscribed to the bug
report.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
New
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
New
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:29 [Qemu-devel] [Bug 1804961] [NEW] qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0 GH Cao
` (4 preceding siblings ...)
2018-12-05 11:57 ` GH Cao
@ 2020-12-01 10:37 ` Thomas Huth
2021-01-31 4:17 ` Launchpad Bug Tracker
6 siblings, 0 replies; 10+ messages in thread
From: Thomas Huth @ 2020-12-01 10:37 UTC (permalink / raw)
To: qemu-devel
The QEMU project is currently considering to move its bug tracking to another system. For this we need to know which bugs are still valid and which could be closed already. Thus we are setting older bugs to "Incomplete" now.
If you still think this bug report here is valid, then please switch the state back to "New" within the next 60 days, otherwise this report will be marked as "Expired". Or mark it as "Fix Released" if the problem has been solved with a newer version of QEMU already. Thank you and sorry for the inconvenience.
** Changed in: qemu
Status: New => Incomplete
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
Incomplete
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
^ permalink raw reply [flat|nested] 10+ messages in thread* [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
2018-11-24 20:29 [Qemu-devel] [Bug 1804961] [NEW] qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0 GH Cao
` (5 preceding siblings ...)
2020-12-01 10:37 ` Thomas Huth
@ 2021-01-31 4:17 ` Launchpad Bug Tracker
6 siblings, 0 replies; 10+ messages in thread
From: Launchpad Bug Tracker @ 2021-01-31 4:17 UTC (permalink / raw)
To: qemu-devel
[Expired for QEMU because there has been no activity for 60 days.]
** Changed in: qemu
Status: Incomplete => Expired
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1804961
Title:
qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using
virt-3.0
Status in QEMU:
Expired
Bug description:
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
https://lists.gnu.org/archive/html/qemu-devel/2015-09/msg01719.html
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:
https://bugs.launchpad.net/qemu/+bug/1804961/+subscriptions
^ permalink raw reply [flat|nested] 10+ messages in thread