qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Remi Duraffort <remi.duraffort@linaro.org>
To: "Alex Bennée" <alex.bennee@linaro.org>
Cc: Anders Roxell <anders.roxell@linaro.org>,
	David Woodhouse <dwmw2@infradead.org>,
	qemu-devel <qemu-devel@nongnu.org>
Subject: Re: Adding default config options to the tuxrun baseline kernels and enabling sshd
Date: Fri, 24 Mar 2023 13:53:58 +0100	[thread overview]
Message-ID: <CANJfhHe-E-+F_P_=+ww46Szp_To=C4QWxKG5hdeCriwQr821jg@mail.gmail.com> (raw)
In-Reply-To: <87h6ua4dkw.fsf@linaro.org>

[-- Attachment #1: Type: text/plain, Size: 2321 bytes --]

Hello Alex,



Le ven. 24 mars 2023 à 12:02, Alex Bennée <alex.bennee@linaro.org> a écrit :

> Hi guys,
>
> I've been working with David on adding testing for the new KVM Xen guest
> functionality and had a couple of questions. His original test is based
> on fedora and is fairly comprehensive:
>
>
> https://git.infradead.org/users/dwmw2/qemu.git/commitdiff/48f78f9bb860dca446e20d6ed8db3aa9d857505f
>
> but we did try building a scratch kernel and using the rest of the
> baseline infrastructure which worked well enough:
>
>
> https://git.infradead.org/users/dwmw2/qemu.git/commitdiff/8b9e04d1c7c942f51b575b94fd280bd2353f76b6
>
> but obviously the kernel there is pulling directly from tuxsuite so will
> time out soon enough. They were built with the following tuxbuild
> config:
>
>   version: 1
>   name: Xen Guest Kernels
>   description: Build Xen Test Kernels
>   jobs:
>   - builds:
>       - {target_arch: x86_64, toolchain: gcc-12, kconfig: [defconfig,
> "CONFIG_XEN=y", "CONFIG_XEN_PVHVM=y", "CONFIG_XEN_BLKDEV_FRONTEND=y",
> "CONFIG_XEN_PVHVM_GUEST=y"]}
>       - {target_arch: i386, toolchain: gcc-12, kconfig: [defconfig,
> "CONFIG_XEN=y", "CONFIG_XEN_PVHVM=y", "CONFIG_XEN_BLKDEV_FRONTEND=y",
> "CONFIG_XEN_PVHVM_GUEST=y"]}
>     test: {device: qemu-x86_64, tests: [ltp-smoke]}
>
> The other nice thing about his original tests where using ssh which
> avoids a) avoids some of the flakeness of using the serial port and b)
> has an explicit success/fail for each command without having to scrape
> pass/fail from the log.
>
> So two questions:
>
>   - is there a process for adding kernel options to the baseline kernels
>     or should we build our own and store them somewhere?
>
>   - what would it take to get dropbear added to the baseline ext4 images
>     so we can enable sshd?
>

The kernels and rootfs are built by this gitlab project:
https://gitlab.com/LinaroLtd/tuxsuite.com/tuxtest/tuxtest-buildroot using
buildroot.
So for sure we can add sshd support quickly. Regarding the support for xen,
this can be added for arm64 if you want (only arm64 or something else)?




> Thanks,
>
> --
> Alex Bennée
> Virtualisation Tech Lead @ Linaro
>


-- 
Rémi Duraffort
Principal Tech Lead
Automation Software Team
Linaro

[-- Attachment #2: Type: text/html, Size: 3844 bytes --]

  reply	other threads:[~2023-03-24 15:23 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-03-24 10:47 Adding default config options to the tuxrun baseline kernels and enabling sshd Alex Bennée
2023-03-24 12:53 ` Remi Duraffort [this message]
2023-03-24 13:26   ` David Woodhouse
2023-03-24 19:48     ` Stefano Stabellini
2023-03-24 17:11   ` Alex Bennée

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='CANJfhHe-E-+F_P_=+ww46Szp_To=C4QWxKG5hdeCriwQr821jg@mail.gmail.com' \
    --to=remi.duraffort@linaro.org \
    --cc=alex.bennee@linaro.org \
    --cc=anders.roxell@linaro.org \
    --cc=dwmw2@infradead.org \
    --cc=qemu-devel@nongnu.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 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).