Ok so if I'm following this right there are two issues:
1. the bug reporter is using a powervm partition. KVM cannot be used there. This is not a KVM bug.
2. the xenial cloud images have an outdated 4.2 kernel which doesn't boot in kvm on powernv. A workaround is to use the isos which do boot. This is a cloud-images bug.
AFAICS there is no qemu bug here, so marking invalid for that package.
Ok so if I'm following this right there are two issues:
1. the bug reporter is using a powervm partition. KVM cannot be used there. This is not a KVM bug.
2. the xenial cloud images have an outdated 4.2 kernel which doesn't boot in kvm on powernv. A workaround is to use the isos which do boot. This is a cloud-images bug.
AFAICS there is no qemu bug here, so marking invalid for that package.