http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c1 --- Comment #1 from Michael Chang --- Created attachment 656334 --> http://bugzilla.suse.com/attachment.cgi?id=656334&action=edit debug patch Could you please give attached patch a shot ? Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |rw@suse.com -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c2 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags|needinfo?(9b3e05a5@opayq.co | |m) | --- Comment #2 from boo35 boo35 <9b3e05a5@opayq.com> --- With the patch applied, ls -al /boot/efi/EFI/opensuse (empty) grub2-mkconfig ... ### END /etc/grub.d/10_linux ### ### BEGIN /etc/grub.d/20_linux_xen ### Found hypervisor: /boot/xen-4.6.0_02-397.gz Found linux image: /boot/vmlinuz-4.3.0-4.g734b32c-xen Found initrd image: /boot/initrd-4.3.0-4.g734b32c-xen menuentry 'openSUSE Leap 42.1, with Xen hypervisor' --class opensuse --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-simple-4716053b-39da-4cc1-a7ce-72171b862357' { echo 'Loading Xen 4.6.0_02-397 with Linux 4.3.0-4.g734b32c-xen ...' chainloader $cmdpath/xen-4.6.0_02-397.efi xen-4.6.0_02-397.efi config.1 } submenu 'Advanced options for openSUSE Leap 42.1 (with Xen hypervisor)' $menuentry_id_option 'gnulinux-advanced-4716053b-39da-4cc1-a7ce-72171b862357' { submenu 'Xen hypervisor, version 4.6.0_02-397' $menuentry_id_option 'xen-hypervisor-4.6.0_02-397-4716053b-39da-4cc1-a7ce-72171b862357' { menuentry 'openSUSE Leap 42.1, with Xen 4.6.0_02-397 and Linux 4.3.0-4.g734b32c-xen' --class opensuse --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-4.3.0-4.g734b32c-xen-advanced-4716053b-39da-4cc1-a7ce-72171b862357' { echo 'Loading Xen 4.6.0_02-397 with Linux 4.3.0-4.g734b32c-xen ...' chainloader $cmdpath/xen-4.6.0_02-397.efi xen-4.6.0_02-397.efi config.2 } menuentry 'openSUSE Leap 42.1, with Xen 4.6.0_02-397 and Linux 4.3.0-4.g734b32c-xen (recovery mode)' --class opensuse --class gnu-linux --class gnu --class os --class xen $menuentry_id_option 'xen-gnulinux-4.3.0-4.g734b32c-xen-recovery-4716053b-39da-4cc1-a7ce-72171b862357' { echo 'Loading Xen 4.6.0_02-397 with Linux 4.3.0-4.g734b32c-xen ...' chainloader $cmdpath/xen-4.6.0_02-397.efi xen-4.6.0_02-397.efi failsafe.3 } } } ### END /etc/grub.d/20_linux_xen ### ... done ls -al /boot/efi/EFI/opensuse -rwxrwxr-x 1 root root 297 Nov 18 06:13 grub.xen-files* -rwxrwxr-x 1 root root 16M Nov 16 16:56 initrd-4.3.0-4.g734b32c-xen* -rwxrwxr-x 1 root root 5.1M Nov 15 03:48 vmlinuz-4.3.0-4.g734b32c-xen* -rwxrwxr-x 1 root root 2.6K Nov 18 06:13 xen-4.6.0_02-397.cfg* -rwxrwxr-x 1 root root 2.1M Nov 11 13:18 xen-4.6.0_02-397.efi* No errors in the `mkinitrd` process ... I'll convert my custom xen.cfg -> xen.efi, and configure grub.cfg defaults and check boot with these gen'd files in a bit. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c4 --- Comment #4 from boo35 boo35 <9b3e05a5@opayq.com> --- fyi, at the EFI shell Shell> Shell>fs0: fs0:\>dir Directory of: fs0:\ 03/28/15 04:20a <DIR> 0 EFI 0 File(s) 0 bytes 1 Dir(s) fs0:\> cd EFI fs0:\EFI> of: fs0:\EFI 03/24/15 09:30p <DIR> 0 . 03/24/15 09:30p <DIR> 0 .. 11/18/15 06:22a <DIR> 0 opensuse 11/18/15 06:23a <DIR> 0 XEN 0 File(s) 0 bytes 4 Dir(s) fs0:\EFI> dir opensuse Directory of: fs0:\EFI\opensuse 03/24/15 09:30p <DIR> 0 . fs0:\EFI> 09:30p <DIR> 0 .. 11/18/15 06:22a 2,571 xen-4.6.0_02-397.cfg 11/18/15 06:23a 297 grub.xen-files 11/11/15 01:18p 2,181,208 xen-4.6.0_02-397.efi 11/15/15 03:48a 5,249,728 vmlinuz-4.3.0-4.g734b32c-xen 11/18/15 06:22a 16,140,876 initrd-4.3.0-4.g734b32c-xen 5 File(s) 23,574,680 bytes 2 Dir(s) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c6 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Flags| |needinfo?(mchang@suse.com) --- Comment #6 from boo35 boo35 <9b3e05a5@opayq.com> --- I'm trying to remove Xen from the equation, see if I can get back to a working network. Even though both Xen & !Xen kernels are installed rpm -qa | grep -i "kernel-xen|kernel-default" kernel-default-4.3.0-4.1.g734b32c.x86_64 kernel-xen-4.3.0-4.1.g734b32c.x86_64 ls -al /boot/vmlinuz* lrwxrwxrwx 1 root root 32 Nov 16 16:37 /boot/vmlinuz -> vmlinuz-4.3.0-4.g734b32c-default -rw-r--r-- 1 root root 5.7M Nov 15 04:50 /boot/vmlinuz-4.3.0-4.g734b32c-default -rw-r--r-- 1 root root 5.1M Nov 15 03:48 /boot/vmlinuz-4.3.0-4.g734b32c-xen lrwxrwxrwx 1 root root 28 Nov 16 16:41 /boot/vmlinuz-xen -> vmlinuz-4.3.0-4.g734b32c-xen `grub2-mkconfig` is failing to create efi for BOTH xen & non-xen instances. Instead only for xen -- the running kernel, ls -al /boot/efi/EFI/opensuse/ total 23M drwxrwxr-x 2 root root 4.0K Nov 18 13:38 ./ drwxrwxr-x 4 root root 4.0K Mar 28 2015 ../ -rwxrwxr-x 1 root root 297 Nov 18 13:39 grub.xen-files* -rwxrwxr-x 1 root root 16M Nov 18 13:38 initrd-4.3.0-4.g734b32c-xen* -rwxrwxr-x 1 root root 5.1M Nov 15 03:48 vmlinuz-4.3.0-4.g734b32c-xen* -rwxrwxr-x 1 root root 2.6K Nov 18 13:39 xen-4.6.0_02-397.cfg* -rwxrwxr-x 1 root root 2.1M Nov 11 13:18 xen-4.6.0_02-397.efi* EFI configs & boot-binaries for *all* installed kernels should be installed, no? -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c8 --- Comment #8 from Michael Chang --- We don't and are not possible to configure startup.nsh, it's in your setup only. And the broken network is a separate problem to the original report. Thanks. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c10 --- Comment #10 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Michael Chang from comment #8)

We don't and are not possible to configure startup.nsh, it's in your setup only.

Then the user must create/edit startup.nsh at every version change of the created xen.efi? Or is there a different method -- static naming, creation of a generic-named symlink, etc. ?

And the broken network is a separate problem to the original report.

I'll separate it. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c12 --- Comment #12 from boo35 boo35 <9b3e05a5@opayq.com> ---

Please answer each of my question in comment #7. Without information from you that allows us to understand where the problem is we cannot fix it.

Please explain what actually happens.

Once again: I boot the machine. It starts up, I'm dropped to the EFI shell. I see the shell prompt, ">Shell" Nothing else happens,

Do you see GRUB menu?

No

Do you see menu entry for Xen?

NO, since I don't see the GRUB menu.

What happens when you select this menu entry?

Unknown, since it's not seen. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c14 --- Comment #14 from boo35 boo35 <9b3e05a5@opayq.com> --- I'd set efibootmgr -c -d /dev/sdg -p 2 -l \\EFI\\opensuse\\xen-4.6.0_02-397.efi -L OpenSuse-Xen efibootmgr -c -d /dev/sdg -p 2 -l \\EFI\\XEN\\xen.efi -L Custom-Xen efibootmgr BootOrder: 0001,0000 Boot0000* OpenSuse-Xen Boot0001* Custom-Xen efibootmgr -o 0,1 efibootmgr BootOrder: 0000,0001 Boot0000* OpenSuse-Xen Boot0001* Custom-Xen and, checking BIOS settings on startup, can verify/select those items in the available EFI direct-overrides list. However, after reboot, efibootmgr -v (empty) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c16 --- Comment #16 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Andrei Borzenkov from comment #15)

Is secure boot enabled?

No

How did you boot before?

As outlined in the OP. I used my own-generated xen.efi, since Opensuse's support didn't work. I had NO startup.nsh. It was not necessary. With my .efi, and Opensuse 13.2, boot simply worked -- exactly as expected.

What has changed?

I upgraded to Opensuse Leap, and now use the Opensuse-generated efi The upgrade changed grub -- 20_linux was modified to "handled" efi. The upgrade broke grub, requiring the patch, above. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c18 --- Comment #18 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Andrei Borzenkov from comment #17)

(In reply to boo35 boo35 from comment #14)

...

I'd set

efibootmgr -c -d /dev/sdg -p 2 -l \\EFI\\opensuse\\xen-4.6.0_02-397.efi -L OpenSuse-Xen

Why? If you are going to use custom entries why do you need to use grub2 in the first place?

Because the system as upgraded is broken, and fails to boot. Adding the efibootmgr entries was one of the steps along the way to getting this system to boot at all ... the other being the startup.nsh. Obviously, as I'm able to boot, the workaround worked. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c20 --- Comment #20 from boo35 boo35 <9b3e05a5@opayq.com> ---

Please run update-bootloader --reinit;

efibootmgr -v (empty) ls -alR /boot/grub2/grub.cfg -rw------- 1 root root 8.5K Nov 19 09:50 /boot/grub2/grub.cfg update-bootloader --reinit

it should reinstall GRUB/shim (whatever is set in configuration) and recreate grub.cfg.

ls -alR /boot/grub2/grub.cfg -rw------- 1 root root 8.5K Nov 19 09:54 /boot/grub2/grub.cfg ls -l /boot/efi /boot/efi/EFI/opensuse /boot/efi: total 8.0K drwxrwxr-x 4 root root 4.0K Mar 28 2015 EFI/ -rwxrwxr-x 1 root root 42 Nov 18 13:58 startup.nsh* /boot/efi/EFI/opensuse: total 23M -rwxrwxr-x 1 root root 297 Nov 19 09:54 grub.xen-files* -rwxrwxr-x 1 root root 133K Nov 19 09:53 grubx64.efi* -rwxrwxr-x 1 root root 16M Nov 19 09:49 initrd-4.3.0-4.g734b32c-xen* -rwxrwxr-x 1 root root 5.1M Nov 15 03:48 vmlinuz-4.3.0-4.g734b32c-xen* -rwxrwxr-x 1 root root 3.2K Nov 19 09:54 xen-4.6.0_02-397.cfg* -rwxrwxr-x 1 root root 2.1M Nov 11 13:18 xen-4.6.0_02-397.efi*

Show efibootmgr -v immediately before reboot.

efibootmgr -v BootOrder: 0000 Boot0000* opensuse HD(2,1000,96000,6196ccc5-1e27-48e6-8372-2e64118e5d03)File(\EFI\opens)

What happens after reboot then? shutdown -r now ...

The system drops to the EFI Shell, waits a few seconds then autoproceeds ... blk1D :BlockDevice - Alias (null) PciRoot(0x0)/Pci(0x1f,0x2)/Sata(0x5,0x0) Press ESC in 1 seconds to skip startup.nsh, any other key to continue. startup.nsh> fs0:\EFI\XEN\xen.efi Xen 4.6.0_02-397 (c/s ) EFI loader Using configuration file 'xen.cfg' vmlinuz-xen: 0x000000002beee000-0x000000002c3efac0 initrd-xen: 0x000000002af8e000-0x000000002beed74c 0x0000:0x00:0x19.0x0: ROM: 0x10000 bytes at 0x329c6018 0x0000:0x04:0x00.0x0: ROM: 0x8000 bytes at 0x329b6018 0x0000:0x10:0x00.0x0: ROM: 0x10800 bytes at 0x3299e018 __ __ _ _ __ ___ ___ ____ _____ ___ _____ \ \/ /___ _ __ | || | / /_ / _ \ / _ \___ \ |___ // _ \___ | \ // _ \ '_ \ | || |_| '_ \| | | | | | | |__) |__ |_ \ (_) | / / / \ __/ | | | |__ _| (_) | |_| | | |_| / __/|__|__) \__, |/ / /_/\_\___|_| |_| |_|(_)___(_)___/___\___/_____| |____/ /_//_/ |_____| (XEN) Xen version 4.6.0_02-397 (abuild@suse.de) (gcc (SUSE Linux) 4.8.5) debug=n Tue Nov 10 5 ... to a system login Welcome to openSUSE Leap 42.1 - Kernel 4.3.0-4.g734b32c-xen (xvc0). xensvr login: I never see a GRUB menu. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c22 --- Comment #22 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Michael Chang from comment #8)

We don't and are not possible to configure startup.nsh, it's in your setup only. And the broken network is a separate problem to the original report. Thanks.

If I remove "my" startup.nsh, the system neither creates one, nor boots without it. It *still* simply drops to EFI Shell prompt -- and sits. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c24 --- Comment #24 from boo35 boo35 <9b3e05a5@opayq.com> --- (In reply to Andrei Borzenkov from comment #23)

Can you set any variable permanently from EFI shell?

setvar foo -bs -rt -nv ="bar"

Shell> setvar foo -bs -rt -nv ="bar" 'setvar' is not recognized as an internal or external command, operable program, or batch file Which specific command do you want? Shell> ? - Displays the EFI Shell command list or verbose command help alias - Displays, creates, or deletes EFI Shell aliases attrib - Displays or changes the attributes of files or directories cd - Displays or changes the current directory cls - Clears standard output and optionally changes background color comp - Compares the contents of two files connect - Connects one or more EFI drivers to a device cp - Copies one or more files or directories to another location date - Displays or changes the current system date dblk - Displays one or more blocks from a block device devices - Displays the list of devices managed by EFI drivers devtree - Displays the EFI Driver Model compliant device tree dh - Displays EFI handle information disconnect - Disconnects one or more EFI drivers from a device dmem - Displays the contents of memory dmpstore - Displays all EFI NVRAM variables dp - Displays perofmance data drivers - Displays the EFI driver list drvcfg - Invokes the Driver Configuration Protocol drvdiag - Invokes the Driver Diagnostics Protocol echo - Controls batch file command echoing or displays a message edit - Full screen editor for ASCII or UNICODE files eficompress - Compress a file efidecompress - Decompress a file err - Displays or changes the error level exit - Exits the EFI Shell environment for - Executes commands for each item in a set of items goto - Forces batch file execution to jump to specified location guid - Displays all registered EFI GUIDs help - Displays the EFI Shell command list or verbose command help hexedit - Full screen hex editor if - Executes commands in specified conditions ifconfig - Modify the default IP address of UEFI network stack ipconfig - Displays or modifies the current IP configuration load - Loads and optionally connects one or more EFI drivers loadpcirom - Loads a PCI Option ROM ls - Displays a list of files and subdirectories in a directory map - Displays or defines mappings mem - Displays the contents of memory memmap - Displays the memory map mkdir - Creates one or more directories mm - Displays or modifies MEM/MMIO/IO/PCI/PCIE address space mode - Displays or changes the console output device mode mount - Mounts a file system on a block device mv - Moves one or more files or directories to another location openinfo - Displays the protocols and agents associated with a handle pause - Prints a message and waits for keyboard input pci - Displays PCI device list or PCI function configuration space ping - Ping a target machine with UEFI network stack reconnect - Reconnects one or more EFI drivers to a device reset - Resets the system rm - Deletes one or more files or directories sermode - Sets serial port attributes set - Displays or modifies EFI Shell environment variables shift - Shifts batch file input parameter positions smbiosview - Displays SMBIOS information stall - Stalls the processor for the specified number of microseconds telnetmgmt - Change terminal type time - Displays or changes the current system time timezone - Displays or sets time zone information touch - Updates filename timestamp with current system date and time type - Displays file contents unload - Unloads a EFI driver ver - Displays EFI Firmware version information vol - Displays or changes a file system volume label Shell> ver EFI Specification Revision : 2.31 EFI Vendor : American Megatrends EFI Revision : 4.655 -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c26 --- Comment #26 from Michael Chang --- (In reply to Andrei Borzenkov from comment #19)

The problem you reported is fixed. The problem you discuss now does not appear to be related to Leap bootloader, because you have problems with manually created boot entries, and Leap bootloader is not involved in any way. I leave it to Michael, but I tend to think this bug should be closed as resolved.

I second with yours. The reported issue was fixed. WE can resolve this one as fixed. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c28 boo35 boo35 <9b3e05a5@opayq.com> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|FIXED |WONTFIX --- Comment #28 from boo35 boo35 <9b3e05a5@opayq.com> --- The fact remains ... Start with a working v13.2 server as described. Run the 13.2 -> Leap upgrade. execute grub2-mkconfig to generated a new config reboot the machine. you will still drop to an EFI shell, and go no further -- as reported. That's WONTFIX at best. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c33 --- Comment #33 from boo35 boo35 <9b3e05a5@opayq.com> ---

By looking into your efibootmgr outputs, it seems there's a truncated path "\EFI\opens" that points to nothing exist on your ESP.

efibootmgr -v BootOrder: 0000 Boot0000* opensuse HD(2,1000,96000,6196ccc5-1e27-48e6-8372-2e64118e5d03)File(\EFI\opens)

Is it a typo ? If not it could be a bug somewhere in efibootmgr/kernel/EFI runtime (variable) service.

No, not a typo ... just copy-n-paste from serial-console output. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |maint-coord@suse.de Flags| |needinfo?(maint-coord@suse. | |de) -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.suse.com/show_bug.cgi?id=955493 http://bugzilla.suse.com/show_bug.cgi?id=955493#c41 Michael Chang changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nmunoz@suse.com --- Comment #41 from Michael Chang --- *** Bug 957870 has been marked as a duplicate of this bug. *** -- You are receiving this mail because: You are on the CC list for the bug.