[opensuse-virtual] after changes to 'xen.cfg' on a grub2 chainloaded Xen instance, what addl steps (mkconfig? mkinitrd? cp?) need to be exec'd?
I boot Xen on UEFI + grub2. uname -rm 3.19.4-1.g74c332b-xen x86_64 rpm -qa | grep -i xen-4 xen-4.5.0_03-367.1.x86_64 Xen is chainloaded from grub2 config cat /boot/grub2/custom.cfg menuentry 'xen' { ... chainloader /efi/xen/xen.efi } cat /boot/efi/efi/xen/xen.cfg [global] default=xen [xen] options=... kernel=vmlinuz-xen ... ramdisk=initrd-xen ... each time a change is made to 'xen.cfg' which of these steps need to be executed to propagate fully to next boot? grub2-mkconfig -o /boot/grub2/grub.cfg mkinitrd /bin/cp -f /usr/lib64/efi/xen.efi /boot/vmlinuz-xen /boot/initrd-xen /boot/efi/efi/xen/ all of them? in that order? LT -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Wed, Apr 22, lyndat3@your-mail.com wrote:
each time a change is made to 'xen.cfg' which of these steps need to be executed to propagate fully to next boot?
Isnt xen.cfg just the config file used by xen.efi? In that sense is independent from any of the steps you mentioned. Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On 23.04.15 at 07:26, <olaf@aepfle.de> wrote: On Wed, Apr 22, lyndat3@your-mail.com wrote:
each time a change is made to 'xen.cfg' which of these steps need to be executed to propagate fully to next boot?
Isnt xen.cfg just the config file used by xen.efi? In that sense is independent from any of the steps you mentioned.
Exactly. Unless the change to xen.cfg involves renaming of any of the to be loaded files, no other step should be needed. Jan -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
On Thu, Apr 23, Jan Beulich wrote:
On 23.04.15 at 07:26, <olaf@aepfle.de> wrote: On Wed, Apr 22, lyndat3@your-mail.com wrote:
each time a change is made to 'xen.cfg' which of these steps need to be executed to propagate fully to next boot?
Isnt xen.cfg just the config file used by xen.efi? In that sense is independent from any of the steps you mentioned.
Exactly. Unless the change to xen.cfg involves renaming of any of the to be loaded files, no other step should be needed.
Perhaps 'xen.efi' was meant. In that case nothing needs to be done, other than copying the new file into the relevant location, AFAIK. Olaf -- To unsubscribe, e-mail: opensuse-virtual+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-virtual+owner@opensuse.org
participants (3)
-
Jan Beulich -
lyndat3＠your-mail.com -
Olaf Hering