On Mon, Apr 13, 2015, at 12:34 AM, Jan Beulich wrote:

...

(2) If the Xen install doesn't populate xen.efi into that directory, then at every Xen update/upgrade, will xen.efi need to be re-copied manually?

... yes, albeit the grub scripts should be taking care of this as long as there's a reference to the image from other than custom.cfg.

Here that's not the case. Only a single reference exists cd /boot egrep -rlni "xen\.efi|xen\.cfg" . ./grub2/custom.cfg custom.cfg is of course sourced, cat /etc/grub.d/41_custom #!/bin/sh cat <

On Mon, Apr 13, 2015, at 06:47 AM, Jan Beulich wrote:

...

If the goal is to have the updating done automatically, where 'other than custom.cfg' should that config be placed?

That's the wrong question to ask: When you want a non-auto- generated entry, it needs to go there. Yet what gets copied automatically is (afaik) only what is needed for auto-generated entries.

...

Or should the grub scripts be modified to handle it?

Perhaps that would be possible, but I can't judge whether that would also make sense from a conceptual perspective.

I'm not thrilled with grub2 to begin with -- more trouble than it's worth, especially when specific, non auto-generated customizations need to be in place. But it's the standard install, and needs to be dealt with. Looking at the grub scripts, it's a mess in there. I'm thinking that leaving custom.cfg alone, and non-auto-generated, is the right thing to do. The issue arises in this case only after kernel-xen or Xen updates. Figuring out how to hook zypper so that "if kernel-xen or Xen has just been updated then copy new xen.efi to EFI boot partition re-exec grub2-mkconfig re-exec mkinitrd " Just automating what I'm doing manually, instead of trying to mangle grub2, might be a simpler approach. -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org