From mboxrd@z Thu Jan 1 00:00:00 1970 From: Avi Kivity Subject: Re: qemu_mutex deadlock with -smp 2 Date: Tue, 15 Jan 2008 17:07:46 +0200 Message-ID: <478CCC42.6030402@qumranet.com> References: <20080114231331.GD3378@tree.beaverton.ibm.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org To: "Darrick J. Wong" Return-path: In-Reply-To: <20080114231331.GD3378-H2FdrP1KBX9hsM67afOH+sxtgHpCUUYS@public.gmane.org> 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 Darrick J. Wong wrote: > Hi, > > I'm attempting to run a KVM instance with 2 CPUs configured. The VM > appears to get most of the way through booting Ubuntu and then kvm locks > up. At that point there's nothing printed on stdout from the kvm > process and the monitor doesn't respond either. The host's kernel is > 2.6.24-rc7 and the kvm binary is built from git. > > Here's the command line I use: > > [...] > It appears that we're deadlocked on qemu_mutex; it would also appear > that disabling the network interface buys me a few more seconds until > the lockup occurs. Most of the time it is the case that post_kvm_run() > locked qemu_mutex and then kvm_eat_signal() tries to lock it as well. > Are you using qcow? If so, this may be the recently-committed smp aio deadlock fix. See 6bcdef5c1157bd7b526491252d20f8007ff2e9dc. Please try a fresh qemu-userspace.git. -- error compiling committee.c: too many arguments to function ------------------------------------------------------------------------- This SF.net email is sponsored by: Microsoft Defy all challenges. Microsoft(R) Visual Studio 2008. http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/