One of my KVM guests locked up again at 100% CPU! Any thoughts on how I can
diagnose it ? We would love to put into production but am very concerned about
the current stability. I have tried to re-direct the console, through screen,
to see whether there is a spin lock that is causing the problem; though all I
got in the log file was a login prompt. What is the correct way of redirecting
the console in KVM on a CentOS 6.4 system please ? Thanks.
--
To unsubscribe from this list: send the line "unsubscribe kvm" in
the body of a message to [email protected]
More majordomo info at http://vger.kernel.org/majordomo-info.html
