I've moved this bug over to GitLab here: https://gitlab.com/qemu-
project/qemu/-/issues/391
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #391
https://gitlab.com/qemu-project/qemu/-/issues/391
--
You received this bug notification because you are a member of qemu-
devel-ml, which
> https://bugs.launchpad.net/qemu/+bug/1869006
Unfortunately, that's not the same issue I'm having, and the error I see
happens regardless of how much or how little RAM I allocate to the VM.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to
I've done some more investigating, and have produced a backtrace of the
error:
#0 0x36b63228 in __libc_signal_restore_set (set=0x3fffcec8) at
../sysdeps/unix/sysv/linux/internal-signals.h:84
#1 0x36b63228 in __GI_raise (sig=) at
../sysdeps/unix/sysv/linux/raise.c:48
Public bug reported:
Attempting to pass through a PCIe device from a ppc64le host to an
x86_64 guest with QEMU v5.2.0-3031-g571d413b5d (built from git master)
fails with the following error:
include/exec/memory.h:43:IOMMU_MEMORY_REGION: Object 0x10438eb00 is
not an instance of type qemu:iommu
