[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Xen-users] Xen 4.2.0 Release Plan / TODO

19 March        -- TODO list locked down
2 April         -- Feature Freeze
30 July         -- Xen 4.2.0-rc1
8 August        -- Xen 4.2.0-rc2
23 August       -- Xen 4.2.0-rc3
Weekly          -- RCN+1 until release          << WE ARE HERE

We intend to release RC4 towards the end of this week. All being well
we intend for this to be the final release candidate. Please test!

The updated TODO list follows.

hypervisor, blockers:

    * None

tools, blockers:

    * libxl stable API -- we would like 4.2 to define a stable API
      which downstream's can start to rely on not changing. Aspects of
      this are:

        * None known

    * xl compatibility with xm:

        * No known issues

    * [CHECK] More formally deprecate xm/xend. Manpage patches already
      in tree. Needs release noting and communication around -rc1 to
      remind people to test xl. (DONE)

    * [CHECK] Confirm that migration from Xen 4.1 -> 4.2 works. (DONE
      for PV, HVM still TODO)

    * Bump library SONAMES as necessary.

    * [BUG] qemu-traditional has 50% cpu utilization on an idle
      Windows system if USB is enabled. Not 100% clear whether this is
      Xen or qemu.  George Dunlap thinks this is mostly down to 64-bit
      syscall overhead and is not a blocker, will drop from the list.

    * Disable generation id from xl. Microsoft changed the
      specification of this value between W8 beta and RC and we now
      implement the old spec. Disable for 4.2 and revist implementing
      the new spec for 4.3. (Paul Durrant, DONE)

hypervisor, nice to have:

    * [BUG(?)] Under certain conditions, the p2m_pod_sweep code will
      stop halfway through searching, causing a guest to crash even if
      there was zeroed memory available.  This is NOT a regression
      from 4.1, and is a very rare case, so probably shouldn't be a
      blocker.  (In fact, I'd be open to the idea that it should wait
      until after the release to get more testing.)
            (George Dunlap, defer until 4.3)

    * S3 regression(s?) reported by Ben Guthro (Ben & Jan Beulich)

    * fix high change rate to CMOS RTC periodic interrupt causing
      guest wall clock time to lag (Jan Beulich, core fix DONE for
      4.2, rest pushed out to post 4.2)

tools, nice to have:

    * xl compatibility with xm:

        * the parameter io and irq in domU config files are not
          evaluated by xl.  So it is not possible to passthrough a
          parallel port for my printer to domU when I start the domU
          with xl command. (reported by Dieter Bloms,
          <20120814100704.GA19704@xxxxxxxx>. Ian Campbell, patch posted)

        * xl doesn't support the '-a' option for shutdown, to shutdown
          all domains. (Reported by Sander Eikelenboom 

    * xl.cfg(5) documentation patch for qemu-upstream
      videoram/videomem support:
      qemu-upstream doesn't support specifying videomem size for the
      HVM guest cirrus/stdvga.  (but this works with
      qemu-xen-traditional). (Pasi KÃrkkÃinen, patches sent)

    * [BUG] 'xl vcpu-set' can't decrease the vCPU number of a HVM guest

    * Load blktap driver from xencommons initscript if available, thread at:
      <db614e92faf743e20b3f.1337096977@kodo2>. To be fixed more
      properly in 4.3. (DONE)

    * [BUG] xl allows same PCI device to be assigned to multiple
      guests. http://bugzilla.xen.org/bugzilla/show_bug.cgi?id=1826

    * "xl cpupool-create" segfault on incorrect input. Reported by
      George Dunlap,
      (Ian Jackson, DONE)

    * [BUG] xl fails on config files which are missing the final
      newline (Ian Jackson) 

Xen-users mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.