[linux-linus test] 167560: tolerable FAIL - PUSHED

2021-12-29 Thread osstest service owner
flight 167560 linux-linus real [real] flight 167567 linux-linus real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/167560/ http://logs.test-lab.xenproject.org/osstest/logs/167567/ Failures :-/ but no regressions. Tests which are failing intermittently (not blocking): test-armhf-

[linux-5.4 test] 167558: regressions - FAIL

2021-12-29 Thread osstest service owner
flight 167558 linux-5.4 real [real] flight 167561 linux-5.4 real-retest [real] http://logs.test-lab.xenproject.org/osstest/logs/167558/ http://logs.test-lab.xenproject.org/osstest/logs/167561/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: t

Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0

2021-12-29 Thread Roger Pau Monné
On Wed, Dec 29, 2021 at 11:27:50AM +0100, Roger Pau Monné wrote: > On Wed, Dec 29, 2021 at 05:13:00PM +0800, G.R. wrote: > > > > > > I think this is hitting a KASSERT, could you paste the text printed as > > > part of the panic (not just he backtrace)? > > > > > > Sorry this is taking a bit of time

[linux-linus test] 167557: regressions - trouble: broken/fail/pass

2021-12-29 Thread osstest service owner
flight 167557 linux-linus real [real] http://logs.test-lab.xenproject.org/osstest/logs/167557/ Regressions :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-xl broken test-armhf-armhf-xl-arndale

Re: [PATCH 5/5] tools/xl: Fix potential deallocation bug

2021-12-29 Thread Luca Fancellu
> On 10 Dec 2020, at 23:09, Elliott Mitchell wrote: > > There is potential for the info and info_free variable's purposes to > diverge. If info was overwritten with a distinct value, yet info_free > still needed deallocation a bug would occur on this line. Preemptively > address this issue (

Re: [PATCH 4/5] tools/xl: Merge down debug/dry-run section of create_domain()

2021-12-29 Thread Luca Fancellu
> On 18 Dec 2020, at 01:42, Elliott Mitchell wrote: > > create_domain()'s use of printf_info_sexp() could be merged down to a > single dump_by_config(), do so. This results in an extra JSON dictionary > in output, but I doubt that is an issue for dry-run or debugging output. > Don’t know if

Re: [PATCH 3/5] tools/xl: Rename printf_info()/list_domains_details() to dump_by_...()

2021-12-29 Thread Luca Fancellu
> On 18 Dec 2020, at 01:42, Elliott Mitchell wrote: > > printf_info()/list_domains_details() had been serving fairly similar > purposes. Increase their consistency (add file-handle and output_format > arguments to list_domains_details(), reorder arguments) and then rename > to better reflect

Re: [PATCH 2/5] tools/xl: Mark libxl_domain_config * arg of printf_info_*() const

2021-12-29 Thread Luca Fancellu
> On 18 Dec 2020, at 21:32, Elliott Mitchell wrote: > > With libxl having gotten a lot more constant, now printf_info_sexp() and > printf_info_one_json() can add consts. May not be particularly > important, but it is best to mark things constant when they are known to > be so. Looks ok to me

Re: [PATCH 1/5] tools/libxl: Mark pointer args of many functions constant

2021-12-29 Thread Luca Fancellu
> On 18 Dec 2020, at 21:37, Elliott Mitchell wrote: > > Anything *_is_empty(), *_is_default(), or *_gen_json() is going to be > examining the pointed to thing, not modifying it. This potentially > results in higher-performance output. This also allows spreading > constants further, allowing

[ovmf test] 167559: all pass - PUSHED

2021-12-29 Thread osstest service owner
flight 167559 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/167559/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf c095122d4b5f3152417cd97dabecfe31cc3b6508 baseline version: ovmf 7935be0fbd8f47266e597

[xen-unstable test] 167554: trouble: broken/fail/pass

2021-12-29 Thread osstest service owner
flight 167554 xen-unstable real [real] http://logs.test-lab.xenproject.org/osstest/logs/167554/ Failures and problems with tests :-( Tests which did not succeed and are blocking, including tests which could not be run: test-armhf-armhf-libvirt broken test-armhf-armhf-lib

[libvirt test] 167556: regressions - FAIL

2021-12-29 Thread osstest service owner
flight 167556 libvirt real [real] http://logs.test-lab.xenproject.org/osstest/logs/167556/ 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

Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0

2021-12-29 Thread Roger Pau Monné
On Wed, Dec 29, 2021 at 05:13:00PM +0800, G.R. wrote: > > > > I think this is hitting a KASSERT, could you paste the text printed as > > part of the panic (not just he backtrace)? > > > > Sorry this is taking a bit of time to solve. > > > > Thanks! > > > Sorry that I didn't make it clear in the fir

Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0

2021-12-29 Thread G.R.
> > I think this is hitting a KASSERT, could you paste the text printed as > part of the panic (not just he backtrace)? > > Sorry this is taking a bit of time to solve. > > Thanks! > Sorry that I didn't make it clear in the first place. It is the same cross boundary assertion. Also sorry about the

[ovmf test] 167555: all pass - PUSHED

2021-12-29 Thread osstest service owner
flight 167555 ovmf real [real] http://logs.test-lab.xenproject.org/osstest/logs/167555/ Perfect :-) All tests in this flight passed as required version targeted for testing: ovmf 7935be0fbd8f47266e5972f4cba1a1e58505061a baseline version: ovmf e910f076ad02c80bb69ce

Re: Possible bug? DOM-U network stopped working after fatal error reported in DOM0

2021-12-29 Thread Roger Pau Monné
Adding xen-devel back. On Wed, Dec 29, 2021 at 01:44:18AM +0800, G.R. wrote: > On Tue, Dec 28, 2021 at 3:05 AM Roger Pau Monné wrote: > > > > On Sun, Dec 26, 2021 at 02:06:55AM +0800, G.R. wrote: > > > > > Thanks. I've raised this on freensd-net for advice [0]. IMO netfront > > > > > shouldn't re