Comment # 10 on bug 926594 from Jan Beulich

(In reply to lynda t from comment #9)
> This sound then like a definite Xen bug, and that a resolution requires
> integrating a known fix from upstream.

Where do you see the Xen bug here? It is a bug of the firmware not to mark for
runtime use any code/data that can be accessed by EFI Runtime Services calls.

> Looking at
> http://wiki.xenproject.org/wiki/Xen_Project_Hypervisor_Roadmap/4.5, 4.5.1,
> not even mentioned there, seems like it's many months out still.

The roadmap only talks about major releases, not stable ones afaik. We're going
to cut 4.5.1-rc1 within the next couple of weeks (preparations are already in
progress).

> But this ^^ has been marked 'wontfix'.  Does that mean the known fix will
> not be integrated into existing tree?  Just confused a bit.

For one there is no "known fix", only a workaround (hence the "wontfix"). And
then ...

> What's meant by a 'maintenance update' here?  Does that mean a patch will be
> backported to the existing 4.5.0 release in openSUSE's Xen sometime in the
> nearer future?  If it does, is there any roadmap / timeline?  Can't begin to
> use Xen in any sort of production until at least this gets resolved.

... 13.2 will pick up 4.4.3 eventually (that'll take some time, as 4.4.2 got
released pretty recently), and Factory will presumably pick up 4.5.1 once
available, i.e. the workaround will become available.