From: "Alex Bennée" <alex.bennee@linaro.org>
To: qemu-devel@nongnu.org
Subject: [Bug 1821595] Re: Failed to emulate MMIO access with EmulatorReturnStatus: 2
Date: Mon, 06 Apr 2020 13:54:57 -0000 [thread overview]
Message-ID: <158618129708.24863.428231285462234220.malone@soybean.canonical.com> (raw)
In-Reply-To: 155352235092.32006.12315829232895734213.malonedeb@soybean.canonical.com
As far as I can tell QEMU just hands this off to the whpx emulation sub-
system:
https://docs.microsoft.com/en-us/virtualization/api/hypervisor-
instruction-emulator/funcs/whvemulatortryemulation
Basically what is happening is the guest has tried to access I/O space
and trapped back to QEMU which then passes the instruction back to the
whpx support library to decode and emulate.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1821595
Title:
Failed to emulate MMIO access with EmulatorReturnStatus: 2
Status in QEMU:
New
Bug description:
I have compiled qemu with enable-whpx parameter for Hyper-V Platform API in Mingw64 . When I tried run with Windows 7 iso file I have faced issue with the following problem:
qemu-system-x86_64.exe: WHPX: Failed to emulate MMIO access with EmulatorReturnStatus: 2
qemu-system-x86_64.exe: WHPX: Failed to exec a virtual processor
configuration directives:
../configure --target-list=x86_64-softmmu,i386-softmmu --enable-lzo\
--enable-bzip2 --enable-tools --enable-sdl --enable-gtk --enable-hax\
--enable-vdi --enable-qcow1 --enable-whpx --disable-capstone\
--disable-werror --disable-stack-protector --prefix="../../QEMU-bin"
Qemu command line:
qemu-system-x86_64.exe -m 1024 -cdrom "C:\Users\vmcs\Documents\en_windows_7_home_premium_with_sp1_x86_dvd_u_676701.iso" -display sdl -machine q35 -accel whpx
To manage notifications about this bug go to:
https://bugs.launchpad.net/qemu/+bug/1821595/+subscriptions
next prev parent reply other threads:[~2020-04-06 14:17 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <155352235092.32006.12315829232895734213.malonedeb@soybean.canonical.com>
2020-04-06 0:51 ` [Bug 1821595] Re: Failed to emulate MMIO access with EmulatorReturnStatus: 2 Russell Morris
2020-04-06 1:14 ` Russell Morris
2020-04-06 7:23 ` Emin Ghuliev
2020-04-06 7:36 ` Emin Ghuliev
2020-04-06 10:20 ` Alex Bennée
2020-04-06 13:54 ` Alex Bennée [this message]
2020-04-09 17:41 ` Russell Morris
2020-04-09 17:53 ` Emin Ghuliev
2020-04-09 18:28 ` Russell Morris
2020-04-09 18:30 ` Russell Morris
2020-04-09 20:07 ` Alex Bennée
2020-04-09 20:22 ` Russell Morris
2020-04-12 1:31 ` Russell Morris
2020-04-12 1:31 ` Russell Morris
2020-09-29 23:54 ` Fernando Luiz
2021-04-20 8:27 ` Thomas Huth
2021-06-20 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=158618129708.24863.428231285462234220.malone@soybean.canonical.com \
--to=alex.bennee@linaro.org \
--cc=1821595@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).