Le 22/01/2016 10:25, Marcus Schäfer a écrit :
Hi,
Why does kiwi install kernel-default whereas we only need kernel-lpae?
I guess this is because of this line:
chroot /usr/src/packages/KIWI-oem/oem/boot-VMX.cPGEzD/kiwi-VMXboot-3950
zypper --non-interactive --pkg-cache-dir /var/cache/kiwi/packages --reposd-dir
/var/cache/kiwi/zypper/repos --solv-cache-dir /var/cache/kiwi/zypper/solv
--cache-dir /var/cache/kiwi/zypper --config
/var/cache/kiwi/zypper/zypper.conf.3950 --no-gpg-checks install
--auto-agree-with-licenses --no-recommends kernel-default
because you are using vmxboot with the standard profile which pulls in
kernel-default. You can do the following:
I have : <type image="oem" boot="oemboot/suse-tumbleweed"
not vmxboot.
So, kiwi should use OEM things, not VMX. No?
- In your <type> section tell kiwi to use a custom kernel
<type .... bootkernel="custom"/>
- In your <packages type="image"/> section tell kiwi which kernel to use
<package name="kernel-lpae" bootinclude="true"/>
The bootinclude statement is important otherwise no kernel will be
installed in the boot(initrd) image
I have it in <packages type="bootstrap">, not image.
That way only kernel-lpae should be visible in the log. If now still
another kernel is pulled in it happens because zypper thinks it is
required which means some package triggers it
I do not think so, since it is pulled-in alone, not as dep.
Guillaume
Regards,
Marcus
--
To unsubscribe, e-mail: [email protected]
To contact the owner, e-mail: [email protected]
