On Wed, Jul 03, 2013 at 12:44:01PM -0400, Don Zickus wrote: > > And why overcommitment is not a valid reason to generate a softlockup in > > the first place ? > > For the guest I don't believe it is. It isn't the guest's fault it > couldn't run processes. A warning should be scheduled on the host that it > couldn't run a process in a very long time. An interesting viewpoint is this: it does not matter who is at fault, whether the host or the guest. What matters is that an application in the guest is being starved of the least amount of resources for proper functioning (as specified by the watchdog threshold). The responsability for verifying that the least amount of resources for functioning of the guest application should not be entirely on the part of the host. -- To unsubscribe from this list: send the line "unsubscribe kvm" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
