Peter Maydell writes:
> "make check-acceptance" takes way way too long. I just did a run
> on an arm-and-aarch64-targets-only debug build and it took over
> half an hour, and this despite it skipping or cancelling 26 out
> of 58 tests!
>
> I think that ~10 minutes runtime is reasonable. 30 is
On Tue, Feb 1, 2022 at 1:06 PM Alex Bennée wrote:
>
>
> Cleber Rosa writes:
>
> > On Tue, Feb 1, 2022 at 11:20 AM Daniel P. Berrangé
> > wrote:
> >>
> >> On Tue, Feb 01, 2022 at 11:01:43AM -0500, Cleber Rosa wrote:
> >> > On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée
> >> > wrote:
> >> > >
> >>
On Tue, 1 Feb 2022 12:47:48 -0500
Cleber Rosa wrote:
> On Tue, Feb 1, 2022 at 11:20 AM Daniel P. Berrangé
> wrote:
> >
> > On Tue, Feb 01, 2022 at 11:01:43AM -0500, Cleber Rosa wrote:
> > > On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée
> > > wrote:
> > > >
> > > > We have up to now tried
On Tue, Feb 1, 2022 at 12:01 PM Daniel P. Berrangé wrote:
>
> On Tue, Feb 01, 2022 at 12:29:56AM -0500, Cleber Rosa wrote:
> >
> > Assuming this is about "Testing that QEMU can boot a full distro", I
> > wouldn't
> > try to solve the problem by making the distro too slim to get to the
> > point
On 2/1/22 17:01, Cleber Rosa wrote:
On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée wrote:
We have up to now tried really hard as a project to avoid building and
hosting our own binaries to avoid theoretical* GPL compliance issues.
This is why we've ended up relying so much on distros to build and
On Tue, Feb 1, 2022 at 11:20 AM Daniel P. Berrangé wrote:
>
> On Tue, Feb 01, 2022 at 11:01:43AM -0500, Cleber Rosa wrote:
> > On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée wrote:
> > >
> > > We have up to now tried really hard as a project to avoid building and
> > > hosting our own binaries to
On Tue, Feb 01, 2022 at 12:29:56AM -0500, Cleber Rosa wrote:
>
> Assuming this is about "Testing that QEMU can boot a full distro", I wouldn't
> try to solve the problem by making the distro too slim to get to the
> point of becoming
> an unrealistic system.
At a high level our with acceptance
Cleber Rosa writes:
> On Tue, Feb 1, 2022 at 11:20 AM Daniel P. Berrangé
> wrote:
>>
>> On Tue, Feb 01, 2022 at 11:01:43AM -0500, Cleber Rosa wrote:
>> > On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée wrote:
>> > >
>> > > We have up to now tried really hard as a project to avoid building and
>>
On Tue, Feb 01, 2022 at 11:01:43AM -0500, Cleber Rosa wrote:
> On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée wrote:
> >
> > We have up to now tried really hard as a project to avoid building and
> > hosting our own binaries to avoid theoretical* GPL compliance issues.
> > This is why we've ended up
On Tue, Feb 1, 2022 at 6:07 AM Kashyap Chamarthy wrote:
>
> On Tue, Jan 25, 2022 at 10:20:11AM +0100, Gerd Hoffmann wrote:
> > Hi,
> >
> > > IMHO the ideal scenario would be for us to have a kernel, initrd
> > > containing just busybox tools for the key arch targets we care
> > > about. Those
On Tue, Feb 1, 2022 at 6:25 AM Alex Bennée wrote:
>
> We have up to now tried really hard as a project to avoid building and
> hosting our own binaries to avoid theoretical* GPL compliance issues.
> This is why we've ended up relying so much on distros to build and host
> binaries we can use.
Stefano Brivio writes:
> On Tue, 1 Feb 2022 09:06:25 +
> Daniel P. Berrangé wrote:
>
>> On Tue, Feb 01, 2022 at 07:31:39AM +0100, Stefano Brivio wrote:
>> > Hi,
>> >
>> > On Tue, 25 Jan 2022 10:20:11 +0100
>> > Gerd Hoffmann wrote:
>> >
>> > > Hi,
>> > >
>> > > > IMHO the ideal
On Tue, Jan 25, 2022 at 10:20:11AM +0100, Gerd Hoffmann wrote:
> Hi,
>
> > IMHO the ideal scenario would be for us to have a kernel, initrd
> > containing just busybox tools for the key arch targets we care
> > about. Those could be used with direct kernel boot or stuffed
> > into a disk iamge.
On Tue, 1 Feb 2022 09:06:25 +
Daniel P. Berrangé wrote:
> On Tue, Feb 01, 2022 at 07:31:39AM +0100, Stefano Brivio wrote:
> > Hi,
> >
> > On Tue, 25 Jan 2022 10:20:11 +0100
> > Gerd Hoffmann wrote:
> >
> > > Hi,
> > >
> > > > IMHO the ideal scenario would be for us to have a
On Tue, Feb 01, 2022 at 07:31:39AM +0100, Stefano Brivio wrote:
> Hi,
>
> On Tue, 25 Jan 2022 10:20:11 +0100
> Gerd Hoffmann wrote:
>
> > Hi,
> >
> > > IMHO the ideal scenario would be for us to have a kernel, initrd
> > > containing just busybox tools for the key arch targets we care
> > >
Hi,
> I'm not sure you can recycle something from it, but my (ugly) approach
> to make this fast (for a different purpose -- I'm using qemu to run
> tests in guests, not testing qemu) is to build an initramfs by copying
> the host binaries I need (a shell, ip, jq) and recursively sourcing
>
Hi,
On Tue, 25 Jan 2022 10:20:11 +0100
Gerd Hoffmann wrote:
> Hi,
>
> > IMHO the ideal scenario would be for us to have a kernel, initrd
> > containing just busybox tools for the key arch targets we care
> > about. Those could be used with direct kernel boot or stuffed
> > into a disk iamge.
On Fri, Jan 21, 2022 at 10:22 AM Daniel P. Berrangé wrote:
>
> On Fri, Jan 21, 2022 at 12:23:23PM +, Alex Bennée wrote:
> >
> > Peter Maydell writes:
> >
> > > On Fri, 21 Jan 2022 at 10:50, Markus Armbruster wrote:
> > >> No objection, but it's no replacement for looking into why these
Hi,
> IMHO the ideal scenario would be for us to have a kernel, initrd
> containing just busybox tools for the key arch targets we care
> about. Those could be used with direct kernel boot or stuffed
> into a disk iamge. Either way, they would boot in ~1 second,
> even with TCG, and would be
On Fri, Jan 21, 2022 at 12:23:23PM +, Alex Bennée wrote:
>
> Peter Maydell writes:
>
> > On Fri, 21 Jan 2022 at 10:50, Markus Armbruster wrote:
> >> No objection, but it's no replacement for looking into why these tests
> >> are so slow.
> >>
> >> The #1 reason for things being slow is not
On 21/01/2022 13.23, Alex Bennée wrote:
Peter Maydell writes:
On Fri, 21 Jan 2022 at 10:50, Markus Armbruster wrote:
No objection, but it's no replacement for looking into why these tests
are so slow.
The #1 reason for things being slow is not giving a damn :)
See previous messages in
Peter Maydell writes:
> On Fri, 21 Jan 2022 at 10:50, Markus Armbruster wrote:
>> No objection, but it's no replacement for looking into why these tests
>> are so slow.
>>
>> The #1 reason for things being slow is not giving a damn :)
>
> See previous messages in the thread -- the test starts
On Fri, 21 Jan 2022 at 10:50, Markus Armbruster wrote:
> No objection, but it's no replacement for looking into why these tests
> are so slow.
>
> The #1 reason for things being slow is not giving a damn :)
See previous messages in the thread -- the test starts a
full-fat guest OS including UEFI
Thomas Huth writes:
> On 20/01/2022 16.13, Peter Maydell wrote:
>> On Fri, 30 Jul 2021 at 16:12, Peter Maydell wrote:
>>>
>>> "make check-acceptance" takes way way too long. I just did a run
>>> on an arm-and-aarch64-targets-only debug build and it took over
>>> half an hour, and this despite
On 20/01/2022 16.13, Peter Maydell wrote:
On Fri, 30 Jul 2021 at 16:12, Peter Maydell wrote:
"make check-acceptance" takes way way too long. I just did a run
on an arm-and-aarch64-targets-only debug build and it took over
half an hour, and this despite it skipping or cancelling 26 out
of 58
Cc'ing Beraldo
On 20/1/22 16:13, Peter Maydell wrote:
On Fri, 30 Jul 2021 at 16:12, Peter Maydell wrote:
"make check-acceptance" takes way way too long. I just did a run
on an arm-and-aarch64-targets-only debug build and it took over
half an hour, and this despite it skipping or cancelling
On Fri, 30 Jul 2021 at 16:12, Peter Maydell wrote:
>
> "make check-acceptance" takes way way too long. I just did a run
> on an arm-and-aarch64-targets-only debug build and it took over
> half an hour, and this despite it skipping or cancelling 26 out
> of 58 tests!
>
> I think that ~10 minutes
On Sat, Jul 31, 2021 at 4:33 PM Peter Maydell wrote:
>
> On Sat, 31 Jul 2021 at 19:43, Alex Bennée wrote:
> >
> >
> > Peter Maydell writes:
> >
> > > "make check-acceptance" takes way way too long. I just did a run
> > > on an arm-and-aarch64-targets-only debug build and it took over
> > > half
Hi,
> > Ok, so that would require a bootloader build too, which is likely going
> > to be arch specific, so probably the most tedious part.
>
> Maybe we could use buildroot for this. I've used buildroot for my images in
> the QEMU Advent Calendar, and it was really a great help. See also:
>
>
On 02/08/2021 15.00, Daniel P. Berrangé wrote:
On Mon, Aug 02, 2021 at 01:55:44PM +0100, Alex Bennée wrote:
Daniel P. Berrangé writes:
On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
"make check-acceptance" takes way way too long. I just did a run
on an
On 02/08/2021 15.04, Daniel P. Berrangé wrote:
On Mon, Aug 02, 2021 at 02:00:19PM +0100, Peter Maydell wrote:
On Mon, 2 Aug 2021 at 13:57, Alex Bennée wrote:
Daniel P. Berrangé writes:
On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
"make check-acceptance" takes way way
On Mon, Aug 02, 2021 at 02:00:19PM +0100, Peter Maydell wrote:
> On Mon, 2 Aug 2021 at 13:57, Alex Bennée wrote:
> >
> >
> > Daniel P. Berrangé writes:
> >
> > > On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
> > >> "make check-acceptance" takes way way too long. I just did a run
On Mon, 2 Aug 2021 at 13:57, Alex Bennée wrote:
>
>
> Daniel P. Berrangé writes:
>
> > On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
> >> "make check-acceptance" takes way way too long. I just did a run
> >> on an arm-and-aarch64-targets-only debug build and it took over
> >>
On Mon, Aug 02, 2021 at 01:55:44PM +0100, Alex Bennée wrote:
>
> Daniel P. Berrangé writes:
>
> > On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
> >> "make check-acceptance" takes way way too long. I just did a run
> >> on an arm-and-aarch64-targets-only debug build and it took
On Mon, Aug 02, 2021 at 01:47:37PM +0100, Alex Bennée wrote:
>
> Daniel P. Berrangé writes:
>
> > On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
> >> "make check-acceptance" takes way way too long. I just did a run
> >> on an arm-and-aarch64-targets-only debug build and it took
Daniel P. Berrangé writes:
> On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
>> "make check-acceptance" takes way way too long. I just did a run
>> on an arm-and-aarch64-targets-only debug build and it took over
>> half an hour, and this despite it skipping or cancelling 26 out
Daniel P. Berrangé writes:
> On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
>> "make check-acceptance" takes way way too long. I just did a run
>> on an arm-and-aarch64-targets-only debug build and it took over
>> half an hour, and this despite it skipping or cancelling 26 out
On Fri, Jul 30, 2021 at 04:12:27PM +0100, Peter Maydell wrote:
> "make check-acceptance" takes way way too long. I just did a run
> on an arm-and-aarch64-targets-only debug build and it took over
> half an hour, and this despite it skipping or cancelling 26 out
> of 58 tests!
>
> I think that ~10
On Sat, 31 Jul 2021 at 19:43, Alex Bennée wrote:
>
>
> Peter Maydell writes:
>
> > "make check-acceptance" takes way way too long. I just did a run
> > on an arm-and-aarch64-targets-only debug build and it took over
> > half an hour, and this despite it skipping or cancelling 26 out
> > of 58
Peter Maydell writes:
> "make check-acceptance" takes way way too long. I just did a run
> on an arm-and-aarch64-targets-only debug build and it took over
> half an hour, and this despite it skipping or cancelling 26 out
> of 58 tests!
>
> I think that ~10 minutes runtime is reasonable. 30 is
On Sat, Jul 31, 2021 at 2:40 AM Thomas Huth wrote:
>
> On 31/07/2021 00.04, Cleber Rosa wrote:
> > On Fri, Jul 30, 2021 at 11:43 AM Peter Maydell
> > wrote:
> >>
> >> On Fri, 30 Jul 2021 at 16:12, Peter Maydell
> >> wrote:
> >>>
> >>> "make check-acceptance" takes way way too long. I just did
On 31/07/2021 00.04, Cleber Rosa wrote:
On Fri, Jul 30, 2021 at 11:43 AM Peter Maydell wrote:
On Fri, 30 Jul 2021 at 16:12, Peter Maydell wrote:
"make check-acceptance" takes way way too long. I just did a run
on an arm-and-aarch64-targets-only debug build and it took over
half an hour,
On Fri, Jul 30, 2021 at 11:43 AM Peter Maydell wrote:
>
> On Fri, 30 Jul 2021 at 16:12, Peter Maydell wrote:
> >
> > "make check-acceptance" takes way way too long. I just did a run
> > on an arm-and-aarch64-targets-only debug build and it took over
> > half an hour, and this despite it skipping
On Fri, 30 Jul 2021 at 16:12, Peter Maydell wrote:
>
> "make check-acceptance" takes way way too long. I just did a run
> on an arm-and-aarch64-targets-only debug build and it took over
> half an hour, and this despite it skipping or cancelling 26 out
> of 58 tests!
>
> I think that ~10 minutes
On 7/30/21 5:12 PM, Peter Maydell wrote:
> "make check-acceptance" takes way way too long. I just did a run
> on an arm-and-aarch64-targets-only debug build and it took over
> half an hour, and this despite it skipping or cancelling 26 out
> of 58 tests!
>
> I think that ~10 minutes runtime is
45 matches
Mail list logo
