All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrew Cooper <andrew.cooper3@citrix.com>
To: George Dunlap <George.Dunlap@eu.citrix.com>
Cc: xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Xen 4.4 development update: RC0 imminent
Date: Thu, 5 Dec 2013 16:34:01 +0000	[thread overview]
Message-ID: <52A0AAF9.9080309@citrix.com> (raw)
In-Reply-To: <CAFLBxZYvTK9BiVwi=Nt48aSRAZ_1xFY5dHNdnMVzGMtF8JUFOg@mail.gmail.com>

On 05/12/13 16:09, George Dunlap wrote:
> This information will be mirrored on the Xen 4.4 Roadmap wiki page:
>  http://wiki.xen.org/wiki/Xen_Roadmap/4.4
>
> We're nearly to the completion of the code freeze, scheduled for
> tomorrow.  After the code freeze, only bug fixes and features marked
> as "blockers" will be considered.  At the moment, the only feature
> considered a blocker is experimental PVH dom0 support.
>
> In early RCs, most bug fixes will be accepted; but in later RCs, even
> bug fixes may be rejected if they risk breaking more important
> functionality than they fix.
>
> I don't think at this point every bug fix needs a blessing from me;
> committers, if there are fixes which are obviously low-risk, just go
> ahead and check them in.
>
> I was thinking that for some of our new features, it would be good to
> have a blog post describing the feature and how to test it.  This
> would both raise awareness of the feature, and hopefully get it more
> testing before the release.  We could choose a couple to focus on for
> each test day.
>
> The code freeze will be complete tomorrow, but we will not be cutting
> the first RC until PVH dom0 support gets in (hopefully in the next few
> days).
>
> = Timeline =
>
> Here is our current timeline based on a 6-month release:
>
> * Feature freeze: 18 October 2013
> * Code freezing point: 18 November 2013 <== WE ARE HERE
> * First RCs: 6 December 2013
> * Release: 21 January 2014
>
> Last updated: 5 December 2013
>
> == Completed ==
>
> * Event channel scalability (FIFO event channels)
>
> * Non-udev scripts for driver domains (non-Linux driver domains)
>
> * Multi-vector PCI MSI (Hypervisor side)
>
> * Improved Spice support on libxl
>  - Added Spice vdagent support
>  - Added Spice clipboard sharing support
>
> * PHV domU (experimental only)
>
> * pvgrub2 checked into grub upstream (external)
>
> * ARM64 guest
>
> * Guest EFI booting (tianocore)
>
> * kexec
>
> * Testing: Xen on ARM
>
> * Update to SeaBIOS 1.7.3.1
>
> * Update to qemu 1.6
>
> * SWIOTLB (in Linux 3.13)
>
> * Disk: indirect descriptors (in 3.11)
>
> == Resolved since last update ==
>
> * xen_platform_pci=0 doesn't work with qemu-xen
>
> == Open ==
>
> * qemu-upstream not freeing pirq
>  > http://www.gossamer-threads.com/lists/xen/devel/281498
>  > http://marc.info/?l=xen-devel&m=137265766424502
>  status: patches posted; latest patches need testing
>
> * Race in PV shutdown between tool detection and shutdown watch
>  > http://www.gossamer-threads.com/lists/xen/devel/282467
>  > Nothing to do with ACPI
>  status: Patches posted
>
> * Supposed regression from a3513737 ("x86: allow guest to set/clear
>  > MSI-X mask bit (try 2)"), as per
>  > http://lists.xenproject.org/archives/html/xen-devel/2013-09/msg01589.html.

There was no followup on that, so is possibly stale.

There has been a more recent commit
(http://xenbits.xen.org/gitweb/?p=xen.git;a=commitdiff;h=74fd0036deb585a139b63b26db025805ecedc37a)
which fixes up a Xen-Qemu communication error when unmasking MSI-X
interrupts which might be related?

>
> * qemu-traditional mis-parses host bus 8 as 0
>  > http://bugs.xenproject.org/xen/bug/15
>
> * xl does not support specifying virtual function for passthrough device
>  > http://bugs.xenproject.org/xen/bug/22
>
> * xl support for vnc and vnclisten options with PV guests
>  > http://bugs.xenproject.org/xen/bug/25
>
> * xl does not handle migrate interruption gracefully
>   > If you start a localhost migrate, and press "Ctrl-C" in the middle,
>   > you get two hung domains
>
> * libxl / xl does not handle failure of remote qemu gracefully
>   > Easiest way to reproduce:
>   >  - set "vncunused=0" and do a local migrate
>   >  - The "remote" qemu will fail because the vnc port is in use
>   > The failure isn't the problem, but everything being stuck afterwards is
>
> * xl needs to disallow PoD with PCI passthrough
>   >see http://xen.1045712.n5.nabble.com/PATCH-VT-d-Dis-allow-PCI-device-assignment-if-PoD-is-enabled-td2547788.html
>
> * HPET interrupt stack overflow (when using hpet_broadcast mode and MSI
> capable HPETs)
>   owner: andyh@citrix
>   status: patches posted, undergoing review iteration.

* Win2k3 SP2 RTC infinite loops
   > Regression introduced late in Xen-4.3 development
   owner: andrew.cooper@citrix
   status: patches posted, undergoing review. ( v2 ID
1386241748-9617-1-git-send-email-andrew.cooper3@citrix.com )

~Andrew

>
> * PCI hole resize support hvmloader/qemu-traditional/qemu-upstream
> with PCI/GPU passthrough
>   > http://lists.xen.org/archives/html/xen-devel/2013-05/msg02813.html
>   > Where Stefano writes:
>   > 2) for Xen 4.4 rework the two patches above and improve
>   > i440fx_update_pci_mem_hole: resizing the pci_hole subregion is not
>   > enough, it also needs to be able to resize the system memory region
>   > (xen.ram) to make room for the bigger pci_hole
>
> * qemu memory leak?
>   > http://lists.xen.org/archives/html/xen-users/2013-03/msg00276.html
>
> === Big ticket items ===
>
> * PVH dom0 (w/ Linux)
>   owner: mukesh@oracle, george@citrix
>   status (Linux): Acked, waiting for ABI to be nailed down
>   status (Xen): v5 posted; considered a blocker
>
> * libvirt/libxl integration (external)
>  - owner: jfehlig@suse, dario@citrix
>  - patches posted (should be released before 4.4)
>   - migration
>   - PCI pass-through
>  - In progress
>   - integration w/ libvirt's lock manager
>   - improved concurrency
>
> * libxl: Spice usbredirection support for upstream qemu
>  > Includes usb2/3 support
>  status: v2 acked
>  prognosis: good
>
> _______________________________________________
> Xen-devel mailing list
> Xen-devel@lists.xen.org
> http://lists.xen.org/xen-devel

  parent reply	other threads:[~2013-12-05 16:34 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-12-05 16:09 Xen 4.4 development update: RC0 imminent George Dunlap
2013-12-05 16:29 ` George Dunlap
2013-12-05 16:34   ` Wei Liu
2013-12-05 16:39     ` George Dunlap
2013-12-05 16:48       ` Wei Liu
2013-12-05 16:59         ` Ian Campbell
2013-12-05 17:06           ` Wei Liu
2013-12-05 17:16             ` Ian Campbell
2013-12-05 17:34               ` Wei Liu
2013-12-05 17:53                 ` George Dunlap
2013-12-05 18:03                   ` Wei Liu
2013-12-06  9:27                     ` Ian Campbell
2013-12-06 10:51                       ` Wei Liu
2013-12-05 16:39   ` Vladimir 'φ-coder/phcoder' Serbinenko
2013-12-05 16:41     ` George Dunlap
2013-12-05 16:42   ` Roger Pau Monné
2013-12-05 16:51     ` George Dunlap
2013-12-05 17:01       ` Lars Kurth
2013-12-05 17:04         ` George Dunlap
2013-12-05 20:06           ` Russell Pavlicek
2013-12-05 23:54             ` Sander Eikelenboom
2013-12-06  9:39             ` Lars Kurth
2013-12-06 12:14             ` George Dunlap
2013-12-05 16:59   ` David Vrabel
2013-12-05 17:05     ` George Dunlap
2013-12-05 17:40       ` Dario Faggioli
2013-12-05 17:07     ` George Dunlap
2013-12-05 17:01   ` Olaf Hering
2013-12-05 17:06     ` David Vrabel
2013-12-05 17:32   ` Dario Faggioli
2013-12-06 13:30   ` Fabio Fantoni
2013-12-05 16:34 ` Andrew Cooper [this message]
2013-12-06  9:07   ` Jan Beulich
2013-12-06 13:07     ` George Dunlap
2013-12-06 14:58       ` Jan Beulich
2013-12-05 16:54 ` George Dunlap
2013-12-16 10:50   ` Lars Kurth

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=52A0AAF9.9080309@citrix.com \
    --to=andrew.cooper3@citrix.com \
    --cc=George.Dunlap@eu.citrix.com \
    --cc=xen-devel@lists.xenproject.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.