On 25/05/2017 18:25, Felipe Franciosi wrote: > The perfect solution (for this throttling strategy) would probably be > a per-cpu timer. In the meantime, I think avoiding massive sleeps is > a win. We observed stalls in excess of 70 secs at 99% throttle.
Ah, so the issue is not overcommit, it's too high throttling. Then it makes sense. Thanks, Paolo >> How overcommitted was the host system? > Not overcommitted at all. And it's quite easy to reproduce. All you > need is a workload heavy enough to prevent the migration from > converging (or a slow network which you can emulate with a qdisc). > > With a Linux guest, you should quickly see soft lockups being > reported. With Windows, probably BSODs.
