[DragonFlyBSD - Bug #3310] 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.


mneumann wrote in #note-9:
> Here some more information:
> 
> letsnote$ groups
> mneumann wheel operator video nvmm
> 
> letsnote$ nvmmctl identify                                                     
> nvmm: Kernel API version 3
> nvmm: State size 1008
> nvmm: Comm size 4096
> nvmm: Max machines 128
> nvmm: Max VCPUs per machine 128
> nvmm: Max RAM per machine 127T
> nvmm: Arch Mach conf 0
> nvmm: Arch VCPU conf 0x3<CPUID,TPR>
> nvmm: Guest FPU states 0x3<x87,SSE>
> 
> 
> pkg ins edk2-qemu-x64-g202202_1
> 
> letsnote$ qemu-system-x86_64 --version                                         
> QEMU emulator version 6.0.0
> 
> 
> qemu-system-x86_64 \
>   -machine type=q35,accel=nvmm \
>   -smp cpus=1 -m 1G \
>   -cdrom FreeBSD-14.3-RELEASE-amd64-bootonly.iso \
>   -boot d \
>   -bios /usr/local/share/edk2-qemu/QEMU_UEFI-x86_64.fd \
>   -vga qxl \
>   -spice addr=127.0.0.1,port=5900,ipv4=on,disable-ticketing=on,seamless-migration=on
> 
> 
> This does not report "UEFI: Mem Assist Failed" error. Using "spicy" from package "spice-gtk" I can follow the boot process.But it hangs early in the FreeBSD kernel when the EFI Framebuffer is attached (see screenshot freebsd-boot.jpg).
> 
> If I remove -bios ... from above call, it gives me "UEFI: Mem Assist Failed" error.
> 
> Now let's try with pflash: 
> 
> qemu-system-x86_64 \
>   -machine type=q35,accel=nvmm \
>   -smp cpus=1 -m 1G \
>   -cdrom FreeBSD-14.3-RELEASE-amd64-bootonly.iso \
>   -display sdl \
>   -boot d \
>   -drive file=/tmp/QEMU_UEFI_CODE-x86_64.fd,if=pflash,format=raw,readonly=on \
>   -drive file=/tmp/QEMU_UEFI_VARS-x86_64.fd,if=pflash,format=raw
> 
> Here, I am getting "UEFI: Mem Assist Failed" error
> 
> 
> Now let's try with Qemu 9:
> 
> letsnote$ qemu-system-x86_64 --version                                         
> QEMU emulator version 9.0.1
> 
> Exactly the same problems.

This case is unrelated to UEFI booting but happened only on Intel systems.

It has been fixed in commit 0087a1d163488a57787a9a6431dd94070b1988d4.

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

* 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

---Files--------------------------------
qemu-system-x86.7z (3.5 MB)
freebsd-boot.jpg (68.1 KB)


-- 
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