From: Glauber Costa <glommer@redhat.com>
To: Gabriel Southern <gabriel.southern@gmail.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] QEMU 0.10.5 release tomorrow
Date: Wed, 20 May 2009 23:02:05 -0300 [thread overview]
Message-ID: <20090521020205.GA17741@poweredge.glommer> (raw)
In-Reply-To: <3c2bf46d0905201853i38836a84oabfeb121ddf039ef@mail.gmail.com>
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.
prev parent reply other threads:[~2009-05-21 1:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-20 20:46 [Qemu-devel] QEMU 0.10.5 release tomorrow Anthony Liguori
2009-05-21 0:54 ` [Qemu-devel] " Alex
2009-05-21 1:53 ` [Qemu-devel] " Gabriel Southern
2009-05-21 2:02 ` Glauber Costa [this message]
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=20090521020205.GA17741@poweredge.glommer \
--to=glommer@redhat.com \
--cc=gabriel.southern@gmail.com \
--cc=qemu-devel@nongnu.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;
as well as URLs for NNTP newsgroup(s).