qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: "Justin M. Forbes" <jmforbes@linuxtx.org>
To: virt@lists.fedoraproject.org
Cc: qemu-devel@nongnu.org
Subject: [Qemu-devel] Fedora Virt Status
Date: Thu, 21 Jul 2011 11:05:34 -0500	[thread overview]
Message-ID: <1311264336.2967.155.camel@fedora64.linuxtx.org> (raw)

Fedora 15
- We have 65 open bugs 11 of which have fixes in awaiting updates.
- 12 bugs have been closed in the last week

Fedora 16
 Fedora 16 Feature Freeze is just 1 week away.  It is time to make sure 
 things are in shape for alpha. Important dates for the Fedora 16 Schedule:

    2011-07-26  Feature Freeze--Planning & Development Ends
    2011-07-26  Branch Fedora 16 from Rawhide-- Branch Freeze
    2011-08-02  Software String Freeze
    2011-08-02  Alpha Change Deadline
    2011-08-16  Alpha Release
    2011-08-30  Software Translation Deadline
    2011-09-06  Beta Change Deadline Features 100% Complete
    2011-09-20  Beta Release
    2011-10-10  Final Change Deadline
    2011-10-11  Compose 'Final' RC
    2011-10-25  Fedora 16 Final Release

 == Updates Needing review ==
  The following packages are in updates-testing and need review and karma as
  appropriate:

  F14:
  - libvirt-0.8.3-10.fc14
    CVE-2011-2511, integer overflow in VirDomainGetVcpus

  - libguestfs-1.8.9-1.fc14
    Stable branch update to version 1.8.9

  F15:
  - libguestfs-1.10.5-1.fc15
    Update to stable branch version 1.10.5.

  - spice-protocol-0.8.1-1.fc15
    this package doesn't close any bugs but it is required to build an updated spice-server that will close bugs.

  == Virt Preview Repository ==
  The virt-preview repository is now active for F15 users wishing to run the
  latest F16 virt packages on their stable F15 systems.  F14 virt-preview users
  will still get the latest F15 packages.  For details on how to run enable 
  virt-preview, please see:
  https://fedoraproject.org/wiki/Virtualization_Preview_Repository

  At the moment, virt preview is out of sync with F16 due to a bug in binutils
  which will not allow the new seabios to build.  Because libvirt requires the
  newer seabios, updates have been put on hold until the binutils fix is pushed
  to Fedora 15.

  == Bugs of importance: ==
  - 700560 F15 virt-manager gui locks/freezes in the default storage pool
    There is a bug which states that sym-linked storage pools will lock
    virt-manager, and now reports that the default storage pool does as well.

  - 720995 F15 kvm gets stuck while booting 32 bit guest on 64 bit host with smp
    This seems to be the kvmclock regression bug, and the patch will make the next
    update

             reply	other threads:[~2011-07-21 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-21 16:05 Justin M. Forbes [this message]
  -- strict thread matches above, loose matches on Subject: below --
2011-05-23 13:21 [Qemu-devel] Fedora virt status Justin M. Forbes
2011-04-26  3:46 [Qemu-devel] Fedora Virt Status Justin M. Forbes
2011-04-05 14:27 [Qemu-devel] Fedora virt status Justin M. Forbes
2011-03-29 14:03 [Qemu-devel] Fedora Virt status Justin M. Forbes
2011-03-04 18:45 [Qemu-devel] Fedora Virt Status Justin M. Forbes
2011-01-12 22:12 [Qemu-devel] Fedora Virt status Justin M. Forbes

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=1311264336.2967.155.camel@fedora64.linuxtx.org \
    --to=jmforbes@linuxtx.org \
    --cc=qemu-devel@nongnu.org \
    --cc=virt@lists.fedoraproject.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).