Fix is now committed on master as SHA-1 cf45183b718f02b1369e18c795dc51bc1821245d, which actually just reverted the mentioned commit that was leading to this broken behavior: https://github.com/qemu/qemu/commit/cf45183b718f02b1369e18c795dc51bc1821245d
The original Xen transport bug that motivated that change, was now fixed differently by handling that Xen issue solely on Xen transport driver side: https://github.com/qemu/qemu/commit/a4c4d462729466c4756bac8a0a8d77eb63b21ef7
Fix is now committed on master as SHA-1 cf45183b718f02b 1369e18c795dc51 bc1821245d, which actually just reverted the mentioned commit that was leading to this broken behavior: /github. com/qemu/ qemu/commit/ cf45183b718f02b 1369e18c795dc51 bc1821245d
https:/
The original Xen transport bug that motivated that change, was now fixed differently by handling that Xen issue solely on Xen transport driver side: /github. com/qemu/ qemu/commit/ a4c4d462729466c 4756bac8a0a8d77 eb63b21ef7
https:/