Comment 19 for bug 990364

I can't add much, except that I started noticing his issue when migrating my VMs to an Ubuntu Precise server hypervisor where under (heavy?) load my Win 2008 Server VM started to crash very frequently with the error showing up in the libvirt log of the VM.

It might be useful information that I ended up moving the VM back to a Debian Squeeze hypervisor which hosted it originally and things were running smoothly until earlier today when a crash with the same message happened again. What's sure is that under Squeeze the issue is far-far less frequent, on Precise the VM got reset a dozen times during the first 48 h, while on Squeeze it's been running fine even under heavy load for weeks without a hiccup.

Details of the Precise hypervisor:
kvm: 1:84+dfsg-0ubuntu16+1.0+noroms+0ubuntu14.3
qemu-kvm: 1.0+noroms-0ubuntu14.3
kernel: 3.2.0-32-generic
(tested with virtio drivers virtio-win-0.1-15.iso and virtio-win-0.1-30.iso)

Details of the Squeeze hypervisor:
kvm: 1:0.12.5+dfsg-5+squeeze8
qemu-kvm: 0.12.5+dfsg-5+squeeze8
kernel: 2.6.32-5-amd64
(tested with virtio drivers virtio-win-0.1-15.iso)