From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1a0bQw-0008Ex-0a for mharc-grub-devel@gnu.org; Sun, 22 Nov 2015 15:40:26 -0500 Received: from eggs.gnu.org ([2001:4830:134:3::10]:50044) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a0bQt-0008Er-4Q for grub-devel@gnu.org; Sun, 22 Nov 2015 15:40:24 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1a0bQp-00067g-TC for grub-devel@gnu.org; Sun, 22 Nov 2015 15:40:23 -0500 Received: from mail-pa0-x22f.google.com ([2607:f8b0:400e:c03::22f]:36174) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1a0bQp-00067c-MQ for grub-devel@gnu.org; Sun, 22 Nov 2015 15:40:19 -0500 Received: by pacdm15 with SMTP id dm15so170048959pac.3 for ; Sun, 22 Nov 2015 12:40:18 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=subject:references:to:from:reply-to:message-id:date:user-agent :mime-version:in-reply-to:content-type:content-transfer-encoding; bh=7m8GGgG90IyFm6Q2p5UTUWcxaW/M03HhR4wK+wvy5EU=; b=ruf2o0oJvR88p8tMqjD0L5RkDlfa74opWijv7PqEtpT39gwbBOl1tPyLxfHjPxQ3m1 vvy/FJtRvQ5A4M0/3pkEXiJlzNFG/gGLQdJ8xknyKQUyXACGyfhy6NzJJn1IEU/Gjqwj gV/m/34Wt3xP9L4Hc+HuwevkzN9UPCF9JLwr4tssRFrktO8QFGUinEHHai7fhvQlz1b2 r6kn9eWvsgjbO3KaOGf5dsRheQePUYOlntbap+0k98PmKs+HZeKKBGJAT0fZdi7Dfm/C REcFp9kcuwt4jDgIvY11onPU3dB3jQu1+RQLd0OHlNMh9lkbSY8udk8r1Ac/amDjJAbz EMWQ== X-Received: by 10.98.80.22 with SMTP id e22mr12125859pfb.34.1448224818673; Sun, 22 Nov 2015 12:40:18 -0800 (PST) Received: from deskEdgar.presence-group.net (99-7-172-215.lightspeed.snmtca.sbcglobal.net. [99.7.172.215]) by smtp.gmail.com with ESMTPSA id vu7sm3627310pbc.11.2015.11.22.12.40.17 for (version=TLS1_2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128); Sun, 22 Nov 2015 12:40:18 -0800 (PST) Subject: Re: Grub2 documentation of the GRUB_CMDLINE_*XEN* parameters -- unclear. What's _intended_? References: <56510884.8060908@gmail.com> <20151122195437.GB4982@riva.ucam.org> To: grub-devel@gnu.org From: PGNet Dev Message-ID: <56522860.5000301@gmail.com> Date: Sun, 22 Nov 2015 12:41:04 -0800 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:42.0) Gecko/20100101 Thunderbird/42.0 MIME-Version: 1.0 In-Reply-To: <20151122195437.GB4982@riva.ucam.org> Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 7bit X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2607:f8b0:400e:c03::22f X-BeenThere: grub-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list Reply-To: The development of GNU GRUB List-Id: The development of GNU GRUB List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 22 Nov 2015 20:40:24 -0000 On 11/22/2015 11:54 AM, Colin Watson wrote: > No, they aren't exclusive of one another, but are used to construct > different command lines. GRUB_CMDLINE_XEN* are used for the hypervisor > command line; GRUB_CMDLINE_LINUX_XEN_REPLACE* are used for the Linux > kernel command line (but if unset, the corresponding GRUB_CMDLINE_LINUX* > values are used instead). > > The misleading description you quote was the one in 2.00, but was > clarified in git a while ago: > > http://git.savannah.gnu.org/cgit/grub.git/commit/?id=48f39bb4df5b903aaa66db9fdc6679571bff0dd9 That's exactly the helpful clarification needed. Thanks! It'd be useful to have that updated on the grub2 website's docs -- it's just as valid there. >> And, what specifically gets mapped to Xen kernel's "options=" parameter >> line? >> >> E.g., a grub2-mkconfig-generated xen*.cfg takes the form > Upstream grub-mkconfig does not generate xen*.cfg at all. This is an > openSUSE-specific patch. From inspecting their source code, I believe > that the GRUB_CMDLINE_XEN* options will apply here. I'd realized that there's different naming, e.g. the "grub2-mkconfig", but had not realized this^^ diff as well. >> The docs should clearly address which PARAMETERS map to the "options=" line, >> and which to the kernel=" line in the Xen case. > > No doubt, but it is up to the openSUSE maintainers to make sure that Noted. The latest upgrade of the distro has proven to be quite problematic, particularly in the real-world/modern { pv-kernel + Xen + Grub2 + EFI } use case; and the docs are a bit of a mess. I'd _strongly_ prefer a grub2 instance closer to upstream's. Not yet sure what replacing the distro's with a 'clean' upstream build entails ... Thanks again for the response.