[Bug 846068] New: kiwi: support use of custom or version pinned kernels more easy
https://bugzilla.novell.com/show_bug.cgi?id=846068 https://bugzilla.novell.com/show_bug.cgi?id=846068#c0 Summary: kiwi: support use of custom or version pinned kernels more easy Classification: openSUSE Product: openSUSE.org Version: unspecified Platform: Other OS/Version: Other Status: ASSIGNED Severity: Enhancement Priority: P5 - None Component: System Imaging AssignedTo: ms@suse.com ReportedBy: ms@suse.com QAContact: adrian@suse.com Found By: --- Blocker: ---
We are using /usr/share/kiwi/image/suse-SLE11-JeOS/config.xml for the image creation. When I pinned the kernel-default version (not the latest in the repo), the ovf build has an issue about wrong kernel version for some kernel modules. I then pinned the /usr/share/kiwi/image/vmxboot/suse-SLES11/config.xml, the issue went away.
yes this is correct. I guess you pinned the kernel by a full qualified name in the <package name="..."> setup in suse-SLE11-JeOS/config.xml. now kiwi sent that information to the package manager and if possible this kernel is installed. The next step is to build the boot image (initrd) and the description for it is vmxboot/suse-SLES11/config.xml. In this description the selected kernel is not full qualified and for the moment kiwi does not inherit the full name information you provided over to the boot image description. This is the reason why you need to change both files in order to solve the kernel version conflict. For future versions of kiwi I will introduce a custom kernel profile which will allow you to setup the following: <type ... bootkernel="custom" ...> <packages type="image"/> <package name="kernel-default-3.7.10-1.16.1" bootinclude="true"/> </packages> that way the specified custom or version pinned kernel is automatically used for the boot image (initrd) too because of the bootinclude statement. But again I first have to implement this, it does not yet exist. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846068 https://bugzilla.novell.com/show_bug.cgi?id=846068#c Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Priority|P5 - None |P2 - High -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846068 https://bugzilla.novell.com/show_bug.cgi?id=846068#c1 David Bahi <david.bahi@emc.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |david.bahi@emc.com --- Comment #1 from David Bahi <david.bahi@emc.com> 2013-10-18 20:34:01 UTC --- you know i was thinking the simplest way to do this might be - just to add 'image-path' to the search path for finding boot=<path> - perhaps first even as that way name conflicts would rule in favor of the override. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846068 https://bugzilla.novell.com/show_bug.cgi?id=846068#c2 --- Comment #2 from Marcus Schaefer <ms@suse.com> 2013-10-21 10:04:44 UTC --- yes that will work but it will introduce another source of potential problems which would be very hard to debug because another boot image description was referenced. I hate to say that but as soon as people have started to clone/modify the boot data as it comes from kiwi and reference them by boot="oemboot/my-stuff" they are on their own with problems at boot time ;) my intention is to provide one source of maintained and considered as working boot image descriptions which allows modifications I still can track and reproduce. That's why I think a 'custom' rule with a bootinclude here should be ok and also explains pretty short what will happen -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
https://bugzilla.novell.com/show_bug.cgi?id=846068 https://bugzilla.novell.com/show_bug.cgi?id=846068#c3 Marcus Schaefer <ms@suse.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Resolution| |FIXED --- Comment #3 from Marcus Schaefer <ms@suse.com> 2013-10-21 10:33:43 UTC --- Ok I added the custom profile to the boot images and tested it with a bootincluded kernel-desktop. On build you get information like: Oct-21 11:58:35 <1> : Boot including package(s) [bootstrap]: Oct-21 11:58:35 <1> : --> kernel-desktop .. Oct-21 11:58:35 <1> : Updating Type section Oct-21 11:58:35 <1> : --> bootkernel: custom Hope that's ok. here is the commit commit eb33c9ed6de3bfae7edb4b646f56daa6a66e0150 Author: Marcus Schäfer <ms@suse.de> Date: Mon Oct 21 11:45:51 2013 +0200 - added custom bootkernel profile (bnc #846068) * with the bootkernel="custom" profile one can prevent the installation of a kernel in the kiwi boot image (initrd) This makes sense if a non profiled kernel or a specific version of a kernel is used as part of the system image XML description. Examples: <type ... bootkernel="custom"/> ==> version pinned kernel: <package name="kernel-default-3.7.10-1.16.1" bootinclude="true"/> ==> non profiled/custom kernel: <package name="kernel-bob" bootinclude="true"/> If the custom bootkernel attribute is used it's required to mark the kernel in the system image XML with bootinclude="true" If this is not done the initrd will not have a kernel/modules which is in most cases unwanted -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.
participants (1)
-
bugzilla_noreply＠novell.com