Jim Paris wrote: > If I stop KVM in the monitor with "stop", wait a minute, and do > "cont", a Linux guest gives me a "BUG: soft lockup detected on CPU#0". > Is that expected behavior?
No. > What isn't virtualized that allows it to > detect that? The host is a core 2 duo. > > It may be that the timer correction code detects that zillions of timer interrupts have not been serviced by the guest so it floods the guest with these interrupts. Does -no-kvm-irqchip help? -- Do not meddle in the internals of kernels, for they are subtle and quick to panic. ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ kvm-devel mailing list kvm-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/kvm-devel