The patch addresses the current issue for me, thanks! Is it possible to make it more future proof? I can imagine a very similar situation arising in the future and it would be good to be able to handle it gracefully. If it's not possible, then maybe there's a way to output some sort of error from qemu that a user can search for. Right now all one gets is a qemu process using 100% of CPU and outputting nothing. None of this is required for this patch, but it would be good to have it at some point.
Reviewed-by: Ivan Babrou <i...@cloudflare.com>
