From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from list by lists.gnu.org with archive (Exim 4.71) id 1YqfES-00039g-3i for mharc-grub-devel@gnu.org; Fri, 08 May 2015 06:10:12 -0400 Received: from eggs.gnu.org ([2001:4830:134:3::10]:45033) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YqfEO-000380-PN for grub-devel@gnu.org; Fri, 08 May 2015 06:10:09 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1YqfEH-0005iB-St for grub-devel@gnu.org; Fri, 08 May 2015 06:10:08 -0400 Received: from mo6-p00-ob.smtp.rzone.de ([2a01:238:20a:202:5300::2]:10260) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1YqfEH-0005g8-Js for grub-devel@gnu.org; Fri, 08 May 2015 06:10:01 -0400 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; t=1431079799; l=859; s=domk; d=aepfle.de; h=In-Reply-To:Content-Transfer-Encoding:Content-Disposition: Content-Type:MIME-Version:References:Subject:To:From:Date; bh=4ZlJK86oThgeC4YwznS0TTBDtnB6rztgA7SyNtO1r3g=; b=nGhjZRaqRXtUxWFCALGf1oU2qvQnv17a6RjeScRl+XCwmgkQN2DM0/M7pqrkt37fCaO O3WgNKp+fINZc985mEVjapt1WHmKqnoIJitgHZmQkgcGhex0WCIQN7O8iQMOMpwyjdX6k UYELFEfmOpxdwkMPj/l+TBKDL9G7fxFH2mE= X-RZG-AUTH: :P2EQZWCpfu+qG7CngxMFH1J+yackYocTD1iAi8x+OWi/zfN1cLnBYfssVY1SE5ClEYfb5sQvxDNUdfk3GFAM3xrxaZN0YQ== X-RZG-CLASS-ID: mo00 Received: from probook.fritz.box ([2001:a60:10a3:eb01:1ec1:deff:feb9:bb48]) by smtp.strato.de (RZmta 37.5 AUTH) with ESMTPSA id y00630r48A9xoE4 (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (curve sect571r1 with 571 ECDH bits, eq. 15360 bits RSA)) (Client did not present a certificate) for ; Fri, 8 May 2015 12:09:59 +0200 (CEST) Received: by probook.fritz.box (Postfix, from userid 1000) id 803C3502A7; Fri, 8 May 2015 12:09:58 +0200 (CEST) Date: Fri, 8 May 2015 12:09:58 +0200 From: Olaf Hering To: The development of GNU GRUB Subject: Re: passing options to grub in xen,openfirmware and efi Message-ID: <20150508100958.GA13979@aepfle.de> References: <20150429154801.GA7715@aepfle.de> <20150429162800.GA32494@aepfle.de> <20150429164921.GA9393@aepfle.de> <554B7A74.7010404@gmail.com> <20150507145426.GA26929@aepfle.de> <554B7DBA.8060501@gmail.com> <554B830A.8040400@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Disposition: inline Content-Transfer-Encoding: 8bit In-Reply-To: <554B830A.8040400@gmail.com> User-Agent: Mutt/1.5.22.rev6346 (2013-10-29) X-detected-operating-system: by eggs.gnu.org: Error: Malformed IPv6 address (bad octet value). X-Received-From: 2a01:238:20a:202:5300::2 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: Fri, 08 May 2015 10:10:09 -0000 On Thu, May 07, Vladimir 'φ-coder/phcoder' Serbinenko wrote: > most other firmwares like EFI or BIOS look for boot image at hardcoded > place e.g. MBR or ESP at predefined locations or uses NVRAM. The trouble > with passing this info from dom0 is that it's difficult to discover for > grub-install where to put image, in some cases this would even make > install impossible without modifying dom0. I feel like location which > changes all the time would create more confusion that hardcoded location > (E.g. I ran grub-install but my system still uses old GRUB) What do you expect from grub-install in a PV guest? Whatever it does today its result will be a noop. All that needs to be done is to write /boot/grub2/grub.cfg. In a PV guest grub2 is the firmware (kernel= in domU.cfg), and the NVRAM is the cmdline (extra= in domU.cfg). Olaf