1. Forum
  2. Usenet
  3. LINUX.DEBIAN.BUGS.DIST

  • Bug#1106713: sbuild: How bind a charactere device in unshare

    From =?utf-8?q?Picca_Fr=C3=A9d=C3=A9ric-@21:1/5 to All on Wed May 28 13:10:01 2025
    Package: sbuild
    Version: 0.89.2
    Severity: normal

    Dear Maintainer,

    Hello, we are trying to run autopkgtest with a computer with and AMD GPU card.

    so the idea is to implement OpenCL test on real hardware.

    In order to run these test the hardware should be available in the unshare backend.

    for this the /dev/dri and /dev/kfd must be available.

    I discuss about this here[1] with the guyes in charge of the rocm stack.

    I would like to know if you could help and make sbuild work out of the box in our case

    for now I do not know if there is an sbuild configuration that could help fixing this...

    thanks for considering.

    Frederic

    [1] https://lists.debian.org/debian-science/2025/05/msg00029.html

    -- System Information:
    Debian Release: 13.0
    APT prefers unstable
    APT policy: (500, 'unstable'), (500, 'testing')
    Architecture: amd64 (x86_64)
    Foreign Architectures: i386

    Kernel: Linux 6.12.29-amd64 (SMP w/6 CPU threads; PREEMPT)
    Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not set
    Shell: /bin/sh linked to /usr/bin/dash
    Init: systemd (via /run/systemd/system)
    LSM: AppArmor: enabled

    Versions of packages sbuild depends on:
    ii adduser 3.152
    ii libsbuild-perl 0.89.2
    ii perl 5.40.1-3

    Versions of packages sbuild recommends:
    ii autopkgtest 5.49
    ii debootstrap 1.0.141
    ii iproute2 6.15.0-1
    ii mmdebstrap 1.5.7-1
    ii schroot 1.6.13-7
    ii uidmap 1:4.17.4-2

    Versions of packages sbuild suggests:
    ii e2fsprogs 1.47.2-1+b1
    ii kmod 34.2-2
    ii wget 1.25.0-2

    -- no debconf information

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jochen Sprickerhof@21:1/5 to All on Thu May 29 05:50:01 2025
    Control: -1 reassign autopkgtest

    Hi Frederic,

    * Picca Frédéric-Emmanuel <picca@debian.org> [2025-05-28 13:03]:
    Hello, we are trying to run autopkgtest with a computer with and AMD GPU card.

    sbuild only calls autopkgtest, so reassigning to autopkgtest
    accordingly.

    so the idea is to implement OpenCL test on real hardware.

    In order to run these test the hardware should be available in the unshare backend.

    Why in the unshare backend?

    for this the /dev/dri and /dev/kfd must be available.

    I discuss about this here[1] with the guyes in charge of the rocm stack.

    I would like to know if you could help and make sbuild work out of the box in our case

    Unlikely it is meant to provide some form of isolation and not expose hardware. I guess one of the other autopkgtest backends would be a
    better fit.

    for now I do not know if there is an sbuild configuration that could help fixing this...

    Once it is working with autopkgtest, coming up with an sbuild config
    should be easy.

    Cheers Jochen

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCgAdFiEEc7KZy9TurdzAF+h6W//cwljmlDMFAmg32NsACgkQW//cwljm lDOP8w/9Enn5DE6dl1m8rFC8F18YkQUWFcIFoioYXJ17qA4up03Il3FG1xpQ90cg ToKqNPHMbIqdXB7+69u59j+fmCxLwuFvDdOgTq8oe00wpVz77J+ZMIf28b4x5hZk hCUeL/8T0YfgIMET4vwwoXL57dHp74m2bVwb/qsTXz6gdHPe9+4JxAj7ron4alFj xMUpdVr7oFFqK3Dv6J033Qaro1f2HxxED4MRsh/qxy2/doDqZXBTjvCLHj41S7Re 3ibzrfDyJKtXNrtLcyoRmyn2nbScnpV4v6oScMaE5EB5q3mZi91iDK2zsf9tiJMK owlKBLXxHUphvAkeJRH7UtjWOyFVbnlLGQFx9F1GxaDM51xdFe6kfyQTAZU53FBu i+MR6m5WGsa1O/X0d8HBm1xiNVTADYFA+LEBUD+6fRy77IaunFTGFYK4jeLDgSZK 8t6/Ci6fFe7MGUrKvo7XzDXnncuA/9FMuKNApdXrk2t4p+WE+aDwlydxmpwnPQlH y46iYQDFVq648hv5upfYiSGwB91yZLAV8MaT7NSMPfX+oowlNxUbVIpDkOPW/jFQ Ybsm+0J5b1mfLUv/R9xc5P1MoE1miJIy+hY9i0PLDqFX4A4A1EbcpyhHU5z6GSFt jeEa042Jk0/NtSjTT6ClW9PWSXQBNSCRyWfkSsVlpkiKLh3NpW0=
    =UQZZ
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From picca@21:1/5 to Jochen Sprickerhof on Thu May 29 09:40:01 2025
    Jochen Sprickerhof <jspricke@debian.org> writes:

    Control: -1 reassign autopkgtest

    Hi Frederic,

    Hello Joshen

    so the idea is to implement OpenCL test on real hardware.

    In order to run these test the hardware should be available in the unshare backend.

    Why in the unshare backend?

    because it is the sbuild prefered backend now. I try to stick to the
    sbuild default so when I run sbuild it use unshare with autopkgtest.

    Unlikely it is meant to provide some form of isolation and not expose hardware. I guess one of the other autopkgtest backends would be a
    better fit.

    the rocm peoples are already proposing specific backend with podman or
    docker, but nothing for unshare.

    Do we have someone in Debian which know unsahre enought in order to
    explain what is possible and what is not with this backend ?

    Once it is working with autopkgtest, coming up with an sbuild config
    should be easy.

    yes :)


    Cheers

    Fred

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Jochen Sprickerhof@21:1/5 to All on Thu May 29 13:40:01 2025
    Am 29. Mai 2025 10:30:37 OESZ schrieb picca <picca@debian.org>:
    Jochen Sprickerhof <jspricke@debian.org> writes:
    Why in the unshare backend?

    because it is the sbuild prefered backend now. I try to stick to the
    sbuild default so when I run sbuild it use unshare with autopkgtest.

    That is only because it needs no setup. We will likely switch to this once it is there:

    <https://salsa.debian.org/ci-team/autopkgtest/-/merge_requests/515>

    the rocm peoples are already proposing specific backend with podman or >docker, but nothing for unshare.

    Note that the unshare backend is rather minimal on purpose. It fits for a lot of tests but for others podman may be a better fit.

    Cheers Jochen

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)