|
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-4.4-testing baseline-only test] 68083: tolerable FAIL
This run is configured for baseline tests only. flight 68083 xen-4.4-testing real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/68083/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-xl 19 guest-start/debian.repeat fail baseline untested test-amd64-amd64-xl-credit2 19 guest-start/debian.repeat fail baseline untested test-amd64-i386-xl-qemuu-ovmf-amd64 13 guest-localmigrate fail baseline untested test-amd64-amd64-xl-qemut-win7-amd64 16 guest-stop fail baseline untested test-amd64-i386-xl-qemut-win7-amd64 16 guest-stop fail baseline untested test-amd64-amd64-xl-qemuu-win7-amd64 16 guest-stop fail baseline untested test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 15 guest-localmigrate/x10 fail baseline untested test-amd64-i386-xend-qemut-winxpsp3 9 windows-install fail baseline untested Tests which did not succeed, but are not blocking: test-amd64-amd64-rumprun-amd64 1 build-check(1) blocked n/a test-amd64-i386-rumprun-i386 1 build-check(1) blocked n/a build-amd64-rumprun 6 xen-build fail never pass build-i386-rumprun 6 xen-build fail never pass test-xtf-amd64-amd64-2 10 xtf-fep fail never pass test-armhf-armhf-xl-vhd 9 debian-di-install fail never pass test-armhf-armhf-libvirt-qcow2 9 debian-di-install fail never pass test-xtf-amd64-amd64-2 51 xtf/test-pv32pae-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-2 52 xtf/test-pv32pae-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-5 10 xtf-fep fail never pass test-xtf-amd64-amd64-2 59 xtf/test-pv64-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-2 60 xtf/test-pv64-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-1 10 xtf-fep fail never pass test-armhf-armhf-libvirt-raw 9 debian-di-install fail never pass test-xtf-amd64-amd64-1 20 xtf/test-hvm32-invlpg~shadow fail never pass test-xtf-amd64-amd64-1 29 xtf/test-hvm32pae-invlpg~shadow fail never pass test-xtf-amd64-amd64-5 51 xtf/test-pv32pae-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-5 52 xtf/test-pv32pae-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-5 59 xtf/test-pv64-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-5 60 xtf/test-pv64-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-1 40 xtf/test-hvm64-invlpg~shadow fail never pass test-amd64-i386-libvirt 12 migrate-support-check fail never pass test-xtf-amd64-amd64-1 51 xtf/test-pv32pae-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-1 52 xtf/test-pv32pae-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-1 59 xtf/test-pv64-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-1 60 xtf/test-pv64-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-4 10 xtf-fep fail never pass test-xtf-amd64-amd64-3 10 xtf-fep fail never pass test-xtf-amd64-amd64-4 20 xtf/test-hvm32-invlpg~shadow fail never pass test-xtf-amd64-amd64-4 29 xtf/test-hvm32pae-invlpg~shadow fail never pass test-xtf-amd64-amd64-4 40 xtf/test-hvm64-invlpg~shadow fail never pass test-xtf-amd64-amd64-4 51 xtf/test-pv32pae-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-4 52 xtf/test-pv32pae-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-3 51 xtf/test-pv32pae-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-4 59 xtf/test-pv64-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-3 52 xtf/test-pv32pae-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-4 60 xtf/test-pv64-pv-iopl~vmassist fail never pass test-xtf-amd64-amd64-3 59 xtf/test-pv64-pv-iopl~hypercall fail never pass test-xtf-amd64-amd64-3 60 xtf/test-pv64-pv-iopl~vmassist fail never pass test-amd64-amd64-libvirt 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 12 migrate-support-check fail never pass test-armhf-armhf-xl-credit2 13 saverestore-support-check fail never pass test-armhf-armhf-xl-midway 12 migrate-support-check fail never pass test-armhf-armhf-xl-midway 13 saverestore-support-check fail never pass test-armhf-armhf-xl-multivcpu 12 migrate-support-check fail never pass test-armhf-armhf-xl-multivcpu 13 saverestore-support-check fail never pass test-armhf-armhf-libvirt 11 guest-start fail never pass test-armhf-armhf-xl 12 migrate-support-check fail never pass test-armhf-armhf-xl 13 saverestore-support-check fail never pass test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-qemuu-nested-amd 16 debian-hvm-install/l1/l2 fail never pass test-amd64-amd64-libvirt-vhd 11 migrate-support-check fail never pass test-amd64-i386-xl-qemuu-win7-amd64 16 guest-stop fail never pass version targeted for testing: xen 6639a202f285ace4adf57453ade066bd4b4298e0 baseline version: xen 488b7d28abe3f79f2d2d17ee25c7948a58d6970b Last test of basis 67805 2016-10-05 17:46:10 Z 48 days Testing same since 68083 2016-11-23 06:51:33 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> jobs: build-amd64-xend pass build-i386-xend pass build-amd64-xtf pass build-amd64 pass build-armhf pass build-i386 pass build-amd64-libvirt pass build-armhf-libvirt pass build-i386-libvirt pass build-amd64-pvops pass build-armhf-pvops pass build-i386-pvops pass build-amd64-rumprun fail build-i386-rumprun fail test-xtf-amd64-amd64-1 pass test-xtf-amd64-amd64-2 pass test-xtf-amd64-amd64-3 pass test-xtf-amd64-amd64-4 pass test-xtf-amd64-amd64-5 pass test-amd64-amd64-xl fail test-armhf-armhf-xl pass test-amd64-i386-xl pass test-amd64-amd64-qemuu-nested-amd fail test-amd64-i386-qemut-rhel6hvm-amd pass test-amd64-i386-qemuu-rhel6hvm-amd pass test-amd64-amd64-xl-qemut-debianhvm-amd64 pass test-amd64-i386-xl-qemut-debianhvm-amd64 pass test-amd64-amd64-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-xl-qemuu-debianhvm-amd64 pass test-amd64-i386-freebsd10-amd64 pass test-amd64-amd64-xl-qemuu-ovmf-amd64 pass test-amd64-i386-xl-qemuu-ovmf-amd64 fail test-amd64-amd64-rumprun-amd64 blocked test-amd64-amd64-xl-qemut-win7-amd64 fail test-amd64-i386-xl-qemut-win7-amd64 fail test-amd64-amd64-xl-qemuu-win7-amd64 fail test-amd64-i386-xl-qemuu-win7-amd64 fail test-amd64-amd64-xl-credit2 fail test-armhf-armhf-xl-credit2 pass test-amd64-i386-freebsd10-i386 pass test-amd64-i386-rumprun-i386 blocked test-amd64-amd64-qemuu-nested-intel fail test-amd64-i386-qemut-rhel6hvm-intel pass test-amd64-i386-qemuu-rhel6hvm-intel pass test-amd64-amd64-libvirt pass test-armhf-armhf-libvirt fail test-amd64-i386-libvirt pass test-armhf-armhf-xl-midway pass test-amd64-amd64-xl-multivcpu pass test-armhf-armhf-xl-multivcpu pass test-amd64-amd64-pair pass test-amd64-i386-pair pass test-amd64-amd64-libvirt-pair pass test-amd64-i386-libvirt-pair pass test-amd64-amd64-pv pass test-amd64-i386-pv pass test-amd64-amd64-amd64-pvgrub pass test-amd64-amd64-i386-pvgrub pass test-amd64-amd64-pygrub pass test-armhf-armhf-libvirt-qcow2 fail test-amd64-amd64-xl-qcow2 pass test-armhf-armhf-libvirt-raw fail test-amd64-i386-xl-raw pass test-amd64-i386-xl-qemut-winxpsp3-vcpus1 pass test-amd64-i386-xl-qemuu-winxpsp3-vcpus1 fail test-amd64-amd64-libvirt-vhd pass test-armhf-armhf-xl-vhd fail test-amd64-i386-xend-qemut-winxpsp3 fail test-amd64-amd64-xl-qemut-winxpsp3 pass test-amd64-amd64-xl-qemuu-winxpsp3 pass ------------------------------------------------------------ sg-report-flight on osstest.xs.citrite.net logs: /home/osstest/logs images: /home/osstest/images Logs, config files, etc. are available at http://osstest.xs.citrite.net/~osstest/testlogs/logs Test harness code can be found at http://xenbits.xensource.com/gitweb?p=osstest.git;a=summary Push not applicable. ------------------------------------------------------------ commit 6639a202f285ace4adf57453ade066bd4b4298e0 Author: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Date: Tue Nov 22 14:35:31 2016 +0100 pygrub: Properly quote results, when returning them to the caller: * When the caller wants sexpr output, use `repr()' This is what Xend expects. The returned S-expressions are now escaped and quoted by Python, generally using '...'. Previously kernel and ramdisk were unquoted and args was quoted with "..." but without proper escaping. This change may break toolstacks which do not properly dequote the returned S-expressions. * When the caller wants "simple" output, crash if the delimiter is contained in the returned value. With --output-format=simple it does not seem like this could ever happen, because the bootloader config parsers all take line-based input from the various bootloader config files. With --output-format=simple0, this can happen if the bootloader config file contains nul bytes. This is CVE-2016-9379 and CVE-2016-9380 / XSA-198. Signed-off-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Tested-by: Ian Jackson <Ian.Jackson@xxxxxxxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 27e14d346ed6ff1c3a3cfc479507e62d133e92a9 master date: 2016-11-22 13:52:09 +0100 commit 14fa85aab363fdd096f578cef0d44f190082dabb Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Nov 22 14:34:56 2016 +0100 x86emul: fix huge bit offset handling We must never chop off the high 32 bits. This is CVE-2016-9383 / XSA-195. Reported-by: George Dunlap <george.dunlap@xxxxxxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 1c6c2d60d205f71ede0fbbd9047e459112f576db master date: 2016-11-22 13:49:06 +0100 commit 1827d5252cf9764d4d5774059905aa21a8c69c80 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Nov 22 14:34:25 2016 +0100 x86/PV: writes of %fs and %gs base MSRs require canonical addresses Commit c42494acb2 ("x86: fix FS/GS base handling when using the fsgsbase feature") replaced the use of wrmsr_safe() on these paths without recognizing that wr{f,g}sbase() use just wrmsrl() and that the WR{F,G}SBASE instructions also raise #GP for non-canonical input. Similarly arch_set_info_guest() needs to prevent non-canonical addresses from getting stored into state later to be loaded by context switch code. For consistency also check stack pointers and LDT base. DR0..3, otoh, already get properly checked in set_debugreg() (albeit we discard the error there). The SHADOW_GS_BASE check isn't strictly necessary, but I think we better avoid trying the WRMSR if we know it's going to fail. This is CVE-2016-9385 / XSA-193. Reported-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: f3fa3abf3e61fb1f25ce721e14ac324dda67311f master date: 2016-11-22 13:46:28 +0100 commit e8a46a210442acc7897d02857d4b77c750b02041 Author: Jan Beulich <jbeulich@xxxxxxxx> Date: Tue Nov 22 14:33:54 2016 +0100 x86/HVM: don't load LDTR with VM86 mode attrs during task switch Just like TR, LDTR is purely a protected mode facility and hence needs to be loaded accordingly. Also move its loading to where it architecurally belongs. This is CVE-2016-9382 / XSA-192. Signed-off-by: Jan Beulich <jbeulich@xxxxxxxx> Reviewed-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Tested-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> master commit: 93aa42b85ae0084ba7b749d0e990c94fbf0c17e3 master date: 2016-11-22 13:45:44 +0100 commit ed77368cc90c9972a747c82bec7c22703bc23184 Author: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Date: Tue Nov 22 14:32:39 2016 +0100 x86/hvm: Fix the handling of non-present segments In 32bit, the data segments may be NULL to indicate that the segment is ineligible for use. In both 32bit and 64bit, the LDT selector may be NULL to indicate that the entire LDT is ineligible for use. However, nothing in Xen actually checks for this condition when performing other segmentation checks. (Note however that limit and writeability checks are correctly performed). Neither Intel nor AMD specify the exact behaviour of loading a NULL segment. Experimentally, AMD zeroes all attributes but leaves the base and limit unmodified. Intel zeroes the base, sets the limit to 0xfffffff and resets the attributes to just .G and .D/B. The use of the segment information in the VMCB/VMCS is equivalent to a native pipeline interacting with the segment cache. The present bit can therefore have a subtly different meaning, and it is now cooked to uniformly indicate whether the segment is usable or not. GDTR and IDTR don't have access rights like the other segments, but for consistency, they are treated as being present so no special casing is needed elsewhere in the segmentation logic. AMD hardware does not consider the present bit for %cs and %tr, and will function as if they were present. They are therefore unconditionally set to present when reading information from the VMCB, to maintain the new meaning of usability. Intel hardware has a separate unusable bit in the VMCS segment attributes. This bit is inverted and stored in the present field, so the hvm code can work with architecturally-common state. This is CVE-2016-9386 / XSA-191. Signed-off-by: Andrew Cooper <andrew.cooper3@xxxxxxxxxx> Reviewed-by: Jan Beulich <jbeulich@xxxxxxxx> master commit: 04beafa8e6c66f5cd814c00e2d2b51cfbc41cb8a master date: 2016-11-22 13:44:50 +0100 ======================================== _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx https://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
 |
Lists.xenproject.org is hosted with RackSpace, monitoring our |