Thanks for moving it over! ... so I'm closing this on Launchpad now.
** Changed in: qemu
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1920013
Title:
Unable to
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
The QEMU project is currently moving its bug tracking to another system.
For this we need to know which bugs are still valid and which could be
closed already. Thus we are setting the bug state to "Incomplete" now.
If the bug has already been fixed in the latest upstream version of QEMU,
then plea
> 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 think cross-arch VFIO has already been discussed in:
https://bugs.launchpad.net/qemu/+bug/1869006
Perhaps you will have some answers.
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1920013
Title:
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
