[fedora-virt] Fedora virt status

Justin M. Forbes jmforbes at linuxtx.org
Tue Jan 19 17:07:17 UTC 2010

Fedora 13

  As we move towards F-13, we are getting really close to the Feature
  Submission deadline.  Planned F-13 features can be seen at

  F-13 schedule:

  2010-01-26  Feature Submission Deadline (8 days)
  2010-02-09  Feature Freeze (22 days)
  2010-02-16  Alpha Freeze (29 days)
  2010-03-23  Beta (Final Development) Freeze (64 days)
  2010-04-29  Compose Release Candidate (101 days)

  Feature status should be updated to reflect current progress sooner rather
  than later.

  Now that qemu-0.12 has been added for F-13 we need as much testing as
  possible.  This can be tested by using rawhide, or for those who prefer an
  F-12 base, the virt-preview repository will allow you to test.

F12 Virt Preview

  As was announced before, the virt-preview repository for F12 users wishing
  to test out the latest virtualization bits is available.  Instructions for
  using this repository can be found at:

  Recent updates in this repository include:

  - Add new API virDomainMemoryStats
  - Public API and domain extension for CPU flags
  - vbox: Add support for version 3.1
  - Support QEMU's virtual FAT block device driver
  - a lot of fixes

  - Better null checking around Scheduled Parameters
  - Added error function callback

  - Point to seabios instead of bochs, and add a requires for seabios
  - Update to upstream
  - Remove patches included in upstream

  - Initial seabios package
  * Required for qemu-0.12 and newer.

  - Build with actual upstream tarball (not manually built dist)

  - Update to 0.2.1 release


  DOOM-O-METER: 211 bugs open 4 weeks ago, up to 216 now.

  We have a lot of work to do!

= Important =

== kernel ==

    KVM/networking-related crash

    This is related to guests using IPV6

== kvm ==

    SIGTRAP leakage between separate virtual machines

    buffer overflow in usb-linux.c

    Patch included, this will require an updated 0.11 push for F-12.

    almost 9 thousand syscalls per second while idle

    This is believed to be a result of the USB Tablet device, but several
    users have noticed high host CPU usage while guests were idle.

    Segfaults logged from kvm (qemu-kvm) resulting in guest sudden crash
    and data loss

    A number of users complaining of guests crashing and sometimes taking
    the host with them.  This appears to be related to sound emulation.

    reattach virtio to rhel{5,6} guests will cause qemu-kvm crash

    Reattaching virtio storage to a guest is causing host crashes.

== libvirt ==

    libvirt can generate bogus node device XML

    libvirt has a function for escaping XML strings that we clearly forgot to
    use here. In addition though we probably need to check where this garbage
    is coming from, because in this particular case we probably shouldn't be
    including the element at all.

More information about the virt mailing list