Not sure who should be the assignee here ... maybe it's best if you
write a mail to the people who have been involved in the original code
(see https://gitlab.com/qemu-project/qemu/-/commit/108a64818e69be0a97c )
and ask them who could have a look at this issue.
--
You received this bug notificati
Thanks Thomas Huth.
I couldn't find an option to assign the issue on gitlab to anyone. Can
you please help with that?
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1924603
Title:
Incorrect feature
This ticket has been moved here (thanks, Gautam):
https://gitlab.com/qemu-project/qemu/-/issues/331
... thus I'm closing this on Launchpad now.
** Bug watch added: gitlab.com/qemu-project/qemu/-/issues #331
https://gitlab.com/qemu-project/qemu/-/issues/331
** Changed in: qemu
Status: In
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://qemu-devel.nongnu.narkive.com/jUimpLt0/patch-vhost-net-initialize-acked-features-to-a-safe-value-during-ack
This review of a patch that introduced "acked_features = backend_features"
behaviour suggests that acked_features should be 0 by default, but it ended up
pushing it as it is now (as
QEMU version: 5.1.0
--
You received this bug notification because you are a member of qemu-
devel-ml, which is subscribed to QEMU.
https://bugs.launchpad.net/bugs/1924603
Title:
Incorrect feature negotiation for vhost-vdpa netdevice
Status in QEMU:
New
Bug description:
QEMU cmdline:
==
