All of
 help / color / mirror / Atom feed
From: Ian Jackson <>
Cc: "Jan Beulich" <>,
	"Andrew Cooper" <>,
	"Frédéric Pierret" <>,
	"Dario Faggioli" <>
Subject: [ANNOUNCE] Xen 4.15 release update - still in feature freeze
Date: Mon, 15 Mar 2021 12:18:09 +0000	[thread overview]
Message-ID: <> (raw)

Thanks everyone for your hard work so far.  I think things are looking
pretty good, although we have slipped.

Please see below for my updated list of release blockers and tracking
issues.  Please let me know if there is information missing, or if you
have corrections.

There is one issue on my radar that I am concerned about and want to
see sorted out: "io-apic issue on Ryzen 1800X".  If we can't get it
fixed soon we may have to live with it as a release notes issue.

I am probably going to take the scheduler issues off this list because
I haven't seen any sign of activity, and because I don't actually
think there are release critical bugs there.  Please let me know if
you disagree.

As previously announced, we are still in codefreeze.  All changes must
have a release-ack.

My current tentative schedule is:

   Tuesday 16th March  RC3 test day

   Wednesday 17th March
       Branch, turn off debug on the 4.15 branch
       xen-next will be open but only for non-disruptive changes

   Monday 22nd March   RC4
   Tuesday 23nd March  RC4 test day

   Week of 29th March **tentative*
       Release (probably Tuesday or Wednesday)



io-apic issue on Ryzen 1800X
Related Qubes issue tracking this:
Information from
  Jan Beulich <>
  Andrew Cooper <>
  Frédéric Pierret <>

ABI stability checking

   [PATCH for-4.15 00/10] tools: Support to use abi-dumper on libraries
   [PATCH v2 for-4.15] tools/libxl: Work around unintialised variable libxl__domain_get_device_model_uid()

This is testing/build work and will enable ABI checking of future
changes to 4.15 after its release.  I don't think it's a blocker but
it would be nice to have.

My most recent impression is that there are still some loose ends


BUG: credit=sched2 machine hang when using DRAKVUF

Information from
  Dario Faggioli <>

Quoting Dario:
| Manifests only with certain combination of hardware and workload. 
| I'm not reproducing, but there are multiple reports of it (see 
| above). I'm investigating and trying to come up at least with 
| debug patches that one of the reporter should be able and willing to 
| test.

Dario is working on this.  Last update 29.1.21 ?

G. Null scheduler and vwfi native problem

Information from
  Dario Faggioli <>


Quoting Dario:
| RCU issues, but manifests due to scheduler behavior (especially   
| NULL scheduler, especially on ARM).
| Patches that should solve the issue for ARM posted already. They
| will need to be slightly adjusted to cover x86 as well.

As of last update from Dario 29.1.21:
waiting for test report from submitter.

H. Ryzen 4000 (Mobile) Softlocks/Micro-stutters

Information from
  Dario Faggioli <>

As of last update from Dario 29.1.21:
Discussions currently ongoing about the severity of this issue.


Fallout from MSR handling behavioral change.

I think there are now no outstanding patches to fix/change MSR
behaviour and there is no longer any blocker here ?

Key partipants:
  Jan Beulich <>
  Andrew Cooper <>

Use-after-free in the IOMMU code

Information from
  Julien Grall <>
 [PATCH for-4.15 v5 0/3] xen/iommu: Collection of bug fixes for     
 IOMMU teardown
Now committed

"x86/PV: avoid speculation abuse through guest accessors"

Information from
  Jan Beulich <>

| F. The almost-XSA "x86/PV: avoid speculation abuse through guest
| accessors" - the first 4 patches are needed to address the actual
| issue. The next 3 patches are needed to get the tree into
| consistent state again, identifier-wise. The remaining patches
| can probably wait.

This has been committed.

Problems with xl save / cancel

Information from Jürgen Groß:
  xl daemon won't kill the domain after it has gone through a
  suspend-cancel cycle.

I think this was fixed by
  tools/libs/light: fix xl save -c handling

x86/time: calibration rendezvous adjustments

Information from
  Jan Beulich <>

Not entirely a regression.  3 out of the 4 patches seem to have been

Patch 4/ is not targeted at 4.15 I think.

             reply	other threads:[~2021-03-15 12:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-03-15 12:18 Ian Jackson [this message]
2021-03-15 13:10 ` [ANNOUNCE] Xen 4.15 release update - still in feature freeze Andrew Cooper
2021-03-15 13:46 ` Jan Beulich
2021-03-16  9:43   ` Roger Pau Monné
2021-03-16 10:12     ` Jan Beulich
2021-03-18 18:11 ` Dario Faggioli
2021-03-29 17:16   ` Dario Faggioli

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:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \ \ \ \ \ \ \ \ \

* 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.