[xen-unstable-smoke test] 175333: regressions - FAIL

[osstest service owner <osstest-admin@xxxxxxxxxxxxxx>]

flight 175333 xen-unstable-smoke real [real]
flight 175339 xen-unstable-smoke real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/175333/
http://logs.test-lab.xenproject.org/osstest/logs/175339/

Regressions :-(

Tests which did not succeed and are blocking,
including tests which could not be run:
 test-amd64-amd64-xl-qemuu-debianhvm-amd64 20 guest-start/debianhvm.repeat fail 
REGR. vs. 175292

Tests which did not succeed, but are not blocking:
 test-amd64-amd64-libvirt     15 migrate-support-check        fail   never pass
 test-arm64-arm64-xl-xsm      15 migrate-support-check        fail   never pass
 test-arm64-arm64-xl-xsm      16 saverestore-support-check    fail   never pass
 test-armhf-armhf-xl          15 migrate-support-check        fail   never pass
 test-armhf-armhf-xl          16 saverestore-support-check    fail   never pass

version targeted for testing:
 xen                  12b593ca0d61ef884c2f2de15ed36b4900fc92b2
baseline version:
 xen                  c8aaebccc8e8fb5d90080e664202b0011ce4d0bd

Last test of basis   175292  2022-12-15 20:00:29 Z    1 days
Testing same since   175333  2022-12-16 20:00:39 Z    0 days    1 attempts

------------------------------------------------------------
People who touched revisions under test:
  Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
  Jan Beulich <jbeulich@xxxxxxxx>

jobs:
 build-arm64-xsm                                              pass    
 build-amd64                                                  pass    
 build-armhf                                                  pass    
 build-amd64-libvirt                                          pass    
 test-armhf-armhf-xl                                          pass    
 test-arm64-arm64-xl-xsm                                      pass    
 test-amd64-amd64-xl-qemuu-debianhvm-amd64                    fail    
 test-amd64-amd64-libvirt                                     pass    


------------------------------------------------------------
sg-report-flight on osstest.test-lab.xenproject.org
logs: /home/logs/logs
images: /home/logs/images

Logs, config files, etc. are available at
    http://logs.test-lab.xenproject.org/osstest/logs

Explanation of these reports, and of osstest in general, is at
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README.email;hb=master
    http://xenbits.xen.org/gitweb/?p=osstest.git;a=blob;f=README;hb=master

Test harness code can be found at
    http://xenbits.xen.org/gitweb?p=osstest.git;a=summary


Not pushing.

------------------------------------------------------------
commit 12b593ca0d61ef884c2f2de15ed36b4900fc92b2
Author: Jan Beulich <jbeulich@xxxxxxxx>
Date:   Tue Dec 13 12:36:54 2022 +0100

    x86/mm: avoid phys_to_nid() calls for invalid addresses
    
    With phys_to_nid() now actively checking that a valid node ID is on
    record, the two uses in paging_init() can actually trigger at least the
    2nd of the assertions there. They're used to calculate allocation flags,
    but the calculated flags wouldn't be used when dealing with an invalid
    (unpopulated) address range. Defer the calculations such that they can
    be done with a validated MFN in hands. This also does away with the
    artificial calculations of an address to pass to phys_to_nid().
    
    Note that while the variable is provably written before use, at least
    some compiler versions can't actually verify that. Hence the variable
    also needs to gain a (dead) initializer.
    
    Fixes: e9c72d524fbd ("xen/x86: Use ASSERT instead of VIRTUAL_BUG_ON for 
phys_to_nid")
    Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx>
    Acked-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx>
(qemu changes not included)