Hrm, I think the performance results are a bit too good to be true. Looking more closely at the code and the announcement, I can see why:
1) Native KVM tool is using virtio whereas they're launching QEMU with IDE. IDE only supports a single request at a time (this is how the hardware works).
2) Native KVM tool does not make guest data writes stable by default. QEMU does. While they do advertise the FLUSH feature, they don't advertise a write cache setting to the guest. Unfortunately, many modern guests assume storage with non-volatile write caches and don't use FLUSH's properly.
I would expect QEMU configured in the same way that Native KVM tool would be at least as good. I also would recommend that type of configuration for anyone that cared about their data as a default.