flight 117041 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117041/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117046 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117046/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117050 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117050/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
coverity-amd64 broken
coverity-am
flight 117013 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117013/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-win10-i386 broken
test-amd64-i386-xl
At 14:38 + on 08 Dec (1512743913), Julien Grall wrote:
> On 08/12/17 08:03, Tim Deegan wrote:
> > +1 for avoiding the full majesty of PoD if you don't need it.
> >
> > It should be possible to do something like the misconfigured-entry bit
> > trick by _allocating_ the memory up-front and build
Hi,
I just upgraded from 4.4 to 4.8 (going from Debian jessie to stretch) and hit a
problem with xentop. On 4.8 xentop shows only zeroes for network traffic.
I did some debugging and the problem appears to be that in
xenstat_collect_networks (in libxenstat_linux.c) the following conditional is
flight 117047 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117047/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117048 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117048/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-prev
flight 117049 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117049/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117045 seabios real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117045/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64-xsm broken
build-i386
flight 117037 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117037/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
test-arm64-arm
flight 117051 linux-4.1 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117051/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117053 linux-3.18 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117053/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117054 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117054/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-prev
Hello all,
I'm trying to set up an android guest on XU4 board. I'm stuck at mounting
the file system for the guest.
Do we need to manually mount/copy the contents of various
images(system.img,userdata.img etc.) and then create a file system image?
Is there a way where we can specify the paths to t
Hello, I'm working on the 'credit scheduler' of Xen.
And I need to compare CPU cache misses between original Xen and my patching
version.
But I failed all attempt even if I have tried many methods by googling.
When I typed 'perf list' with my 'perf' compiled by source code in the
current kernel sou
flight 117055 linux-4.9 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117055/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
flight 117052 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/117052/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-i386
>>> On 08.12.17 at 14:22, wrote:
> On 08/12/17 12:17, Jan Beulich wrote:
>> Unconditionally reporting a value seen on the P4 or older invokes
>> functionality like io_apic_get_unique_id() on 32-bit builds, resulting
>> in a panic() with sufficiently many CPUs and/or IO-APICs. Doing what
>> that fu
19 matches
Mail list logo
