From: David Woodhouse <dwmw2@infradead.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: "Cleber Rosa" <crosa@redhat.com>,
"Philippe Mathieu-Daudé" <philmd@linaro.org>,
"Wainer dos Santos Moschetta" <wainersm@redhat.com>,
"Beraldo Leal" <bleal@redhat.com>,
"Paolo Bonzini" <pbonzini@redhat.com>,
"Paul Durrant" <paul@xen.org>,
"Michael S. Tsirkin" <mst@redhat.com>,
"Peter Xu" <peterx@redhat.com>,
qemu-devel@nongnu.org
Subject: Re: [PATCH v2 2/3] tests/avocado: Add Fedora 34 distro, including kernel/initrd checksums
Date: Thu, 09 Mar 2023 08:51:10 +0000 [thread overview]
Message-ID: <0d64ec92287c268727f6bdc7b5723d57a397e1bb.camel@infradead.org> (raw)
In-Reply-To: <c9959d02928c14a3e93f9419099a08102887b887.camel@infradead.org>
[-- Attachment #1: Type: text/plain, Size: 4854 bytes --]
On Wed, 2023-03-08 at 19:20 +0000, David Woodhouse wrote:
> On Wed, 2023-03-08 at 17:42 +0000, Alex Bennée wrote:
> > 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...
So...
'34': {
'x86_64':
{'checksum': ('b9b621b26725ba95442d9a56cbaa0547'
'84e0779a9522ec6eafff07c6e6f717ea'),
'pxeboot_url': ('https://archives.fedoraproject.org/'
'pub/archive/fedora/linux/releases/34/'
'Everything/x86_64/os/images/pxeboot/'),
'kernel_hash': ('085fc6e47f2e3a271b591f3e56739ca9'
'4c16718837a5f431ab95468e1e95f9eb'),
'initrd_hash': ('d6cd2e03e8188eed6c896fd65ff05f81'
'2c4c1c8777d630b5909e9a1a4627e337'),
'kernel_params': ('root=UUID=386769a3-cfa5-47c8-8797-'
'd5ec58c9cb6c ro no_timer_check '
'net.ifnames=0 console=tty1 '
'console=ttyS0,115200n8'),
},
},
'36': {
'x86_64':
{'checksum': ('ca9e514cc2f4a7a0188e7c68af60eb4e'
'573d2e6850cc65b464697223f46b4605'),
'pxeboot_url': ('https://archives.fedoraproject.org/'
'pub/archive/fedora/linux/releases/36/'
'Everything/x86_64/os/images/pxeboot/'),
'kernel_hash': ('f5d8162b1e086f1a9d09d3d2c6decdbe'
'c84d7020cde4b6f32a98f21eacc8cf3b'),
'initrd_hash': ('2c8a9d3f0b607f86422a0df8227106c0'
'847eb4a4f15bade77b1abbc3228533c6'),
'kernel_params': ('root=UUID=737459fa-eab9-4d8f-9a14-'
'c8c32d403c08 ro rootflags=subvol=root '
'no_timer_check net.ifnames=0 '
'console=tty1 console=ttyS0,115200n8'),
},
},
'37': {
'x86_64':
{'checksum': ('b5b9bec91eee65489a5745f6ee620573'
'b23337cbb1eb4501ce200b157a01f3a0'),
'pxeboot_url': ('https://archives.fedoraproject.org/'
'pub/fedora/linux/releases/37/'
'Everything/x86_64/os/images/pxeboot/'),
'kernel_hash': ('2bd5f834349313d10a9dbeb41d9f71d9'
'85f7b9c4f7e2ba750a1dd6558f082ba9'),
'initrd_hash': ('8b7e91d6f14353217ed44a98802b0fef'
'b190ab1ce38a96166da87d629ab39bef'),
'kernel_params': ('root=UUID=3975d5e5-e66a-44c3-90f7-'
'dc2d1c7859d1 ro rootflags=subvol=root '
'no_timer_check net.ifnames=0 '
'console=tty1 console=ttyS0,115200n8'),
},
},
}
Fedora 36 does work (since I'm not actually trying to install anything
inside the guest any more, and I'm sure that *would* be a surmountable
problem if we bothered to investigate and fix up the repo config). It's
about 10 seconds slower per test than Fedora 34 was.
Fedora 37 fails thus:
2023-03-09 08:25:17,072 datadrainer L0193 DEBUG| -----END SSH HOST KEY KEYS-----
2023-03-09 08:25:17,081 datadrainer L0193 DEBUG| [ 49.036621] cloud-init[1550]: 2023-03-09 08:25:16,989 - util.py[WARNING]: Running module phone-home (<module 'cloudinit.config.cc_phone_home' from '/usr/lib/python3.11/site-packages/cloudinit/config/cc_phone_home.py'>) failed
2023-03-09 08:25:17,101 datadrainer L0193 DEBUG| [ 49.055528] cloud-init[1550]: Cloud-init v. 22.2 finished at Thu, 09 Mar 2023 08:25:16 +0000. Datasource DataSourceNoCloud [seed=/dev/sda][dsmode=net]. Up 49.04 seconds
2023-03-09 08:25:17,203 datadrainer L0193 DEBUG| [FAILED] Failed to start cloud-fina… Execute cloud user/final scripts.
Full log at http://david.woodhou.se/job-2023-03-09T08.20-d57f30d.log
I've made the other changes (mostly xen_guest → kvm_xen_guest) and
pushed to my branch at
https://git.infradead.org/users/dwmw2/qemu.git/shortlog/refs/heads/xenfv
[-- Attachment #2: smime.p7s --]
[-- Type: application/pkcs7-signature, Size: 5965 bytes --]
next prev parent reply other threads:[~2023-03-09 8:52 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-08 11:19 [PATCH v2 0/3] Enable avocado testing for Xen guests David Woodhouse
2023-03-08 11:19 ` [PATCH v2 1/3] hw/intc/ioapic: Update KVM routes before redelivering IRQ, on RTE update David Woodhouse
2023-03-09 11:44 ` Paolo Bonzini
2023-03-08 11:19 ` [PATCH v2 2/3] tests/avocado: Add Fedora 34 distro, including kernel/initrd checksums David Woodhouse
2023-03-08 17:42 ` Alex Bennée
2023-03-08 19:20 ` David Woodhouse
2023-03-09 8:51 ` David Woodhouse [this message]
2023-03-08 11:19 ` [PATCH v2 3/3] tests/avocado: Test Xen guest support under KVM David Woodhouse
2023-03-08 17:45 ` Alex Bennée
2023-03-08 19:07 ` David Woodhouse
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0d64ec92287c268727f6bdc7b5723d57a397e1bb.camel@infradead.org \
--to=dwmw2@infradead.org \
--cc=alex.bennee@linaro.org \
--cc=bleal@redhat.com \
--cc=crosa@redhat.com \
--cc=mst@redhat.com \
--cc=paul@xen.org \
--cc=pbonzini@redhat.com \
--cc=peterx@redhat.com \
--cc=philmd@linaro.org \
--cc=qemu-devel@nongnu.org \
--cc=wainersm@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).