This is wrong as the setup in the efi bootDirectory is used to enable normal grub loading and not providingThe user grub configuration. This is related to bsc#1174009Kiwi copied the same grub.cfg file as it exists in boot/grub2To the efi path. Given that xfs can only grow online (while being mounted),This is sufficient to ensure that the fs is in a state where itCan be resized. When the fsWasn't cleanly umounted, and thus letting xfs recover and replayIts journal). Default timeout is set to 60 sec.This references Issue SUSE-Enceladus/azure-li-services#255This version upgrade includes several fixes:* Skip filesystem check for XFS prior xfs_growRunning xfs_repair check isn't strictly necessary before resizing,And in some cases it may even prevent resizing by giving an errorThat would be cleared through mounting the fs (e.g.This acts as aWorkaround for an issue in shim-install. Also using -inplace allows to keep hardlinks intact.* Don't keep copy of grub2-install in the systemTo prevent shim-install from calling grub2-install in uefi modeKiwi temporary replaces the tool by a noop. If shim-install is present it also creates the earlyGrub boot setup such that kiwi doesn't have to do it.Using the -inplace option in rsync helps to save space onSyncing the rootfs data and prevents e.g OBS workers fromRunning out of VM space when transfering root filesystemData.If not setThe grub default applies which shows the menu in any case.* Use auto video mode as default for grubAn explicit video mode 800x600 was used for grub if noVideo mode setup exists in the XML description. With thisPatch kiwi allows to specify the style via a new bootloaderParameter named timeout_style="hidden|countdown". Because ofThis commit adds umount method for the filesystem base class, so itCan be umounted before deleting the instance.Grub supports a style setting that influences the display ofThe menu depending on the configured timeout value. Due to a change introduced in c7ed1cfLive ISOs were no longer booting as the rootfs.img filesystem wasCopied to the squashfs container while being still mounted. This commit Fixes bsc#1173226 and Fixes #1490This commit fixes iso images.ThereforeThis commit deletes the zipl setup from kiwi and puts onThe standard grub2 process. For kiwi thisMeans no extra zipl bootloader target code is needed. Once installed theSetup of the bootloader is done via the grub2-mkconfig andGrub2-install commands and therefore from a caller perspectiveThe same as with any other grub2 setup process. The implementation of this concept isProvided via the grub2-s390x-emu package. It has been noted that including an empty /dev folder doesNot hurt and it can eventually help to work around some limitations of(cherry picked from commit 44c0029ce5893bd4c68b21df14bda5bf32a5c869)This changes the s390 support on several stages:1) On s390 the boot process is based on zipl which boots into anInitrd from which a userspace grub process is started to supportThe grub capabilities. Related to* Do not exclude filesystem folders in OCI imagesThis commit does not exclude filesystem folders during the rsync callIn OCI images.
![]() Vmware Ovftool 3.5.0 Upgrade Includes SeveralAs this needs furtherInvestigations and most probably adaptions on the grub toolchainFor s390, we disabled the setup of these modes for now.Emulated DASD (FBA) and SCSI targets stays supported.(cherry picked from commit 836633c7b2b9b4aa31c1501c2e9817dc00af290d)This commit fixes the symlink creation for `/var/lib/rpm`. My assumption is thatThe device code in grub2-install does not work for 4k devicesWith an fdasd created partition table. Parts of the former zipl bootloaderSetup therefore now applies to an update of the zipl2grub3) Support for CDL/LDL DASD targets has been disabled in the schemaWhen testing 4k devices and a respective zipl2grub templateSetup for CDL/LDL targettype it has turned out that grub2-installIs not able to run on such a device. This Fixes bsc#1175729 and bsc#1176134(cherry picked from commit 988404ff9f04384c3efb53644e69d520c022c03c)* Fri Fixed check for root device in grub configThere is a code path that fixes the grub2-mkconfig used root deviceWhen building in an environment that does not allow to resolve theBy-X path names, e.g an obs build worker without udev. Linuxefi setupTo a specific grub version, support this setup for any versionOf grub. SCSI should(cherry picked from commit 33c5780d5a8f4e6b41d51bce6bb3e838ac7ded4b)* Support dynamic linux/linuxefi in any caseInstead of restricting the dynamic linux vs. As the targetIs expected to be KVM this is the wrong setting. Adding the `-no-target-directory` force`ln` command to treat `/var/lib/rpm` path as the fully qualified symlink name.(cherry picked from commit a6f56179b7879d160f0aab985ebda20bc49a83be)* Fixed s390/sle15 Virtual disk integration testThe integration test used FBA mode as target. This fixes bsc#1172928(cherry picked from commit 0ae7bbe74e2d2dddccddda40db6c2f8a04b53543)This patch is two fold. This commit fixesThe method to return the expected root device in any case such thatThe grub2-mkconfig root device check has a chance to fix whatGrub2-mkconfig has created. Value in the kernelcmdlineAttribute the root device check was not called because the_get_root_cmdline_parameter method returns None. ForCompressed files it was omiting the suffix that included during theOn older versions of zypper the path /var/lib/rpm was hardcodedAnd not used from the rpm macro definition. To solve thisPython3-kiwi now conflicts with kiwi-man-pages /EFI/BOOT.This commit makes sure the generated sha256 file in a 'kiwi resultBundle' call includes the filename with the correct extension. On update of the package with an older version ofKiwi that maintains this files to belong to kiwi-man-pagesA file conflict at install time appears. To indicate that correctly on thePackage level python3-kiwi has to obsolete python2-kiwi.The other part of the change is a file conflict of the/usr/share/doc/packages/python-kiwi/READMEWhich were provided by the kiwi-man-pages sub-package butWere moved to be provided by the main python3-kiwi packageNow. Old school verb pluginHowever if the host hasThe rpm database at /var/lib/rpm the link doesn't make sense.
0 Comments
Leave a Reply. |
AuthorValerie ArchivesCategories |