What | Removed | Added |
---|---|---|
CC | gmoro@suse.com | |
Flags | needinfo?(mchang@suse.com) | needinfo?(gmoro@suse.com) |
(In reply to Michal Nowak from comment #5) > (In reply to Gary Ching-Pang Lin from comment #4) > Michael Chang: Perhaps you can help with explaining, why we have "GRUB for > EFI" on JeOS KVM image despite VM may not have UEFI? Not really .. But my speculation is kiwi first boot scripts did not setup /etc/sysconfig/bootloader correctly wrt firmware type being booted. If you use guestfish to inspect the qcow2 image https://openqa.opensuse.org/tests/396373/asset/hdd/openSUSE-Leap-42.3-JeOS-for-kvm-and-xen.x86_64-1.1.1-Build11.33.qcow2 The /etc/sysconfig/bootloader is initially an empty file poised to be written. After the first boot, /etc/sysconfig/bootloader is filled with content below, which looks wrong as its being booted on legacy bios. > LOADER_TYPE="grub2-efi" > LOADER_LOCATION="mbr" > DEFAULT_APPEND=" root=/dev/disk/by-label/ROOT disk=/dev/sda resume=swap systemd.show_status=0 plymouth.enable=0 quiet" > FAILSAFE_APPEND="ide=nodma apm=off noresume edd=off powersaved=off nohz=off highres=off processsor.max+cstate=1 nomodeset x11failsafe root=/dev/disk/by-label/ROOT disk=/dev/sda resume=swap systemd.show_status=0 plymouth.enable=0 quiet" @Guilherme, What do you think ? Thanks, Michael