flight 156805 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156805/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm broken
test-amd64-amd64-libvirt-vhd 19 guest-st
flight 156811 xen-unstable-coverity real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156811/
Perfect :-)
All tests in this flight passed as required
version targeted for testing:
xen 5505f5f8e7e805365cfe70b6a4af6115940bb749
baseline version:
xen 3059
flight 156808 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156808/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
flight 156807 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156807/
Failures :-/ but no regressions.
Tests which did not succeed, but are not blocking:
test-amd64-amd64-xl-qemuu-ws16-amd64 19 guest-stopfail like 156799
test-amd64-amd64-xl-qemuu-win7-amd64
On Sat, 14 Nov 2020 at 12:37, Nico Huber wrote:
> > (I think
> > newer spec versions should not change anything in first 5 bf_log
> members;
> > this way older log parsers will be able to traverse/copy all logs
> regardless
> > of version used in one log or another),
>
> Good point, w
flight 156809 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156809/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-qemut-rhel6hvm-intel 7 xen-install fail REGR. vs. 152332
test-amd64-i386-xl-
Hello,
I spent some more time debugging NetBSD as a PVH dom0 on Xen,
With Roger's patch to avoid a Xen panic, the NetBSD kernel stalls
configuring devices. At first I though it was an issue with hardware
interrupts, but it more likely is an issue with Xen timer events.
Specifically: virtual CPU 0 s
On Sun, Nov 15, 2020 at 06:49:38PM +0100, Manuel Bouyer wrote:
> Hello,
> I spent some more time debugging NetBSD as a PVH dom0 on Xen,
> With Roger's patch to avoid a Xen panic, the NetBSD kernel stalls
> configuring devices. At first I though it was an issue with hardware
> interrupts, but it mor
On Sun, Nov 15, 2020 at 06:49:38PM +0100, Manuel Bouyer wrote:
> Hello,
> I spent some more time debugging NetBSD as a PVH dom0 on Xen,
> With Roger's patch to avoid a Xen panic, the NetBSD kernel stalls
> configuring devices. At first I though it was an issue with hardware
> interrupts, but it mor
On Sun, Nov 15, 2020 at 07:24:16PM +0100, Roger Pau Monné wrote:
> On Sun, Nov 15, 2020 at 06:49:38PM +0100, Manuel Bouyer wrote:
> > Hello,
> > I spent some more time debugging NetBSD as a PVH dom0 on Xen,
> > With Roger's patch to avoid a Xen panic, the NetBSD kernel stalls
> > configuring device
flight 156810 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156810/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-arm64-arm64-libvirt-xsm broken in 156805
test-amd64-amd64-libvirt-vhd
flight 156812 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156812/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
test-amd64-i386-xl-qemuu-ws16-amd64 7 xen-install fail REGR. vs. 152332
test-amd64-i386-qem
flight 156813 qemu-mainline real [real]
flight 156816 qemu-mainline real-retest [real]
http://logs.test-lab.xenproject.org/osstest/logs/156813/
http://logs.test-lab.xenproject.org/osstest/logs/156816/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be
>>> Daniel Kiper schrieb am 14.11.2020 um 00:52 in
Nachricht <20201113235242.k6fzlwmwm2xqh...@tomti.i.net-space.pl>:
...
> The members of struct bf_log_msg:
> ‑ size: total size of bf_log_msg struct,
> ‑ ts_nsec: timestamp expressed in nanoseconds starting from 0,
Who or what defines t == 0?
On the affected Cortex-A76/Neoverse-N1 cores (r0p0 to r3p0),
if a virtual address for a cacheable mapping of a location is being
accessed by a core while another core is remapping the virtual
address to a new physical page using the recommended break-before-make
sequence, then under very rare circu
flight 156817 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/156817/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-armhf-libvirt 6 libvirt-buildfail REGR. vs. 151777
build-amd64-libvirt
On 13.11.20 18:23, Edwin Torok wrote:
CAUTION: This email originated from outside of the organization. Do not click
links or open attachments unless you can confirm the sender and know the
content is safe.
On Fri, 2020-11-13 at 17:13 +, Andrew Cooper wrote:
On 13/11/2020 16:56, Bjoern
17 matches
Mail list logo
