Hi all, I’m sorry if this has been answered before and I overlooked some posting.
I’m using xCAT 2.16.5 running on a CentOS SN node. I use the xCAT SN instance to install clients with diskful SuSE sles15.4 images. Is there a way to enforce the installation of the target kernel during the 1st installation phase, so that the desired final kernel version is already running in the 2nd installation phase when I wanted to install the nvidia and MOFED RPMs with this kernel as target? I tried to add yet another directory to pkgdir, but this wasn’t successful (see below). Does anyone found a solution for this workflow and can share it? Many thanks in advance. Cheers, -Frank ---------------------------- 1. Create kernel repo for target kernel and add dir to pkgdir pkgdir=/install/sle15.4/x86_64,/install/Images/sles15.4-x86_64/compute-0.0.1/kernels --> is ignored in 1st phase; only the kernel version shipped with the distro (shipped with imported ISO) is installed 2. Contacted SuSE support for updating and recreating the repo --> the tool create_package_descr is outdated and not supported anymore; old RPMs still around in the web will most likely will produce a mess. See section 4.9.3 at SLES 15 SP4 | AutoYaST Guide | Configuration and installation options (suse.com) <https://documentation.suse.com/sles/15-SP4/html/SLES-all/cha-configuration-installation-options.html#CreateProfile-Software> 3. Create a new ISO – image containing the desired kernel RPMs + re-import of ISO in xCAT --> haven’t done that, yet, because it seems very cumbersome and clumsy. See https://documentation.suse.com/sbp/all/single-html/SBP-SLE15-Custom-Installation-Medium/
smime.p7s
Description: S/MIME cryptographic signature
_______________________________________________ xCAT-user mailing list xCAT-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/xcat-user
