The VM has now had the problem recur again with the monitoring showing that just before it stops functioning nothing appears to be odd/excessive with the network usage.
As such, I may have mis-titled my bug as I had assumed it was heavy load causing the issue. One thing which struck me as slightly odd with it was that during the time it was not responding it's showing a small number of packets being received but nothing going out: 170613-210207: TX ens3: 1578 pkts/s RX ens3: 2690 pkts/s 170613-210217: TX ens3: 1090 pkts/s RX ens3: 1324 pkts/s 170613-210227: TX ens3: 0 pkts/s RX ens3: 17 pkts/s 170613-210237: TX ens3: 0 pkts/s RX ens3: 12 pkts/s 170613-210247: TX ens3: 0 pkts/s RX ens3: 13 pkts/s 170613-210257: TX ens3: 0 pkts/s RX ens3: 13 pkts/s 170613-210307: TX ens3: 0 pkts/s RX ens3: 12 pkts/s 170613-210317: TX ens3: 0 pkts/s RX ens3: 13 pkts/s 170613-210327: TX ens3: 0 pkts/s RX ens3: 12 pkts/s 170613-210337: TX ens3: 0 pkts/s RX ens3: 13 pkts/s 170613-210347: TX ens3: 0 pkts/s RX ens3: 12 pkts/s 170613-210357: TX ens3: 0 pkts/s RX ens3: 10 pkts/s 170613-210407: TX ens3: 0 pkts/s RX ens3: 11 pkts/s 170613-210417: TX ens3: 0 pkts/s RX ens3: 12 pkts/s 170613-210427: TX ens3: 0 pkts/s RX ens3: 13 pkts/s 170613-210437: TX ens3: 0 pkts/s RX ens3: 11 pkts/s I will have to set up monitoring on the host side as well to see if it reports the same. -- 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
