grub-devel.gnu.org archive mirror
 help / color / mirror / Atom feed
From: PGNet Dev <pgnet.dev@gmail.com>
To: grub-devel@gnu.org
Subject: Grub2 documentation of the GRUB_CMDLINE_*XEN* parameters -- unclear. What's _intended_?
Date: Sat, 21 Nov 2015 16:12:52 -0800	[thread overview]
Message-ID: <56510884.8060908@gmail.com> (raw)

Grub2 documentation @ 
https://www.gnu.org/software/grub/manual/grub.html#Configuration states

	...
	‘GRUB_CMDLINE_XEN’
	‘GRUB_CMDLINE_XEN_DEFAULT’

	    The values of these options are appended to the values of 
‘GRUB_CMDLINE_LINUX’ and ‘GRUB_CMDLINE_LINUX_DEFAULT’ for Linux and Xen 
menu entries.
	‘GRUB_CMDLINE_LINUX_XEN_REPLACE’
	‘GRUB_CMDLINE_LINUX_XEN_REPLACE_DEFAULT’

	    The values of these options replace the values of 
‘GRUB_CMDLINE_LINUX’ and ‘GRUB_CMDLINE_LINUX_DEFAULT’ for Linux and Xen 
menu entries.
	...

 From these docs. it's not clear which values get mapped to which grub 
entries.  One set 'appends', one set 'replaces'.  Are they exclusive of 
one another?

And, what specifically gets mapped to Xen kernel's "options=" parameter 
line?

E.g., a grub2-mkconfig-generated xen*.cfg takes the form

	# disclaimer
	[global]
	#default=

	[config.1]
	options= dom0_mem= ...
	kernel=vmlinuz-4.3.0-16.gff1dcd9-xen ...
	ramdisk=initrd-4.3.0-16.gff1dcd9-xen ...

whereas for a NON-xen grub*.cfg

	# disclaimer
	[global]
	#default=

	[config.1]
	kernel=vmlinuz-4.3.0-16.gff1dcd9-default ...
	ramdisk=initrd-4.3.0-16.gff1dcd9-default ...

there's NO "options=..." line.

The docs should clearly address which PARAMETERS map to the "options=" 
line, and which to the kernel=" line in the Xen case.

To get there -- What's intended, by designn, from development in these 
specific *XEN* cases?


             reply	other threads:[~2015-11-22  0:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22  0:12 PGNet Dev [this message]
2015-11-22  6:37 ` Grub2 documentation of the GRUB_CMDLINE_*XEN* parameters -- unclear. What's _intended_? Andrei Borzenkov
2015-11-22 15:00   ` PGNet Dev
2015-11-22 19:54 ` Colin Watson
2015-11-22 20:41   ` PGNet Dev

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=56510884.8060908@gmail.com \
    --to=pgnet.dev@gmail.com \
    --cc=grub-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).