From: "Michael S. Tsirkin" <mst@redhat.com>
To: Nishank Trivedi <nishank.trivedi@netapp.com>
Cc: mdroth@linux.vnet.ibm.com, qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [ANNOUNCE] QEMU 2.1.0 is now available
Date: Tue, 5 Aug 2014 11:47:19 +0200 [thread overview]
Message-ID: <20140805094719.GA24619@redhat.com> (raw)
In-Reply-To: <53E03454.9060103@netapp.com>
On Mon, Aug 04, 2014 at 06:33:08PM -0700, Nishank Trivedi wrote:
> Hi Michael,
>
> I'm trying to send mail to qemu-devel, but it seems to be getting filtering
> out as I dont see it come over mailing list. Is there a keyword needed in
> subject for qemu-devel?
>
> I'm trying to report issue of x86 host hardlocking on doing pci-passthrough
> of PMC-sierra sas device through qemu (no libvirt in picture). Could you
> please point me to appropriate person/mailing-list to discuss this further?
>
> Thanks,
> Nishank
You are using the correct mailing list.
Sometimes our mailing list is down and does not
forward mail, let's see if this mail will get there,
if yes resending should help.
>
>
> On 8/1/14, 9:41 AM, Michael Roth wrote:
> >Hello,
> >
> >On behalf of the QEMU Team, I'd like to announce the availability of
> >the QEMU 2.1.0 release. This release contains 2200+ commits from 180
> >authors.
> >
> > http://wiki.qemu.org/download/qemu-2.1.0.tar.bz2
> >
> >The full list of changes are available at:
> >
> > http://wiki.qemu.org/ChangeLog/2.1
> >
> >Highlights include:
> >
> > * Support for memory hotplug on x86 guests
> > * Support for pinning memory on host NUMA nodes on x86 guests
> > * Basic hot-plug/hot-unplug support for x86 guests using Q35 machine-type
> > * Support for TCG-based system emulation on AArch64 (in addition
> > KVM-based virtualization)
> > * AArch64 SHA and Crypto instruction support.
> > * Support for VFIO-based device passthrough on pSeries/PowerKVM guests
> > * Migration support for virtio-ccw on s390x guests
> > * Improved IOMMU emulation for SPARC guests
> > * Full support for USB3 passthrough (including streams).
> > * Multi-seat support for GTK+ and SDL 2.0 UIs, and lots of bug fixes.
> > * Dedicated threading model for virtio-blk, virtio-blk dataplane, now supports
> > almost all features of the block layer including: image formats, POSIX AIO,
> > I/O throttling, statistics and error recovery
> > * Fixes migration from QEMU 1.7 when certain bridge/CPU combinations are in
> > use (see changelog for notes on migration incompatibilities between 2.0
> > and 2.1 for certain guest configuations), and new code/tools to detect
> > migration issues
> > * And lots more...
> >
> >Thank you to everyone involved!
> >
> >Sincerely,
> >
> >Michael Roth
> >
> >
> >
prev parent reply other threads:[~2014-08-05 9:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-01 16:41 [Qemu-devel] [ANNOUNCE] QEMU 2.1.0 is now available Michael Roth
2014-08-01 22:33 ` Peter Maydell
2014-08-04 9:50 ` Kevin Wolf
2014-08-04 12:56 ` Michael S. Tsirkin
2014-08-04 13:21 ` Mark Cave-Ayland
2014-08-04 13:37 ` Peter Maydell
[not found] ` <53E03454.9060103@netapp.com>
2014-08-05 9:47 ` Michael S. Tsirkin [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=20140805094719.GA24619@redhat.com \
--to=mst@redhat.com \
--cc=mdroth@linux.vnet.ibm.com \
--cc=nishank.trivedi@netapp.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).