From: "Darrick J. Wong" <djwong-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
To: Avi Kivity <avi-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
Cc: kvm-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
Subject: Re: qemu_mutex deadlock with -smp 2
Date: Tue, 15 Jan 2008 12:13:40 -0800 [thread overview]
Message-ID: <20080115201340.GA7429@tree.beaverton.ibm.com> (raw)
In-Reply-To: <478CCC42.6030402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
On Tue, Jan 15, 2008 at 05:07:46PM +0200, Avi Kivity wrote:
> 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.
qcow2, actually. qcow + fresh git seems to reduce the deadlocks, but
not eliminate them entirely. Converting to raw fixes the problem.
--D
-------------------------------------------------------------------------
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/
next prev parent reply other threads:[~2008-01-15 20:13 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
[not found] ` <478CCC42.6030402-atKUWr5tajBWk0Htik3J/w@public.gmane.org>
2008-01-15 20:13 ` Darrick J. Wong [this message]
[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=20080115201340.GA7429@tree.beaverton.ibm.com \
--to=djwong-r/jw6+rmf7hqt0dzr+alfa@public.gmane.org \
--cc=avi-atKUWr5tajBWk0Htik3J/w@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