[DragonFlyBSD - Bug #3310] (In Progress) NVMM+QEMU fail to boot with UEFI: Mem Assist Failed [gpa=0xfffffff0]

[bugtracker-admin at leaf.dragonflybsd.org]

Issue #3310 has been updated by liweitianux.

Category set to nvmm
Status changed from New to In Progress

A temporary workaround to boot with UEFI in NVMM+QEMU is:
specify the UEFI code with the @-bios@ option instead of the @-device if=pflash@ (or @-pflash@) option.

However, this is not recommended because the UEFI variables are partially emulated and aren't persistent.
See: https://lists.gnu.org/archive/html/qemu-discuss/2018-04/msg00045.html

----------------------------------------
Bug #3310: NVMM+QEMU fail to boot with UEFI: Mem Assist Failed [gpa=0xfffffff0]
http://bugs.dragonflybsd.org/issues/3310#change-14241

* Author: liweitianux
* Status: In Progress
* Priority: Normal
* Category: nvmm
* Target version: 6.4
* Start date: 2022-01-09
----------------------------------------
NVMM+QEMU fail to boot with UEFI, for example:

<pre>
% qemu-system-x86_64 \
      -boot menu=on -display sdl -accel nvmm \
      -drive file=OVMF_CODE.fd,if=pflash,format=raw,readonly=on \
      -drive file=OVMF_VARS.fd,if=pflash,format=raw
NetBSD Virtual Machine Monitor accelerator is operational
qemu-system-x86_64: NVMM: Mem Assist Failed [gpa=0xfffff000]
qemu-system-x86_64: NVMM: Failed to execute a VCPU.
</pre>

The UEFI firmware can be obtained by installing the @uefi-edk2-qemu-x86_64@ package
or by downloading from: https://leaf.dragonflybsd.org/~aly/uefi/

First reported by Mario Marietto and confirmed by me, see:
https://lists.dragonflybsd.org/pipermail/users/2022-January/404898.html



-- 
You have received this notification because you have either subscribed to it, or are involved in it.
To change your notification preferences, please click here: http://bugs.dragonflybsd.org/my/account