From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jim Paris Subject: soft lockup after stop/cont Date: Wed, 10 Oct 2007 04:01:52 -0400 Message-ID: <20071010080152.GA27601@jim.sh> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Return-path: Content-Disposition: inline List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org Errors-To: kvm-devel-bounces-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org List-Id: kvm.vger.kernel.org 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? What isn't virtualized that allows it to detect that? The host is a core 2 duo. I have bigger problems in the guest after migrating to a file and restoring from that, but this seems like a good place to start.. -jim ------------------------------------------------------------------------- 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/