> > > Two approaches to get closer to the source of the problem: > > > 1. Try the latest vanilla kernel on the host (Linux 3.10.5). This way > > > you can rule out fixed bugs in vhost_net or tap. > > > 2. Get the system into the bad state and then do some deeper. Start > > > with outgoing ping, instrument guest driver and host vhost_net > > > functions to see what the drivers are doing, inspect the transmit > > > vring, etc. > > > > > > #1 is probably the best next step. If it fails and you still have time > > > to work on a solution we can start digging deeper with #2. > > > > I can upgrade now to 3.10.3 as that is the current version in debian. > > Sounds good. That way you'll also have access to the latest perf for > instrumenting vhost_net if it still fails.
It seems some of perf is in the debian kernel and some isn't. So I have to request them to include that. That might take a while. I have a feeling but I did not write it down so I'm not 100% sure that this problem mosly happens (starts at) 18:30 and also past 00:00. That would make one say: then the problem is with that vm. I don't think it is also at least one other vm/guest has this problem. Only very very much less than this problem vm. I'm going to make a list for when it happens. Folkert van Heusden -- Feeling generous? -> http://www.vanheusden.com/wishlist.php ---------------------------------------------------------------------- Phone: +31-6-41278122, PGP-key: 1F28D8AE, www.vanheusden.com -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majord...@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
