From mboxrd@z Thu Jan 1 00:00:00 1970 From: PGNet Dev Subject: Re: [PATCH v2 00/23] x86: multiboot2 protocol support Date: Fri, 30 Oct 2015 11:36:03 -0700 Message-ID: <5633B893.4040800@gmail.com> References: <56339075.9010403@gmail.com> <20151030172959.GK3489@olila.local.net-space.pl> <5633B1BD.9070908@gmail.com> <20151030182318.GM3489@olila.local.net-space.pl> Reply-To: PGNet Dev Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20151030182318.GM3489@olila.local.net-space.pl> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Daniel Kiper Cc: xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org On 10/30/2015 11:23 AM, Daniel Kiper wrote: > I missed that you are talking about PE executable. However, > as it was said you must create xen.cfg in advance and put it in the same > directory with xen.efi. Please check xen/docs/misc/efi.markdown for more details. TBH I'm not clear on whether the executable is -- or more importantly, still will be -- needed. Atm, I'm manually creating the xen.cfg/xen.ini and chainloading via GRUB2. Hence the mess, and asking about simpler approaches. IIUC, systemd-boot is a rename (fork?) of gummiboot. WAS going to try it awhile ago, as a simpler alternative to Grub2, but saw only that the project had been emptied out. Didn't realize that it'd been subsumed. Interestingly, from https://en.wikipedia.org/wiki/Gummiboot_(software) "Red Hat's Fedora Project does not use gummiboot for booting UEFI systems; instead, it will use efilinux to chainload GRUB." Trying to find out the WHY in the different boot-Xen-on-UEFI approaches, let alone simply what just works, is a challenge.