[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Xen-devel] booting Xen from EFI

  • To: Jan Beulich <JBeulich@xxxxxxxxxx>
  • From: Keir Fraser <keir.xen@xxxxxxxxx>
  • Date: Wed, 15 Jun 2011 16:58:21 +0100
  • Cc: "xen-devel@xxxxxxxxxxxxxxxxxxx" <xen-devel@xxxxxxxxxxxxxxxxxxx>
  • Delivery-date: Wed, 15 Jun 2011 09:00:19 -0700
  • Domainkey-signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=user-agent:date:subject:from:to:cc:message-id:thread-topic :thread-index:in-reply-to:mime-version:content-type :content-transfer-encoding; b=jf4HgJrRs6xXJ8ChM2WfkZfL7tYB6QUHdo1COKLDjz2DlkpSAT+ro/223jTb0HI3g6 Wl6F41bgHgtsXeT6KfYtbCJZWv1nhKd1en7TdNkTMhuXPbTPD9lXDmTAMlzXVG1yMqSV ACNNnfUEi9DsIMdgMxDwFUkW/0s3+jF1Im0vo=
  • List-id: Xen developer discussion <xen-devel.lists.xensource.com>
  • Thread-index: AcwrdQyhuU13KwDclUaoQJ3gl4vL3g==
  • Thread-topic: [Xen-devel] booting Xen from EFI

On 15/06/2011 16:22, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:

>>>> On 15.06.11 at 16:55, Keir Fraser <keir.xen@xxxxxxxxx> wrote:
>> On 15/06/2011 13:48, "Jan Beulich" <JBeulich@xxxxxxxxxx> wrote:
>>> 3) GrUB decompresses simple gzip-ed binaries (i.e. the traditional
>>> non-bzImage kernel), but with EFI Xen will need to do so itself.
>>> The most obvious choice would seem be to allow for all currently
>>> supported compression methods to not only be used inside a
>>> bzImage container, but also on a plain ELF binary.
>> I don't really understand the problem. As long as we don't get yet another
>> pile of decompressors in the tree I don't really care either.
> Xen doesn't currently understand a compressed (gzip or other)
> ELF image, it can only deal with compressed payloads of bzImage
> containers.
> And no, it would just mean hooking up the existing decompressors
> via a second path.

Ah yes I see. That makes sense.

 -- Keir

Xen-devel mailing list



Lists.xenproject.org is hosted with RackSpace, monitoring our
servers 24x7x365 and backed by RackSpace's Fanatical Support®.