Comment 8 for bug 1936831

Just to clarify things a little bit. I don't believe this is actually very "unusual hardware". I try to develop software for Raspberry Pi (a common hardware platform) on my laptop and have installed QEmu to do so. If I use libvirt to start QEmu, I run into this exact same problem. Starting QEmu directly of course works and, these days, it does have support for emulating a Raspberry Pi.

If I fudge things by removing the "-no-acpi" command line option from being passed to QEmu, things work just as expected. So, I believe this could be as easy as checking the target machine type, and if it is any of the raspiXXX types, then drop this particular argument.