qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Subject: [Qemu-devel] Next stable release
Date: Fri, 20 Mar 2009 11:23:27 -0500	[thread overview]
Message-ID: <49C3C2FF.7060702@us.ibm.com> (raw)

We've accumulated a good number of patches in the stable tree.  I'd like 
to cut a release tomorrow sometime mid-day.  I wanted to cut a release 
this past Wednesday but was too busy.  Below is the current changelog.  
If you can, please test the stable tree and let me know if you run into 
any issues.  I'd appreciate holding off on committing any additional 
stable patches until after the release tomorrow.

Note, I've tried to make the changelog descriptive enough that someone 
can look at it to determine whether the stable release fixes their bug.

version 0.10.1:

  - virtio-net: allow masking of notifications on empty queue (Alex 
Williamson)
  - e1000: fix rx descriptor low threshold logic (Alex Willaimson)
  - x86 tcg: add NULL checks to lsl instruction (Jan Kiszka)
  - kvm vga: fix screen corruption with -std-vga and Windows (Avi Kivity)
  - kvm vga: fix screen corruption with Ubuntu installations (Glauber Costa)
  - virtio-net: check right return size on sg list (Alex Williamson)
  - Make qemu_announce_self handle holes (live migration after hotplug)
    (Marcelo Tosatti)
  - Revert r6804-r6808 (qcow2 allocation info).  This series of changes 
added
    a high cost to startup for large qcow2 images (Anthony Liguori)
  - qemu-img: fix help message (Aurelien Jarno)
  - Fix build for non-default installs of SDL (Anthony Liguori)
  - Fix race condition in env->interrupt_request.  When using TCG and a 
dynticks
    host timer, this condition could cause TCG to get stuck in an infinite
    loop (Aurelien Jarno)
  - Fix reading encrypted hard disk passwords during early startup (Jan 
Kiszka)
  - Fix encrypted disk reporting in 'info block' (Jan Kiszka)
  - Fix console size with tiny displays (MusicPal) (Jan Kiszka)
  - Improve error handling in bdrv_open2 (Jan Kiszka)
  - Avoid leaking data in mux'ed character devices (Jan Kiszka)
  - Fix initial character device reset (no banner in monitor) (Jan Kiszka)
  - Fix cpuid KVM crash on i386 host (Lubomir Rintel)
  - Fix SLES10sp2 installation by adding ISTAT1 register to LSI SCSI 
emulation
    (Ryan Harper)

Regards,

Anthony Liguori

             reply	other threads:[~2009-03-20 16:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-03-20 16:23 Anthony Liguori [this message]
2009-03-20 17:02 ` [Qemu-devel] Next stable release René Rebe
2009-03-20 20:20 ` Robert Riebisch
2009-03-21  9:05 ` Andreas Färber
  -- strict thread matches above, loose matches on Subject: below --
2009-04-05 19:38 Anthony Liguori
2009-04-06 13:08 ` TeLeMan
2009-04-06 13:43   ` Anthony Liguori
2009-04-07  1:38     ` Edgar E. Iglesias
2009-04-06 21:03   ` malc
2009-04-10  2:35     ` TeLeMan
2009-04-10  2:54       ` malc
2009-04-10  3:04         ` TeLeMan
2009-04-10  4:17           ` malc
2009-04-06 14:51 ` Stefan Weil
2009-04-07  1:11   ` Anthony Liguori
2009-04-07  6:06     ` Stefan Weil
2009-04-07  7:16       ` Aurelien Jarno
2009-04-07  9:27         ` Stefan Weil
2009-04-07 10:03           ` Aurelien Jarno

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=49C3C2FF.7060702@us.ibm.com \
    --to=aliguori@us.ibm.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).