On Mon, 08 May 2023 10:12:35 +0200
Juan Quintela wrote:
> Lukas Straub wrote:
> > On Tue, 02 May 2023 12:39:12 +0200
> > Juan Quintela wrote:
> >
> >> [...]
> >>
> >> my patches are only code movement and cleanups, so Lukas any clue?
> >>
> >> Lukas, I am going to drop the compress code for
Lukas Straub wrote:
> On Tue, 02 May 2023 12:39:12 +0200
> Juan Quintela wrote:
>
>> [...]
>>
>> my patches are only code movement and cleanups, so Lukas any clue?
>>
>> Lukas, I am going to drop the compress code for now and pass the other
>> patches. In the meanwhile, I am going to try to
On Tue, 02 May 2023 12:39:12 +0200
Juan Quintela wrote:
> [...]
>
> my patches are only code movement and cleanups, so Lukas any clue?
>
> Lukas, I am going to drop the compress code for now and pass the other
> patches. In the meanwhile, I am going to try to setup some machine
> where I can
On Wed, 3 May 2023 at 14:29, Juan Quintela wrote:
> So now we are between a rock and a hard place.
>
> We have slowed down the bandwidth for migration test because on non
> loaded machines, migration was too fast to need more than one pass.
>
> And we slowed it so much than now we hit the timer
Peter Maydell wrote:
> On Wed, 3 May 2023 at 10:17, Juan Quintela wrote:
>>
>> Peter Maydell wrote:
>> > On Tue, 2 May 2023 at 11:39, Juan Quintela wrote:
>> >> Richard, once that we are here, one of the problem that we are having is
>> >> that the test is exiting with an abort, so we have no
On Wed, 3 May 2023 at 10:17, Juan Quintela wrote:
>
> Peter Maydell wrote:
> > On Tue, 2 May 2023 at 11:39, Juan Quintela wrote:
> >> Richard, once that we are here, one of the problem that we are having is
> >> that the test is exiting with an abort, so we have no clue what is
> >> happening.
On Wed, May 03, 2023 at 11:17:33AM +0200, Juan Quintela wrote:
> Peter Maydell wrote:
> > On Tue, 2 May 2023 at 11:39, Juan Quintela wrote:
> >> Richard, once that we are here, one of the problem that we are having is
> >> that the test is exiting with an abort, so we have no clue what is
> >>
Peter Maydell wrote:
> On Tue, 2 May 2023 at 11:39, Juan Quintela wrote:
>> Richard, once that we are here, one of the problem that we are having is
>> that the test is exiting with an abort, so we have no clue what is
>> happening. Is there a way to get a backtrace, or at least the number
>
>
On Tue, 2 May 2023 at 11:39, Juan Quintela wrote:
> Richard, once that we are here, one of the problem that we are having is
> that the test is exiting with an abort, so we have no clue what is
> happening. Is there a way to get a backtrace, or at least the number
This has been consistently an
Richard Henderson wrote:
> On 4/28/23 20:11, Juan Quintela wrote:
>> The following changes since commit 05d50ba2d4668d43a835c5a502efdec9b92646e6:
>>Merge tag 'migration-20230427-pull-request' of
>> https://gitlab.com/juan.quintela/qemu into staging (2023-04-28
>> 08:35:06 +0100)
>> are
On 4/29/23 21:14, Lukas Straub wrote:
On Sat, 29 Apr 2023 19:45:07 +0100
Richard Henderson wrote:
On 4/28/23 20:11, Juan Quintela wrote:
The following changes since commit 05d50ba2d4668d43a835c5a502efdec9b92646e6:
Merge tag 'migration-20230427-pull-request' of
On Sat, 29 Apr 2023 19:45:07 +0100
Richard Henderson wrote:
> On 4/28/23 20:11, Juan Quintela wrote:
> > The following changes since commit 05d50ba2d4668d43a835c5a502efdec9b92646e6:
> >
> >Merge tag 'migration-20230427-pull-request' of
> > https://gitlab.com/juan.quintela/qemu into staging
On 4/28/23 20:11, Juan Quintela wrote:
The following changes since commit 05d50ba2d4668d43a835c5a502efdec9b92646e6:
Merge tag 'migration-20230427-pull-request' of
https://gitlab.com/juan.quintela/qemu into staging (2023-04-28 08:35:06 +0100)
are available in the Git repository at:
The following changes since commit 05d50ba2d4668d43a835c5a502efdec9b92646e6:
Merge tag 'migration-20230427-pull-request' of
https://gitlab.com/juan.quintela/qemu into staging (2023-04-28 08:35:06 +0100)
are available in the Git repository at:
https://gitlab.com/juan.quintela/qemu.git
14 matches
Mail list logo
