Re: Adding default config options to the tuxrun baseline kernels and enabling sshd

["Alex Bennée" <alex.bennee@linaro.org>]

Remi Duraffort <remi.duraffort@linaro.org> writes:

> 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:

Just mentioning I posted an RFC:

  Subject: [RFC PATCH] tests/avocado: Test Xen guest support under KVM
  Date: Fri, 24 Mar 2023 16:07:19 +0000
  Message-Id: <20230324160719.1790792-1-alex.bennee@linaro.org>

which uses a custom kernel + hand built rootfs for now.

>  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.

Erm that gives me a 404. I can see various tux* projects under:

  https://gitlab.com/Linaro

but nothing related to tuxtest-buildroot.

> So for sure we can add sshd support quickly.

I enabled dropbear and the following overlay:

  https://gitlab.com/stsquad/buildroot-overlays/-/tree/main/noauth-serial-and-ssh

Obviously this drops any pretence of security but I think the root has
no password anyway so adding /etc/dropbear/defaults with:

  # Allow empty password login
  DROPBEAR_ARGS=-B

is enough. Once pointed at the right place I shall have a go at tweaking
the build.

-- 
Alex Bennée
Virtualisation Tech Lead @ Linaro