[Xen-devel] [qemu-mainline bisection] complete test-amd64-amd64-qemuu-nested-intel

2016-06-04 Thread osstest service owner
branch xen-unstable xenbranch xen-unstable job test-amd64-amd64-qemuu-nested-intel testid debian-hvm-install/l1/l2 Tree: linux git://xenbits.xen.org/linux-pvops.git Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git Tree: qemu git://xenbits.xen.org/qemu-xen-traditional.git Tree:

[Xen-devel] [ovmf test] 95270: regressions - FAIL

2016-06-04 Thread osstest service owner
flight 95270 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/95270/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR. vs. 94748 test-amd64-amd64-

[Xen-devel] [xen-unstable test] 95261: trouble: blocked/broken/fail/pass

2016-06-04 Thread osstest service owner
flight 95261 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/95261/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-libvirt-xsm 3 host-install(3) broken REGR. vs. 95242

[Xen-devel] [qemu-upstream-4.3-testing test] 95273: trouble: blocked/broken

2016-06-04 Thread osstest service owner
flight 95273 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/95273/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 3 host-install(3) broken REG

[Xen-devel] [qemu-mainline test] 95258: regressions - FAIL

2016-06-04 Thread osstest service owner
flight 95258 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/95258/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-qemuu-nested-intel 16 debian-hvm-install/l1/l2 fail REGR. vs. 94856 test-amd64-a

[Xen-devel] [qemu-upstream-4.3-testing test] 95264: trouble: blocked/broken

2016-06-04 Thread osstest service owner
flight 95264 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/95264/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 3 host-install(3) broken REG

[Xen-devel] [ovmf test] 95248: regressions - FAIL

2016-06-04 Thread osstest service owner
flight 95248 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/95248/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ovmf-amd64 17 guest-start/debianhvm.repeat fail REGR. vs. 94748 test-amd64-amd64-

Re: [Xen-devel] [PATCH v5 5/9] monitor: ARM SMC events

2016-06-04 Thread Tamas K Lengyel
On Sat, Jun 4, 2016 at 3:03 AM, Edgar E. Iglesias wrote: > On Fri, Jun 03, 2016 at 09:34:20AM -0600, Tamas K Lengyel wrote: >> On Fri, Jun 3, 2016 at 9:27 AM, Tamas K Lengyel wrote: >> >>> > Furthermore, I think the vm_event app should only received SMCs whose >> >>> condition has succeeded, bec

[Xen-devel] [xen-4.5-testing test] 95250: regressions - FAIL

2016-06-04 Thread osstest service owner
flight 95250 xen-4.5-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/95250/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-win7-amd64 15 guest-localmigrate/x10 fail REGR. vs. 94855 Tests which

[Xen-devel] [libvirt test] 95255: tolerable FAIL - PUSHED

2016-06-04 Thread osstest service owner
flight 95255 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/95255/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt-xsm 12 migrate-support-checkfail never pass test-armhf-armhf-libvirt-xsm 14 guest-saver

Re: [Xen-devel] Issues with PCI-Passtrough (VT-d) in HVM with Xen 4.6

2016-06-04 Thread Jürgen Walter
On 3 Jun 2016, at 15:26, Jan Beulich wrote: I'll see to put together a patch for the recognizable problem, but I'm still unclear about your actual one. regarding the actual one: while it is still not working, I managed to dig deeper and found a few observations background: there is a drive

[Xen-devel] [qemu-upstream-4.3-testing test] 95257: trouble: blocked/broken

2016-06-04 Thread osstest service owner
flight 95257 qemu-upstream-4.3-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/95257/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 3 host-install(3) broken REG

Re: [Xen-devel] Issues with PCI-Passtrough (VT-d) in HVM with Xen 4.6

2016-06-04 Thread Jürgen Walter
Hi Jan, On 3 Jun 2016, at 16:20, Jan Beulich wrote: On 03.06.16 at 15:26, wrote: On 03.06.16 at 14:02, wrote: or is this just some method the overwrite all registers with "" first and then set the actual value? [914572] xbk: 06:00.0: write request 4 bytes at 0x10 =

[Xen-devel] [xen-unstable test] 95242: tolerable FAIL - PUSHED

2016-06-04 Thread osstest service owner
flight 95242 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/95242/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): build-amd64-rumpuserxen 6 xen-buildfail like 95222 build-i386-rumpuserxen

Re: [Xen-devel] handle virtualization exception

2016-06-04 Thread Big Strong
To handle this system reserved exception, should I modify the linux kernel instead of using loadable kernel module? Is there any suggestions? 2016-06-01 11:08 GMT+08:00 Big Strong : > Virtualization exception is a fault exception caused by specific type of > EPT violations. The vector is 20, whic

Re: [Xen-devel] [PATCH v5 5/9] monitor: ARM SMC events

2016-06-04 Thread Edgar E. Iglesias
On Fri, Jun 03, 2016 at 09:34:20AM -0600, Tamas K Lengyel wrote: > On Fri, Jun 3, 2016 at 9:27 AM, Tamas K Lengyel wrote: > >>> > Furthermore, I think the vm_event app should only received SMCs whose > >>> condition has succeeded, because they will be actual SMC. The others > >>> should just be i