Comment 7 for bug 1646181

Was discussing this issue with QEMU upstream this morning. (Thanks to
Stefan Hajnoczi & Dan Berrange for the chat on IRC).

The "-9" is actually SIGKILL signal, which is expected when the CPU /
memory limits are hit.

Also:

    'Exit status' comes from an exception which is in turn populated
    from python subprocess "returncode" attribute, whichis just
    documented as "Exit status of the child process"

---

I was also incidentally triaging a downstream bug report that has
similar error: they seem to notice the said error if they upload images
to Glance that are > ~20GB in size and then booting an instance out of
it.

And, it seems like the reporter downstream has confirmed by increasing
the CPU limit from 2 to 8, they're able to successfully boot instances.

So, can you also try by increasing the CPU limit from 2 -> 8 (or
similar, based on your machine's specifications)?