From mboxrd@z Thu Jan 1 00:00:00 1970 From: Fabio Fantoni Subject: Re: [PATCH 0/4] Reintroduce OVMF support Date: Mon, 28 Oct 2013 11:53:39 +0100 Message-ID: <526E4233.5060203@m2r.biz> References: <1381855205-3329-1-git-send-email-wei.liu2@citrix.com> <525E8C1B.9060206@cantab.net> <20131016131002.GF16371@zion.uk.xensource.com> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii"; Format="flowed" Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20131016131002.GF16371@zion.uk.xensource.com> List-Unsubscribe: , List-Post: List-Help: List-Subscribe: , Sender: xen-devel-bounces@lists.xen.org Errors-To: xen-devel-bounces@lists.xen.org To: Wei Liu , David Vrabel Cc: ian.jackson@eu.citrix.com, ian.campbell@citrix.com, xen-devel@lists.xen.org List-Id: xen-devel@lists.xenproject.org Il 16/10/2013 15:10, Wei Liu ha scritto: > On Wed, Oct 16, 2013 at 01:52:43PM +0100, David Vrabel wrote: >> On 15/10/13 17:40, Wei Liu wrote: >>> This small series reintroduces OVMF support in Xen >> I think somewhere in this series there needs to a brief description of >> what OVMF is. >> > OVMF is a project to enable UEFI firmware for virtual machines. It's > part of the EDK2 kit. OVMF was first introduced to Xen about a year ago > but it was later disabled due to build process breakage. > > Now that the build problem is resolved in upstream we would like to > re-enable it in Xen. I will test ovmf shortly, there is a new patches version ready or near to be posted or I'll start to test with this version? Thanks for any reply. > >> With the exception of the first patch this is just adding yet another >> component to clone and build. Why is this useful? Why isn't >> (effectively) --with-system-ovmf always enabled (and thus not actually >> needed as an option)? >> > Idealy we should always use the binary provided by distro, but > pratically their binaries are not always up to date / don't always work > with Xen. > >> Isn't Xen's keenness to build it's own particular versions of stuff >> something that causes significant problems for distributions? >> > We've been trying to work closely with upstream to fix bugs. But the > proecess for distros to pick up upstream bug fixes are different > stories which we have no control over. > > That's why we provide several --with-system-FOO options in our build > system. The packager can choose in stock binaries if they want to. But > if the in stock binaries don't work they can use our trees. > > Wei. > >> David > _______________________________________________ > Xen-devel mailing list > Xen-devel@lists.xen.org > http://lists.xen.org/xen-devel