FS#76760 - edk2-ovmf 202211-3 crashes qemu-system-x86_64 at VFIO_MAP_DMA phase

Attached to Project: Arch Linux
Opened by j angel riarola (txangel) - Wednesday, 07 December 2022, 00:08 GMT
Last edited by Toolybird (Toolybird) - Wednesday, 07 December 2022, 04:59 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture x86_64
Severity Medium
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:

edk2-ovmf 202211-3 seems to be causing crashes on startup when using vfio on qemu-system-x86_64

The previous version 202208-2 works fine.

This might look like duplicate of https://bugs.archlinux.org/task/76732 but symptoms are different as this is an immediate crash and is on the new version and not the old one.

The errors are as follow:

2022-12-05T13:26:34.568681Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2022-12-05T13:26:34.568704Z qemu-system-x86_64: vfio_dma_map(0x55fb5f4e2d00, 0x384000000000, 0x10000000, 0x7f72ac000000) = -2 (No such file or
directory)
2022-12-05T13:26:34.569946Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2022-12-05T13:26:34.569954Z qemu-system-x86_64: vfio_dma_map(0x55fb5f4e2d00, 0x384010000000, 0x2000000, 0x7f72aa000000) = -22 (Invalid argumen
t)
2022-12-05T13:26:34.740282Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2022-12-05T13:26:34.740293Z qemu-system-x86_64: vfio_dma_map(0x55fb5f4e2d00, 0x384000000000, 0x10000000, 0x7f72ac000000) = -22 (Invalid argume
nt)
2022-12-05T13:26:34.740731Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2022-12-05T13:26:34.740738Z qemu-system-x86_64: vfio_dma_map(0x55fb5f4e2d00, 0x384010000000, 0x2000000, 0x7f72aa000000) = -22 (Invalid argumen
t)
2022-12-05T13:26:34.748184Z qemu-system-x86_64: VFIO_MAP_DMA failed: Invalid argument
2022-12-05T13:26:34.748191Z qemu-system-x86_64: vfio_dma_map(0x55fb5f4e2d00, 0x380800000000, 0x8000000, 0x7f72d3dff000) = -22 (Invalid argumen
t)
qemu: hardware error: vfio: DMA mapping failed, unable to continue
<Then qemu dump of registers>


Additional info:
* edk2-ovmf 202211-3
* There is a thread with some hypothesis https://www.reddit.com/r/VFIO/comments/zaoy5o/warning_newest_arch_qemu_packages_may_break_your/

Steps to reproduce:

1. Create a new domain for Windows 10 or Windows 11 (you can use an old image or even try to run the installer, it crashes before reaching UEFI)
2. Attach a PCIe GPU to the domain
3. Start the domain
   win11-2.log (57.6 KiB)
This task depends upon

Closed by  Toolybird (Toolybird)
Wednesday, 07 December 2022, 04:59 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#76466 
Comment by j angel riarola (txangel) - Wednesday, 07 December 2022, 00:30 GMT
A couple of interesting changes I could find so far:
https://github.com/archlinux/svntogit-packages/commit/6cbcbe8f7f72b9e08de4c0193fe205b861083cb2: Where a number of paths change, perhaps that is the source of the no such file error
https://github.com/archlinux/svntogit-packages/commit/53c32fe3ff3e555c4c70784ca07a3de2c86a5446: Support for CSM which I presume is what lies down the /var/lib/libvirt/qemu/nvram/<domain name>_VARS.fd

When I can I will run a test of upgrading and creating symlinks around from /usr/share/edk2/ to/usr/share/edk2-ovmf/ so both paths work
Comment by Toolybird (Toolybird) - Wednesday, 07 December 2022, 04:59 GMT
> The previous version 202208-2 works fine.

There was a change in 202208-3 which unfortunately requires manual intervention for some folks. Please see [1] for the solutions. More info in  FS#76466 . Please take any further discussion to the proper support channels (forum/IRC/etc).

[1] https://bugs.archlinux.org/task/76238#comment212141

Loading...