[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [xen-unstable-smoke test] 96636: trouble: broken/pass
flight 96636 xen-unstable-smoke real [real] http://logs.test-lab.xenproject.org/osstest/logs/96636/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl 3 host-install(3) broken REGR. vs. 96626 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 4481335590f9b585b8dd168f0269e064e7ecbf43 baseline version: xen d0fd9ae54491328b10dee4003656c14b3bf3d3e9 Last test of basis 96626 2016-07-04 10:01:47 Z 0 days Testing same since 96636 2016-07-04 13:11:05 Z 0 days 1 attempts ------------------------------------------------------------ People who touched revisions under test: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx> Jan Beulich <jbeulich@xxxxxxxx> Kevin Tian <kevin.tian@xxxxxxxxx> Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Tamas K Lengyel <tamas@xxxxxxxxxxxxx> Wei Liu <wei.liu2@xxxxxxxxxx> jobs: build-amd64 pass build-armhf pass build-amd64-libvirt pass test-armhf-armhf-xl broken 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 broken-step test-armhf-armhf-xl host-install(3) Not pushing. ------------------------------------------------------------ commit 4481335590f9b585b8dd168f0269e064e7ecbf43 Author: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx> Date: Mon Jul 4 12:11:44 2016 +0200 vm-event: proper vCPU-paused checks at resume A VM_EVENT_FLAG_VCPU_PAUSED flag in a vm-event response should only be treated as informative that the toolstack user wants the vm-event subsystem to unpause the target vCPU, but not be relied upon to decide if the target vCPU is actually paused. That being said, this patch does the following: * Fixes (replaces) the old behavior in vm_event_resume, which relied on VM_EVENT_FLAG_VCPU_PAUSED to determine if the target vCPU is paused, by actually checking the vCPU vm-event pause-count. * ASSERTs that the vCPU is paused in vm_event_set_registers and vm_event_toggle_singlestep. * Ignores VM_EVENT_FLAG_DENY @ vm_event_register_write_resume if the target vCPU is not paused. Also adjusts comment in public/vm_event.h to reflect that. Signed-off-by: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx> Acked-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx> commit 2e0dd2f9a56c3fd01ec7557346580ab0b01ab7ac Author: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx> Date: Mon Jul 4 12:11:30 2016 +0200 vm-event: MAINTAINERS fix Fix vm-event section of MAINTAINERS file: add back files x86/hvm/monitor.c, asm-x86/hvm/monitor.h, x86/monitor.c, x86/vm_event.c and sort entries alphabetically. Culprits which got MAINTAINERS out-of-sync: c/s ca63cee: "monitor: Rename hvm/event to hvm/monitor": - added x86/hvm/monitor.c & asm-x86/hvm/monitor.h w/o MAINTAINERS update c/s ec89da2: "MAINTAINERS: update monitor/vm_event covered code": - (mistakenly?) removed both x86/monitor.c & x86/vm_event.c Signed-off-by: Corneliu ZUZU <czuzu@xxxxxxxxxxxxxxx> Acked-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx> commit b7d4cffbf2b17ec8a5c233f84395f4f85ad1a91d Author: Tamas K Lengyel <tamas@xxxxxxxxxxxxx> Date: Mon Jul 4 12:11:03 2016 +0200 x86/vmx: clean up TRAP_int3 handling Clean up the handling of TRAP_int3 VMEXITs to conform to the handling of TRAP_debug. Signed-off-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> commit 94db5dbb6c5f331dac35a8723a5d982ad17536d6 Author: Tamas K Lengyel <tamas@xxxxxxxxxxxxx> Date: Mon Jul 4 12:10:00 2016 +0200 x86/vm_event: add HVM debug exception vm_events Since in-guest debug exceptions are now unconditionally trapped to Xen, adding a hook for vm_event subscribers to tap into this new always-on guest event. We rename along the way hvm_event_breakpoint_type to hvm_event_type to better match the various events that can be passed with it. We also introduce the necessary monitor_op domctl's to enable subscribing to the events. This patch also provides monitor subscribers to int3 events proper access to the instruction length necessary for accurate event-reinjection. Without this subscribers manually have to evaluate if the int3 instruction has any prefix attached which would change the instruction length. Signed-off-by: Tamas K Lengyel <tamas@xxxxxxxxxxxxx> Acked-by: Razvan Cojocaru <rcojocaru@xxxxxxxxxxxxxxx> Acked-by: Jan Beulich <jbeulich@xxxxxxxx> Acked-by: Kevin Tian <kevin.tian@xxxxxxxxx> Acked-by: Wei Liu <wei.liu2@xxxxxxxxxx> (qemu changes not included) _______________________________________________ osstest-output mailing list osstest-output@xxxxxxxxxxxxxxxxxxxx http://lists.xenproject.org/cgi-bin/mailman/listinfo/osstest-output
|
Lists.xenproject.org is hosted with RackSpace, monitoring our |