Since I have put monitoring in place it would appear that I haven't had the issue again in 3 days.
This is rather frustrating as it was happening every night. I'm going to dial back on some of the monitoring in case this was prompting it to stay alive unexpectedly (as I don't think the option of "run this script that keeps pinging stuff" is really a viable long term solution to the issue). I don't currently know a way of monitoring the packets/bytes per second of a VM from the host so I'm going to move the ping/reboot script off the quest and onto the host to see if this makes any difference. It's possible that if it was keeping it alive when sending pings from the guest, I may end up keeping it alive when sending to the guest as well. If this turns out to be the case I'll kill the pinging off and just leave the stats scripts running in the hope that it'll die at some stage and I'll be able to work out when it did and what throughput was happening at the time. If there are any other suggestions on how I could do monitoring on this I'd love to hear them. I may also try swapping to the e1000 at some point if I can get it to stop working again to prove that it's a virtio issue rather than something more generic. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1694625 Title: KVM Guest loses network connectivity under heavy load To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/qemu-kvm/+bug/1694625/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
