Comment 7 for bug 1679704

Leveraging from the original bug this came from when debugging:

As a workaround for the case reported a user might set memtune options for the guest like this:
  <memtune>
    <hard_limit unit='KiB'>16961536</hard_limit>
    <soft_limit unit='KiB'>16961536</soft_limit>
  </memtune>

Needed numbers may vary depending on the case.
Ugly but a workaround at least.

This is still really awkward, at least we need to understand why it is even blocking when it should not.
If there is no fix that makes it "just work" I'm fine SRUing something into the libvirt/qemu profiles but we'd need to know what and so far we don't.