* [xen-unstable-smoke test] 100564: regressions - FAIL
@ 2016-08-19 20:03 osstest service owner
0 siblings, 0 replies; only message in thread
From: osstest service owner @ 2016-08-19 20:03 UTC (permalink / raw)
To: xen-devel, osstest-admin
flight 100564 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/100564/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-armhf-armhf-xl 7 host-ping-check-xen fail REGR. vs. 100561
Tests which did not succeed, but are not blocking:
test-amd64-amd64-libvirt 12 migrate-support-check fail never pass
version targeted for testing:
xen 2a99aa99fc84a45f505f84802af56b006d14c52e
baseline version:
xen f8992212c9ee537e67f30841e3232b982d74af2b
Last test of basis 100561 2016-08-19 16:01:07 Z 0 days
Testing same since 100564 2016-08-19 18:01:31 Z 0 days 1 attempts
------------------------------------------------------------
People who touched revisions under test:
Andrew Cooper <andrew.cooper3@citrix.com>
Jan Beulich <jbeulich@suse.com>
jobs:
build-amd64 pass
build-armhf pass
build-amd64-libvirt pass
test-armhf-armhf-xl fail
test-amd64-amd64-xl-qemuu-debianhvm-i386 pass
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 2a99aa99fc84a45f505f84802af56b006d14c52e
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Fri Aug 19 15:08:10 2016 +0100
xen/physmap: Do not permit a guest to populate PoD pages for itself
PoD is supposed to be entirely transparent to guest, but this interface has
been left exposed for a long time.
The use of PoD requires careful co-ordination by the toolstack with the
XENMEM_{get,set}_pod_target hypercalls, and xenstore ballooning target. The
best a guest can do without toolstack cooperation crash.
Furthermore, there are combinations of features (e.g. c/s c63868ff "libxl:
disallow PCI device assignment for HVM guest when PoD is enabled") which a
toolstack might wish to explicitly prohibit (in this case, because the two
simply don't function in combination). In such cases, the guest mustn't be
able to subvert the configuration chosen by the toolstack.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
commit f2c060fc972b1cb7aa7a1be35508a9ebfd564fdc
Author: Andrew Cooper <andrew.cooper3@citrix.com>
Date: Fri Aug 19 14:28:54 2016 +0100
xen/memop: Latch current->domain in a local variable
It is more efficient.
Signed-off-by: Andrew Cooper <andrew.cooper3@citrix.com>
Acked-by: Jan Beulich <jbeulich@suse.com>
(qemu changes not included)
_______________________________________________
Xen-devel mailing list
Xen-devel@lists.xen.org
https://lists.xen.org/xen-devel
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2016-08-19 20:03 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-08-19 20:03 [xen-unstable-smoke test] 100564: regressions - FAIL osstest service owner
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.