Can you still re-create this issue with the latest version of QEMU? If not, I think we should close this bug nowadays...
Can you still re-create this issue with the latest version of QEMU? If not, I think we should close this bug nowadays...