flight 142323 linux-4.19 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142323/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-i386-xl-qemut-ws16-amd64 17 guest-stop fail like 142224
test-amd64-amd64-libvirt 13 migrat
On 06.10.19 07:19, Andy Smith wrote:
Hi,
I was writing a little utility to dump out domain CPU times and I
noticed that occasionally xenstat_domain_cpu_ns() returns an
erroneous huge value like 9223488034477457013.
Attached is a small test program that just requests every domain's
CPU time in a
flight 142352 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142352/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen f4049b2a9850c847b06ec6ad1cec1c7c2c303b94
baseline version:
xen 7a4e
flight 142327 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142327/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-debianhvm-i386-xsm 7 xen-boot fail REGR. vs. 141822
test-amd64-amd64-l
branch xen-unstable
xenbranch xen-unstable
job test-amd64-amd64-xl-qemuu-debianhvm-amd64-shadow
testid debian-hvm-install
Tree: linux git://xenbits.xen.org/linux-pvops.git
Tree: linuxfirmware git://xenbits.xen.org/osstest/linux-firmware.git
Tree: ovmf git://xenbits.xen.org/osstest/ovmf.git
Tree: q
flight 142335 linux-4.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142335/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 18 guest-localmigrate/x10 fail REGR. vs. 139698
Tests which did not s
On 04.10.19 18:09, George Dunlap wrote:
On 10/4/19 4:40 PM, Jürgen Groß wrote:
On 04.10.19 17:37, George Dunlap wrote:
On 10/4/19 4:03 PM, Jürgen Groß wrote:
On 04.10.19 16:56, George Dunlap wrote:
On 10/4/19 3:43 PM, Jürgen Groß wrote:
On 04.10.19 16:34, George Dunlap wrote:
On 10/4/19 3:2
flight 142345 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142345/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-qcow2 16 guest-start.2 fail REGR. vs. 142252
Tests which did not suc
flight 142338 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142338/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs.
140282
test-amd64-i38
On Wed, 11 Sep 2019, Ian Jackson wrote:
> Steven Haigh writes ("Re: [Xen-devel] [PATCH] read grubenv and set default
> from saved_entry or next_entry"):
>> Just wanted to give this a quick followup... Did this end up
>> progressing?
>
> Hi. I'm a tools maintainer and probably your best bet for a
flight 142333 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142333/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-freebsd10-i386 7 xen-boot fail REGR. vs. 133580
test-amd64-i386-xl-
flight 142363 linux-4.4 real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142363/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-pvshim 18 guest-localmigrate/x10 fail in 142335 REGR. vs.
139698
Tests which ar
flight 142359 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142359/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-libvirt-pair 22 guest-migrate/src_host/dst_host fail REGR.
vs. 141822
test-amd6
On 06.10.19 20:05, Jürgen Groß wrote:
On 04.10.19 18:09, George Dunlap wrote:
On 10/4/19 4:40 PM, Jürgen Groß wrote:
On 04.10.19 17:37, George Dunlap wrote:
On 10/4/19 4:03 PM, Jürgen Groß wrote:
On 04.10.19 16:56, George Dunlap wrote:
On 10/4/19 3:43 PM, Jürgen Groß wrote:
On 04.10.19 16:3
flight 142369 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/142369/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-amd64-xl-qemuu-ovmf-amd64 10 debian-hvm-install fail REGR. vs.
140282
test-amd64-i38
The credit scheduler is the only scheduler with tick_suspend and
tick_resume callbacks. Today those callbacks are invoked without being
guarded by the scheduler lock which is critical when at the same the
cpu those callbacks are active is being moved to or from a cpupool.
Crashes like the followin
On 04.10.19 17:17, Ian Jackson wrote:
libxl_get_required_shadow_memory has always been anomalous. libxl
ought to default these things itself. Recently, another analogous
setting, iommu_memkb, was introduced, along with another function
along the same lines.
This API is not very good. Fixing i
On 04.10.19 18:56, Julien Grall wrote:
xmalloc_array() may return NULL if there are memory. Rather than trying
to deference it directly, we should check the return value first.
Coverity-ID: 1381852
Signed-off-by: Julien Grall
Release-acked-by: Juergen Gross
Juergen
___
On 05.10.19 01:09, Stefano Stabellini wrote:
When reserved-memory regions are present in the host device tree, dom0
is started with multiple memory nodes. Each memory node should have a
unique name, but today they are all called "memory" leading to Linux
printing the following warning at boot:
On 04.10.19 18:42, Julien Grall wrote:
flask_assign_{, dt}device() may be used to check whether you can test if
a device is assigned. In this case, the domain will be NULL.
However, flask_iommu_resource_use_perm() will be called and may end up
to deference a NULL pointer. This can be prevented b
20 matches
Mail list logo
