These fixes seem important, albeit unrelated to this specific problem we're dealing with.
I'd like to ask for IBM's input on the best approach to take here. If we decide to go along with backporting the fixes above, we might have to expand the scope of this bug.
Hello,
I'm working on this bug now, and I need at least one more patch backported from QEMU upstream:
https:/ /gitlab. com/qemu- project/ qemu/-/ commit/ bdbc87e323ee417 735141ed2b11dab 0091b57593
However, there are other fixes that have been added on top of the patch mentioned above, namely:
https:/ /gitlab. com/qemu- project/ qemu/-/ commit/ 703d03a4aaf38f2 85555ef5422ba5c e075416fc4 /gitlab. com/qemu- project/ qemu/-/ commit/ 349372ff9e3e7c0 47e258383f061a8 617f66adc3
https:/
These fixes seem important, albeit unrelated to this specific problem we're dealing with.
I'd like to ask for IBM's input on the best approach to take here. If we decide to go along with backporting the fixes above, we might have to expand the scope of this bug.
Thanks.