From mboxrd@z Thu Jan  1 00:00:00 1970
Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43)
	id 1M6xWp-0001Az-Ce
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:57:03 -0400
Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43)
	id 1M6xWk-0001AW-22
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:57:02 -0400
Received: from [199.232.76.173] (port=52863 helo=monty-python.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.43) id 1M6xWj-0001AS-SD
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:56:57 -0400
Received: from mx2.redhat.com ([66.187.237.31]:33159)
	by monty-python.gnu.org with esmtp (Exim 4.60)
	(envelope-from <glommer@redhat.com>) id 1M6xWj-0001jL-BM
	for qemu-devel@nongnu.org; Wed, 20 May 2009 21:56:57 -0400
Date: Wed, 20 May 2009 23:02:05 -0300
From: Glauber Costa <glommer@redhat.com>
Subject: Re: [Qemu-devel] QEMU 0.10.5 release tomorrow
Message-ID: <20090521020205.GA17741@poweredge.glommer>
References: <4A146C19.8090203@codemonkey.ws>
	<3c2bf46d0905201853i38836a84oabfeb121ddf039ef@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <3c2bf46d0905201853i38836a84oabfeb121ddf039ef@mail.gmail.com>
List-Id: qemu-devel.nongnu.org
List-Unsubscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/pipermail/qemu-devel>
List-Post: <mailto:qemu-devel@nongnu.org>
List-Help: <mailto:qemu-devel-request@nongnu.org?subject=help>
List-Subscribe: <http://lists.nongnu.org/mailman/listinfo/qemu-devel>,
	<mailto:qemu-devel-request@nongnu.org?subject=subscribe>
To: Gabriel Southern <gabriel.southern@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>

On Wed, May 20, 2009 at 06:53:14PM -0700, Gabriel Southern wrote:
> There is a problem with qemu-system-sparc that causes a segmentation
> fault.  I think the problem was traced to the
> 9d07d7579bcaf01e05c511c63d091ed2ac310091 "PCI network qdev conversion"
> commit, but I have not seen a fix yet.  I'm not sure how to check the
> tagged release (I did not see a tag for v0.10.5) so I don't know if
> 0.10.5 will have this problem or not.
none of the qdev stuff is in stable.