From: Andrei Borzenkov <arvidjaar@gmail.com>
To: The development of GNU GRUB <grub-devel@gnu.org>
Subject: Re: Grub2 documentation of the GRUB_CMDLINE_*XEN* parameters -- unclear. What's _intended_?
Date: Sun, 22 Nov 2015 09:37:43 +0300 [thread overview]
Message-ID: <565162B7.7000000@gmail.com> (raw)
In-Reply-To: <56510884.8060908@gmail.com>
22.11.2015 03:12, PGNet Dev пишет:
> 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.
That's not what current manual says. Please use current upstream sources
when you contact upstream.
> ‘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.
I agree it is a bit fuzzy. If set, it is used for Linux kernel arguments
in Xen menu entries. Care to send a patch clarifying it?
> ...
>
> 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
>
Please direct this question to your distribution. For a start, there is
no grub2-mkconfig upstream.
> # 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 ...
>
I have no idea what you are talking about, sorry. Again, you need to
direct this question to your distribution.
> 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?
>
> _______________________________________________
> Grub-devel mailing list
> Grub-devel@gnu.org
> https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2015-11-22 6:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-11-22 0:12 Grub2 documentation of the GRUB_CMDLINE_*XEN* parameters -- unclear. What's _intended_? PGNet Dev
2015-11-22 6:37 ` Andrei Borzenkov [this message]
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=565162B7.7000000@gmail.com \
--to=arvidjaar@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.