[Xen-devel] [libvirt bisection] complete build-i386-libvirt

branch xen-unstable xenbranch xen-unstable job build-i386-libvirt testid libvirt-build Tree: libvirt git://libvirt.org/libvirt.git Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git Tree: qemu git://xenbits.xen.org/qemu-xe

[Xen-devel] Explicit cpuid may be incompatible with vixen

We had an experience where vixen would crash with (XEN) (XEN) (XEN) Panic on CPU 0: (XEN) GENERAL PROTECTION FAULT (XEN) [error_code=] (XEN) (XEN) (XEN) Reboot in five seconds... when cpuid was set to: cpuid =

[Xen-devel] [qemu-mainline test] 117930: tolerable FAIL - PUSHED

flight 117930 qemu-mainline real [real] http://logs.test-lab.xenproject.org/osstest/logs/117930/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-armhf-armhf-libvirt 14 saverestore-support-checkfail like 117833 test-amd64-amd64-xl-qemuu-win7-amd6

[Xen-devel] [qemu-upstream-4.10-testing test] 117922: regressions - FAIL

flight 117922 qemu-upstream-4.10-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/117922/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64 6 xen-buildfail REGR. vs. 117345 buil

[Xen-devel] [linux-next test] 117921: regressions - FAIL

flight 117921 linux-next real [real] http://logs.test-lab.xenproject.org/osstest/logs/117921/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemut-stubdom-debianhvm-amd64-xsm 7 xen-boot fail REGR. vs. 117788 test-amd64-i

[Xen-devel] [libvirt bisection] complete build-amd64-libvirt

branch xen-unstable xenbranch xen-unstable job build-amd64-libvirt testid libvirt-build Tree: libvirt git://libvirt.org/libvirt.git Tree: libvirt_gnulib git://git.sv.gnu.org/gnulib.git Tree: libvirt_keycodemapdb https://gitlab.com/keycodemap/keycodemapdb.git Tree: qemu git://xenbits.xen.org/qemu-x

[Xen-devel] [seabios test] 117935: regressions - FAIL

flight 117935 seabios real [real] http://logs.test-lab.xenproject.org/osstest/logs/117935/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-amd64-xl-qemuu-ws16-amd64 17 guest-stop fail REGR. vs. 115539 Tests which did not suc

[Xen-devel] [xen-unstable test] 117920: regressions - FAIL

flight 117920 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/117920/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-xsm 6 xen-buildfail REGR. vs. 117311 Tests which did no

Re: [Xen-devel] [PATCH] x86: Meltdown band-aid against malicious 64-bit PV guests

On 12/01/18 10:19, Jan Beulich wrote: > This is a very simplistic change limiting the amount of memory a running > 64-bit PV guest has mapped (and hence available for attacking): Only the > mappings of stack, IDT, and TSS are being cloned from the direct map > into per-CPU page tables. Guest contro

[Xen-devel] [linux-linus test] 117909: tolerable FAIL - PUSHED

flight 117909 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/117909/ Failures :-/ but no regressions. Tests which did not succeed, but are not blocking: test-amd64-amd64-xl-qemut-win7-amd64 17 guest-stopfail like 117788 test-armhf-armhf-libvirt 14 saver

[Xen-devel] [libvirt test] 117889: regressions - FAIL

flight 117889 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/117889/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: build-amd64-libvirt 6 libvirt-buildfail REGR. vs. 117772 build-i386-libvirt

[Xen-devel] [xen-4.7-testing test] 117873: regressions - FAIL

flight 117873 xen-4.7-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/117873/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-amd64-i386-xl-qemuu-ws16-amd64 15 guest-saverestore.2 fail REGR. vs. 117705 Tests which

Re: [Xen-devel] Clarification regarding Meltdown and 64-bit PV guests

On 01/13/2018 11:08 AM, Andy Smith wrote: > Hi Hans, > > On Sat, Jan 13, 2018 at 10:43:03AM +0100, Hans van Kranenburg wrote: >> By injecting a copy of a hypervisor between the outer level hypervisor >> (that's called L0 right?) (in HVM or PVH mode) and the guest, having it >> just run 1 guest, th

[Xen-devel] [distros-debian-stretch test] 74354: trouble: blocked/broken

flight 74354 distros-debian-stretch real [real] http://osstest.xs.citrite.net/~osstest/testlogs/logs/74354/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: build-armhf-pvopsbroken build-i3

Re: [Xen-devel] Clarification regarding Meltdown and 64-bit PV guests

Hi Hans, On Sat, Jan 13, 2018 at 10:43:03AM +0100, Hans van Kranenburg wrote: > By injecting a copy of a hypervisor between the outer level hypervisor > (that's called L0 right?) (in HVM or PVH mode) and the guest, having it > just run 1 guest, that (64-bit PV) guest cannot attack its own kernel,

Re: [Xen-devel] Clarification regarding Meltdown and 64-bit PV guests

On 01/13/2018 07:42 AM, Andy Smith wrote: > Hi, > > In > : > > "On Intel processors, only 64-bit PV mode guests can attack Xen > using Variant 3. [...] 64bit PV domU userspace can attack the hypervisor -> read "host

[Xen-devel] [xen-4.10-testing test] 117870: tolerable FAIL - PUSHED

flight 117870 xen-4.10-testing real [real] http://logs.test-lab.xenproject.org/osstest/logs/117870/ Failures :-/ but no regressions. Regressions which are regarded as allowable (not blocking): test-amd64-amd64-rumprun-amd64 17 rumprun-demo-xenstorels/xenstorels.repeat fail REGR. vs. 117741 Tes