Great! Happy to help. We're all in same boat here, so we're happy to collaborate on making sure this is smooth for all QEMU based folks. Oddball bugs like this are never fun.
Good thing is that I think we've at least got this bug cornered, so now its just a matter of "who dun it?" in between what QEMU fixups can be made vs what Microsoft might need to engage on to fixup their side.