On 20.10.2020 23:37, osstest service owner wrote: > flight 156027 xen-unstable real [real] > flight 156048 xen-unstable real-retest [real] > http://logs.test-lab.xenproject.org/osstest/logs/156027/ > http://logs.test-lab.xenproject.org/osstest/logs/156048/
Here as well as in the respective 4.14 and 4.13 reports the "retest" flights look to not really work, so they don't provide any additional useful data. Ian? > Regressions :-( > > Tests which did not succeed and are blocking, > including tests which could not be run: > test-amd64-i386-xl-qemut-debianhvm-i386-xsm 12 debian-hvm-install fail REGR. > vs. 156013 Taking together this and the respective 4.14 and 4.13 reports there looks to be an interaction problem with qemu: The gpa of the physical address of the NPF vCPU1 did encounter last points at 04:00.0, i.e. the (emulated) NIC. In the 4.x flights no such information is available (on VT-x the gpa of the last EPT violation doesn't get dumped when dumping the VMCS), but one of them shows Dom0 in the context of XEN_DMOP_set_pci_intx_level, again for 04:00.0. In any event the guests in all cases experience soft lockups. What I'm unable to do for the moment is put in place any kind of connection to the commits under test, but it's highly likely one of the security fixes committed yesterday. Jan
