Re: [Xen-devel] 4.2 TODO / Release Plan

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 06.08.12 at 18:17, George Dunlap <George.Dunlap@xxxxxxxxxxxxx> wrote:
> On Mon, Aug 6, 2012 at 9:58 AM, Ian Campbell <Ian.Campbell@xxxxxxxxxx> wrote:
>> 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.)
> 
> I can take this one.
> 
>> tools, nice to have:
> 
> * [BUG(?)] If domain 0 attempts to access a guests' memory before it
> is finished being built, and it is being built in PoD mode, this may
> cause the guest to crash.  Again, this is NOT a regression from 4.1.
> Furthermore, it's only been reported (AIUI) by a customer of OpenSuSE;

It's a SLES customer really, and hence is quite a bit more important
to us than if it was an openSUSE one. But we'd have to backport
an eventual fix anyway (as this was reported against 4.0.x), so
as long as a fix becomes available we'd be fine with backporting it
no matter whether it makes it into 4.2 (though of course, given
that all versions of the PoD code are affected, getting this fixed
in 4.0.4 and 4.1.3 would seem desirable).

> so it shoudn't be a blocker.  (Again, I'd be open to the idea that it
> should wait until after the release to get more testing.)
> 
> Jan, since you've got access to the system that reproduces it, do you
> want to take this one?  I think it should just be a matter of moving
> xc_domain_set_target() just before the while() loop in the domain
> builder (but after xc_domain_populate_physmap_exact, I think), and
> changing the loop to never allocate real memory in PoD mode.  I can do
> it, but it will be longer before we can get it tested.

If that's really expected to work, then yes, I can have them test
such a change (as indicated, on 4.0.x) and post the patch once
validated. But it wasn't really clear to me whether the non-PoD
allocation for at least the low 2Mb weren't on purpose (as that's
where BIOS image and hvmloader will end up sitting).

Jan


_______________________________________________
Xen-devel mailing list
Xen-devel@xxxxxxxxxxxxx
http://lists.xen.org/xen-devel