[Bug 1378556] [NEW] Replace the "placeholder" entry in /etc/grub.d/20_linux_xen with the BOOT_IMAGE string

Justin Hahn jeh+launchpad at google.com
Tue Oct 7 22:42:47 UTC 2014


Public bug reported:

For non-Xen kernels,  the BOOT_IMAGE cmdline argument is populated with
the path to the booted kernel image. However, for Xen dom0 kernels, this
is not the case.  Instead there is a "placeholder" cmdline argument. I'd
like to suggest this be changed.

The advantage is this allows scripts to parse /proc/cmdline to determine
the running kernel image in a consistent fashion, regardless of whether
Xen is involved or not.

This amounts to the following one line change:

--- a/20_linux_xen	2014-10-07 15:39:24.545916713 -0700
+++ b/20_linux_xen	2014-10-07 15:41:21.902980904 -0700
@@ -127,7 +127,7 @@
         fi
 	multiboot	${rel_xen_dirname}/${xen_basename} placeholder ${xen_args} \${xen_rm_opts}
 	echo	'$(echo "$lmessage" | grub_quote)'
-	module	${rel_dirname}/${basename} placeholder root=${linux_root_device_thisversion} ro ${args}
+	module	${rel_dirname}/${basename} BOOT_IMAGE=/${basename} root=${linux_root_device_thisversion} ro ${args}
 EOF
   if test -n "${initrd}" ; then
     # TRANSLATORS: ramdisk isn't identifier. Should be translated.

** Affects: grub2 (Ubuntu)
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to grub2 in Ubuntu.
https://bugs.launchpad.net/bugs/1378556

Title:
  Replace the "placeholder" entry in /etc/grub.d/20_linux_xen with the
  BOOT_IMAGE string

Status in “grub2” package in Ubuntu:
  New

Bug description:
  For non-Xen kernels,  the BOOT_IMAGE cmdline argument is populated
  with the path to the booted kernel image. However, for Xen dom0
  kernels, this is not the case.  Instead there is a "placeholder"
  cmdline argument. I'd like to suggest this be changed.

  The advantage is this allows scripts to parse /proc/cmdline to
  determine the running kernel image in a consistent fashion, regardless
  of whether Xen is involved or not.

  This amounts to the following one line change:

  --- a/20_linux_xen	2014-10-07 15:39:24.545916713 -0700
  +++ b/20_linux_xen	2014-10-07 15:41:21.902980904 -0700
  @@ -127,7 +127,7 @@
           fi
   	multiboot	${rel_xen_dirname}/${xen_basename} placeholder ${xen_args} \${xen_rm_opts}
   	echo	'$(echo "$lmessage" | grub_quote)'
  -	module	${rel_dirname}/${basename} placeholder root=${linux_root_device_thisversion} ro ${args}
  +	module	${rel_dirname}/${basename} BOOT_IMAGE=/${basename} root=${linux_root_device_thisversion} ro ${args}
   EOF
     if test -n "${initrd}" ; then
       # TRANSLATORS: ramdisk isn't identifier. Should be translated.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/grub2/+bug/1378556/+subscriptions



More information about the foundations-bugs mailing list