Comment 7 for bug 965525

But it seems that you are still correct.

I have tested it the whole day.

Everytime when I indroduce high harddrive traffic in a qemu-kvm guest(uck or remastersys running) the ata1 entries occures in the host kernel.log and when I ignore them, sooner or later not only the guest get frozen, also the host just behind.

That causes fielesytem corruption to my host, which until now I get managed to repair succesfully every time.

This is dangerous!

On the opposite when I introduce high harddrive traffic direct on my host(uck for .iso remastering) with no qemu-kvm guest started there are no ata1 errors in the kernel.log of my hostsytems.

Logically follows that the ata1 entries are caused by qemu-kvm only.