public inbox for kvm@vger.kernel.org
 help / color / mirror / Atom feed
From: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
To: "Darrick J. Wong" <djwong-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: qemu_mutex deadlock with -smp 2
Date: Tue, 15 Jan 2008 17:07:46 +0200	[thread overview]
Message-ID: <478CCC42.6030402@qumranet.com> (raw)
In-Reply-To: <20080114231331.GD3378-H2FdrP1KBX9hsM67afOH+sxtgHpCUUYS@public.gmane.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/

  parent reply	other threads:[~2008-01-15 15:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-01-14 23:13 qemu_mutex deadlock with -smp 2 Darrick J. Wong
     [not found] ` <20080114231331.GD3378-H2FdrP1KBX9hsM67afOH+sxtgHpCUUYS@public.gmane.org>
2008-01-15 15:07   ` Avi Kivity [this message]
     [not found]     ` <478CCC42.6030402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-15 20:13       ` Darrick J. Wong
     [not found]         ` <20080115201340.GA7429-H2FdrP1KBX9hsM67afOH+sxtgHpCUUYS@public.gmane.org>
2008-01-15 20:39           ` Darrick J. Wong
     [not found]             ` <20080115203959.GB7429-H2FdrP1KBX9hsM67afOH+sxtgHpCUUYS@public.gmane.org>
2008-01-20 15:15               ` Avi Kivity
     [not found]                 ` <4793657B.2060709-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-22  0:17                   ` Darrick J. Wong
2008-01-27 13:31               ` Avi Kivity

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=478CCC42.6030402@qumranet.com \
    --to=avi-atkuwr5tajbwk0htik3j/w@public.gmane.org \
    --cc=djwong-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org \
    --cc=kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox