From: dmkhn@proton.me
To: "Marek Marczykowski-Górecki" <marmarek@invisiblethingslab.com>
Cc: xen-devel@lists.xenproject.org,
Doug Goldstein <cardoe@cardoe.com>,
Stefano Stabellini <sstabellini@kernel.org>
Subject: Re: [PATCH v2 3/3] CI: Run driver domains test on Debian too
Date: Fri, 08 Aug 2025 17:30:33 +0000 [thread overview]
Message-ID: <aJY0NYbcHF6sZ/bY@kraken> (raw)
In-Reply-To: <3f4e22c2424e8b534fe743aad1e1ee4934f9444c.1754663560.git-series.marmarek@invisiblethingslab.com>
On Fri, Aug 08, 2025 at 04:32:43PM +0200, Marek Marczykowski-Górecki wrote:
> The recent failure affected only glibc-based systems, so do the test on
> Debian too.
>
> Signed-off-by: Marek Marczykowski-Górecki <marmarek@invisiblethingslab.com>
Just one tiny comment below, otherwise looks good to me!
With or without addressing it:
Reviewed-by: Denis Mukhin <dmukhin@ford.com>
> ---
> Changes in v2:
> - use systemd in Debian
>
> I once got the following timeout:
>
> (backend) ==> /var/log/xen/xldevd.log <==
> (backend) libxl: error: libxl_aoutils.c:539:async_exec_timeout: killing execution of /etc/xen/scripts/vif-bridge online because of timeout
>
> https://gitlab.com/xen-project/people/marmarek/xen/-/jobs/10961394681
> (docker-bobcat runner)
>
> Could be related to having systemd in domU (and being on QEMU TCG, not
> even KVM). I never hit this case on Alpine nor Debian with OpenRC. If
> that will repeat, may need some adjustments - more CPUs in QEMU? limit
> to more powerful runners? setup KVM on the runners?
> ---
> automation/gitlab-ci/test.yaml | 19 ++++++++++++++++++-
> automation/scripts/qemu-driverdomains-x86_64.sh | 18 +++++++++++++++--
> 2 files changed, 35 insertions(+), 2 deletions(-)
>
> diff --git a/automation/gitlab-ci/test.yaml b/automation/gitlab-ci/test.yaml
> index 5c4b2dc304b4..a5ae03b0eee9 100644
> --- a/automation/gitlab-ci/test.yaml
> +++ b/automation/gitlab-ci/test.yaml
> @@ -30,6 +30,17 @@
> job: microcode-x86
> ref: master
>
> +.debian-x86-64-test-needs: &debian-x86-64-test-needs
> + - project: xen-project/hardware/test-artifacts
> + job: linux-6.6.56-x86_64
> + ref: master
> + - project: xen-project/hardware/test-artifacts
> + job: debian-12-x86_64-rootfs
> + ref: master
> + - project: xen-project/hardware/test-artifacts
> + job: microcode-x86
> + ref: master
> +
> .qemu-arm64:
> extends: .test-jobs-common
> variables:
> @@ -664,6 +675,14 @@ qemu-alpine-driverdomains-x86_64-gcc:
> - *x86-64-test-needs
> - alpine-3.18-gcc
>
> +qemu-debian-12-driverdomains-x86_64-gcc:
> + extends: .qemu-x86-64
> + script:
> + - ./automation/scripts/qemu-driverdomains-x86_64.sh 2>&1 | tee ${LOGFILE}
> + needs:
> + - *debian-x86-64-test-needs
> + - debian-12-x86_64-gcc-debug
> +
> qemu-smoke-x86-64-gcc:
> extends: .qemu-smoke-x86-64
> script:
> diff --git a/automation/scripts/qemu-driverdomains-x86_64.sh b/automation/scripts/qemu-driverdomains-x86_64.sh
> index a8e2ceb33527..e5765ba5dbd6 100755
> --- a/automation/scripts/qemu-driverdomains-x86_64.sh
> +++ b/automation/scripts/qemu-driverdomains-x86_64.sh
> @@ -23,7 +23,11 @@ if grep -q test=backend /proc/cmdline; then
> brctl addbr xenbr0
> ip link set xenbr0 up
> ip addr add 192.168.0.1/24 dev xenbr0
> - bash /etc/init.d/xendriverdomain start
> + if [ -d /run/systemd ]; then
> + systemctl start xendriverdomain
> + else
> + bash /etc/init.d/xendriverdomain start
> + fi
> # log backend-related logs to the console
> tail -F /var/log/xen/xldevd.log /var/log/xen/xen-hotplug.log >>/dev/console 2>/dev/null &
> else
> @@ -77,7 +81,11 @@ cat > etc/local.d/xen.start << EOF
>
> set -x
>
> -bash /etc/init.d/xencommons start
> +if [ -d /run/systemd ]; then
> + systemctl start xen-init-dom0.service
> +else
> + bash /etc/init.d/xencommons start
> +fi
>
> xl list
>
> @@ -94,6 +102,12 @@ cp ../bzImage ./root/
> mkdir -p etc/default
> echo 'XENCONSOLED_TRACE=all' >> etc/default/xencommons
> mkdir -p var/log/xen/console
> +if [ -e etc/systemd/system.conf ]; then
> + chroot . systemctl enable proc-xen.mount \
> + xenstored.service \
> + xenconsoled.service \
> + xen-init-dom0.service
I would keep the list of files sorted; that may help with future merges, if
any.
> +fi
> mkfs.ext4 -d . ../dom0-rootfs.img 2048M
> cd ..
> rm -rf rootfs
> --
> git-series 0.9.1
>
prev parent reply other threads:[~2025-08-08 17:31 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-08 14:32 [PATCH v2 0/3] Add driver domains test Marek Marczykowski-Górecki
2025-08-08 14:32 ` [PATCH v2 1/3] CI: Add driver domains tests Marek Marczykowski-Górecki
2025-08-08 17:02 ` dmkhn
2025-08-08 14:32 ` [PATCH v2 2/3] CI: Add configure --enable-systemd for full build Marek Marczykowski-Górecki
2025-08-08 17:03 ` dmkhn
2025-08-08 14:32 ` [PATCH v2 3/3] CI: Run driver domains test on Debian too Marek Marczykowski-Górecki
2025-08-08 17:30 ` dmkhn [this message]
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=aJY0NYbcHF6sZ/bY@kraken \
--to=dmkhn@proton.me \
--cc=cardoe@cardoe.com \
--cc=marmarek@invisiblethingslab.com \
--cc=sstabellini@kernel.org \
--cc=xen-devel@lists.xenproject.org \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.