[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [PATCH v2 2/3] tests/avocado: Add Fedora 34 distro, including kernel
From: |
David Woodhouse |
Subject: |
Re: [PATCH v2 2/3] tests/avocado: Add Fedora 34 distro, including kernel/initrd checksums |
Date: |
Wed, 08 Mar 2023 19:20:46 +0000 |
User-agent: |
Evolution 3.44.4-0ubuntu1 |
On Wed, 2023-03-08 at 17:42 +0000, Alex Bennée wrote:
>
> David Woodhouse <dwmw2@infradead.org> writes:
>
> > From: David Woodhouse <dwmw@amazon.co.uk>
> >
> > The kernel in Fedora 31 doesn't support 'xen_no_vector_callback' on
> > its command line, so add a slightly newer version as a prelude to
> > enabling avocado tests for Xen guests.
>
> Why slightly newer rather than current release?
>
> Our existing Fedora guest builds cause all sorts of timeout issues
> running under TCG and seem particularly heavyweight considering the
> coverage we manage to get.
Yeah, I spent a happy afternoon playing with this; I think you may have
observed some of it on IRC. Although I kept some of the naughtier words
to my side of the keyboard. From memory...
I tried Fedora 37 and eventually got that to *boot* (hint:
rootflags=subvol=root) although it concerned me that it wasn't yet at
the URL containing /archive/ so I wondered if adding it at its current
URL might not work in the long term. And then cloudinit didn't seem to
work on it (the finalize step failed in the guest IIRC).
I tried Fedora 36 and cloudinit *did* work there, and it was in
basically the same /pub/archive/fedora/ location so all that made me
happier... but 'dnf install xen-runtime' didn't work, which I was using
in my tests at that point to install the `xenstore-ls` binary. And in
fact dnf didn't seem to find *anything* useful at all in the
repositories which were configured in the Fedora Cloud 36 image.
So I tried Fedora 34, which is the first to have the
'xen_no_vector_callback' option that I'd added in the 5.12 kernel.
And when that worked, I declared all the above to be "Someone Else's
Problem".
The fact that it didn't boot with `-smp 4` was clearly *my* problem,
but the code was already merged upstream at that point, so fixing what
turned out to be the I/OAPIC migration bug ended up being my top
priority.
Now, I've dropped the dnf invocation because now the second PR has
been submitted I've switched it to use xen-disk anyway, and that's a
good enough exercise for both xenstore and event channel interrupts.
So it probably *could* move to Fedora 36, and the fact that the intel-
iommu test wouldn't work on Fedora 36 could remain Someone Else's
Problem. :)
Please advise.
smime.p7s
Description: S/MIME cryptographic signature