From: Igor Mammedov <imammedo@redhat.com>
To: GH Cao <1804961@bugs.launchpad.net>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [Bug 1804961] Re: qemu-system-aarch64: Windows 10 ARM64 BSoD on boot while using virt-3.0
Date: Mon, 26 Nov 2018 13:14:38 +0100 [thread overview]
Message-ID: <20181126131438.6a54e565@redhat.com> (raw)
In-Reply-To: <154309181512.10041.15816389425746279853.launchpad@chaenomeles.canonical.com>
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.
next prev parent reply other threads:[~2018-11-26 12:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
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-26 12:14 ` Igor Mammedov [this message]
2018-11-28 19:25 ` GH Cao
2018-12-04 12:43 ` Igor Mammedov
2018-11-29 4:57 ` GH Cao
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20181126131438.6a54e565@redhat.com \
--to=imammedo@redhat.com \
--cc=1804961@bugs.launchpad.net \
--cc=qemu-devel@nongnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).