
By default, we attempt to inject a serial console, which may, or may not be needed, for example, Centos Stream 9 cloud images already configure a console setting, and repeating it just might be undesirable and cause workload performance degredation if the kernel or an application has to report anything to a console. This change generally results in original console entries being preserved, which might actually be a bug and get fixed in a latter patch. Generally, users of dib *should* likely be specific what they want to do with their console setting, and without setting the new DIB_BOOTLOADER_USE_SERIAL_CONSOLE paramter to false, the default will be adhered to, and any pre-existing serial console entries will *not* be de-duplicated from the base image. That too is *likely* a bug, but a harder one to fix. Change-Id: Icdfb5ed021b1a91e2de3c9a22bb2ff7fe9882bcd
12 lines
629 B
Plaintext
12 lines
629 B
Plaintext
export DIB_BOOTLOADER_DEFAULT_CMDLINE=${DIB_BOOTLOADER_DEFAULT_CMDLINE:-"nofb nomodeset gfxpayload=text"}
|
|
export DIB_BOOTLOADER_SERIAL_CONSOLE=${DIB_BOOTLOADER_SERIAL_CONSOLE:-""}
|
|
if [ ! -v DIB_BOOTLOADER_VIRTUAL_TERMINAL ]; then
|
|
# DIB_BOOTLOADER_VIRTUAL_TERMINAL is unset
|
|
export DIB_BOOTLOADER_VIRTUAL_TERMINAL=tty0
|
|
else
|
|
# DIB_BOOTLOADER_VIRTUAL_TERMINAL is set to empty string or other value
|
|
export DIB_BOOTLOADER_VIRTUAL_TERMINAL=${DIB_BOOTLOADER_VIRTUAL_TERMINAL}
|
|
fi
|
|
export DIB_NO_TIMER_CHECK=${DIB_NO_TIMER_CHECK:-"True"}
|
|
export DIB_BOOTLOADER_USE_SERIAL_CONSOLE=${DIB_BOOTLOADER_USE_SERIAL_CONSOLE:-"True"}
|