flight 162955 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162955/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-arm64-xs
flight 162938 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162938/
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-pvops
flight 162950 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162950/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-arm64-xs
flight 162936 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162936/
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-pvops
flight 162946 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162946/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-arm64-xs
On Fri, Jun 18, 2021 at 07:31:46PM +, George Dunlap wrote:
>
>
> > On Jun 18, 2021, at 7:28 PM, George Dunlap wrote:
> >
> >
> >
> >> On May 24, 2021, at 9:36 PM, Nick Rosbrook wrote:
> >>
> >> Add a helper function to wait for domain death events, and then write
> >> the events to a pr
On 21/06/2021 18:54, Rasmus Villemoes wrote:
On 18/06/2021 03.06, Sander Eikelenboom wrote:
On 17/06/2021 21:39, Sander Eikelenboom wrote:
OK, done some experimentation and it seems with 256M assigned to the VM
it was almost at the edge of OOM with the 5.12 kernel as well in the
config I am
On Mon, Jun 21, 2021 at 10:59:20AM -0700, Stefano Stabellini wrote:
> Just as a clarification: I was referring to the zeroing of "mem" in
> swiotlb_late_init_with_tbl and swiotlb_init_with_tbl. While it looks
> like Tom and Christoph are talking about the zeroing of "tlb".
Indeed.
>
> The zeroi
flight 162932 linux-linus real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162932/
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-pvops
flight 162930 libvirt real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162930/
Regressions :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-amd64-pvops
flight 162942 xen-unstable-smoke real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162942/
Failures and problems with tests :-(
Tests which did not succeed and are blocking,
including tests which could not be run:
build-amd64 broken
build-arm64-xs
On Fri, 18 Jun 2021, Christoph Hellwig wrote:
> On Fri, Jun 18, 2021 at 09:09:17AM -0500, Tom Lendacky wrote:
> > > swiotlb_init_with_tbl uses memblock_alloc to allocate the io_tlb_mem
> > > and memblock_alloc[1] will do memset in memblock_alloc_try_nid[2], so
> > > swiotlb_init_with_tbl is also go
On 18/06/2021 03.06, Sander Eikelenboom wrote:
> On 17/06/2021 21:39, Sander Eikelenboom wrote:
>
> OK, done some experimentation and it seems with 256M assigned to the VM
> it was almost at the edge of OOM with the 5.12 kernel as well in the
> config I am using it.
> With v5.12 when I assign 240
flight 162929 xen-unstable real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162929/
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
On Mon, Jun 21, 2021 at 03:53:39PM +, George Dunlap wrote:
>
>
> > On May 24, 2021, at 9:36 PM, Nick Rosbrook wrote:
> >
> > The primary goal of this patch series is to allow users of the xenlight
> > package to manage a full domain life cycle. In particular, it provides
> > support for rec
Hi George (and sorry for the delay in replying),
On Mon, 2021-06-07 at 12:10 +, George Dunlap wrote:
> > On May 28, 2021, at 4:12 PM, Dario Faggioli
> > wrote:
> > Reported-by: Michał Leszczyński
> > Reported-by: Dion Kant
> > Signed-off-by: Dario Faggioli
>
> Thanks for tracking this dow
On Fri, Jun 18, 2021 at 11:00:26AM +, George Dunlap wrote:
>
>
> > On May 24, 2021, at 9:36 PM, Nick Rosbrook wrote:
> >
> > In gengotypes.py, the toC functions only set C string fields when
> > the Go strings are non-empty. However, to prevent segfaults in some
> > cases, these fields shou
> On May 24, 2021, at 9:36 PM, Nick Rosbrook wrote:
>
> The primary goal of this patch series is to allow users of the xenlight
> package to manage a full domain life cycle. In particular, it provides
> support for receiving domain death events so that domain shutdown,
> reboot, destroy, etc. c
On 21.06.2021 12:41, Andrew Cooper wrote:
> On 21/06/2021 07:58, Jan Beulich wrote:
>> On 18.06.2021 22:27, Daniel P. Smith wrote:
>>> On 6/18/21 8:26 AM, Jan Beulich wrote:
On 18.06.2021 01:39, Daniel P. Smith wrote:
> The only difference between !CONFIG_XSM and CONFIG_XSM with
> !CO
flight 162926 ovmf real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162926/
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-pvops
On 21/06/2021 07:58, Jan Beulich wrote:
> On 18.06.2021 22:27, Daniel P. Smith wrote:
>> On 6/18/21 8:26 AM, Jan Beulich wrote:
>>> On 18.06.2021 01:39, Daniel P. Smith wrote:
The only difference between !CONFIG_XSM and CONFIG_XSM with
!CONFIG_XSM_SILO and !CONFIG_XSM_FLASK
is wheth
> On 17 Jun 2021, at 18:38, Julien Grall wrote:
>
> From: Julien GralL
>
> As Live-Update is asynchronous, it is possible to receive a request to
> cancel it (either on the same connection or from a different one).
>
> Currently, this will crash xenstored because do_lu_start() assumes
> lu_
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> At the moment, Live-Update will, by default, not proceed if there are
> in-flight transactions. It is possible force it by passing -F but this
> will break any connection with in-flight transactions.
>
> There are PV
flight 162924 qemu-mainline real [real]
http://logs.test-lab.xenproject.org/osstest/logs/162924/
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-pvops
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> Currently, only Live-Update request can be delayed. In a follow-up,
> we will want to delay more requests (e.g. transaction start).
> Therefore we want to preserve delayed requests across Live-Update.
>
> Delayed req
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> Currently, the restore code is considering the stream will contain at
> most one in-flight request per connection. In a follow-up changes, we
> will want to transfer multiple in-flight requests.
>
> The function read
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> delay_request() is currently assuming that the request delayed is
> always conn->in. This is currently correct, but it is a call for
> a latent bug as the function allows the caller to specify any request.
>
> To pre
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> Currently, the callbacks can_read and can_write are called directly. This
> doesn't allow us to add generic check and therefore requires duplication.
>
> At the moment, one check that could benefit to be common is wh
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> xenstored_core.h will consider live-udpate is not supported if
> O_CLOEXEC doesn't exist. However, the header doesn't include the one
> defining O_CLOEXEC (i.e. fcntl.h). This means that depending on
> the header incl
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> Currently, only liveupdate request can be delayed. The request can only
> be performed by a privileged connection (e.g. dom0). So it is fine to
> have no limits.
>
> In a follow-up patch we will want to delay request
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> call_delayed() is currently assuming that conn->in is NULL when
> handling delayed request. However, the connection is not paused.
> Therefore new request can be processed and conn->in may be non-NULL
> if we have onl
> On 16 Jun 2021, at 15:43, Julien Grall wrote:
>
> From: Julien Grall
>
> At the moment, dump_state_buffered_data() is taking two connections
> in parameters (one is the connection to dump, the other is the
> connection used to request LU). The naming doesn't help to
> distinguish (c vs con
On 18.06.2021 18:42, Olaf Hering wrote:
> Fixes commit fa5afbbc20ef3577c5338f9d0b24dad45cef59cd,
> due to lack of commit 534519f0514f52007d504e0f2eeb714de7b2468d.
>
> Signed-off-by: Olaf Hering
Reviewed-by: Jan Beulich
albeit ...
> --- a/xen/include/xen/compiler.h
> +++ b/xen/include/xen/compi
On 18.06.2021 18:55, Olaf Hering wrote:
> Am Fri, 18 Jun 2021 17:46:47 +0100
> schrieb Andrew Cooper :
>
>> On 18/06/2021 17:42, Olaf Hering wrote:
>>> Fixes commit fa5afbbc20ef3577c5338f9d0b24dad45cef59cd,
>>> due to lack of commit 534519f0514f52007d504e0f2eeb714de7b2468d.
>
>> Presumably you're
On 18.06.2021 23:20, Andrew Cooper wrote:
> On 18/06/2021 13:26, Jan Beulich wrote:
>> On 18.06.2021 01:39, Daniel P. Smith wrote:
>>> The only difference between !CONFIG_XSM and CONFIG_XSM with
>>> !CONFIG_XSM_SILO and !CONFIG_XSM_FLASK
>>> is whether the XSM hooks in dummy.h are called as static
35 matches
Mail list logo
