Re: [Xen-devel] [xen-unstable test] 110009: regressions - FAIL

["Jan Beulich" <JBeulich@xxxxxxxx>]

>>> On 05.06.17 at 18:55, <osstest-admin@xxxxxxxxxxxxxx> wrote:
> flight 110009 xen-unstable real [real]
> http://logs.test-lab.xenproject.org/osstest/logs/110009/ 
> 
> Regressions :-(
> 
> Tests which did not succeed and are blocking,
> including tests which could not be run:
>  test-amd64-amd64-xl-qemut-win7-amd64 15 guest-localmigrate/x10 fail REGR. 
> vs. 109841

So finally we have some output from the debugging code added by
933f966bcd ("x86/mm: add temporary debugging code to
get_page_from_gfn_p2m()"), i.e. the migration heisenbug we hope
to hunt down:

(XEN) d0v2: d7 dying (looking up 3e000)
...
(XEN) Xen call trace:
(XEN)    [<ffff82d0803150ef>] get_page_from_gfn_p2m+0x7b/0x416
(XEN)    [<ffff82d080268e88>] arch_do_domctl+0x51a/0x2535
(XEN)    [<ffff82d080206cf9>] do_domctl+0x17e4/0x1baf
(XEN)    [<ffff82d080355896>] pv_hypercall+0x1ef/0x42d
(XEN)    [<ffff82d0803594c6>] entry.o#test_all_events+0/0x30

which points at XEN_DOMCTL_getpageframeinfo3 handling code.
What business would the tool stack have invoking this domctl for
a dying domain? I'd expect all of these operations to be done
while the domain is still alive (perhaps paused), but none of them
to occur once domain death was initiated.

Jan


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