From: Ian Campbell <ian.campbell@citrix.com>
To: Jan Beulich <JBeulich@suse.com>
Cc: Anthony Perard <anthony.perard@citrix.com>,
Ian Jackson <Ian.Jackson@eu.citrix.com>,
Wei Liu <wei.liu2@citrix.com>,
xen-devel <xen-devel@lists.xenproject.org>
Subject: Re: Stable backport request for new OVMF version
Date: Thu, 23 Jul 2015 15:43:22 +0100 [thread overview]
Message-ID: <1437662602.24746.6.camel@citrix.com> (raw)
In-Reply-To: <55B115D00200007800094AA8@prv-mh.provo.novell.com>
On Thu, 2015-07-23 at 08:26 -0600, Jan Beulich wrote:
> >
> > > > On 23.07.15 at 15:56, <ian.campbell@citrix.com> wrote:
> > The version of OVMF in 4.5 (and presumably earlier) doesn't build
> > with
> > the gcc in modern Linux distros (I noticed it with 4.9 from
> > Debian/Jessie).
> >
> > I think we should update Config.mk:OVMF_UPSTREAM_REVISION to
> > cb9a7ebabcd6b8a49dc0854b2f9592d732b5afbd in all stable branches.
> > That
> > version is the one currently in master.
>
> To be honest I didn't even know we support use of OVMF in any
> released version (nor in unstable). When did this change?
It was present in 4.3. I don't think we build it by default since its
toolchain is a bit picky, but we turn it on and test it in osstest from
4.4 onwards.
You can ask for it with bios="ovmf" in your hvm guest's config.
Ian.
next prev parent reply other threads:[~2015-07-23 14:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1437659800.19412.104.camel@citrix.com>
2015-07-23 14:19 ` Stable backport request for new OVMF version Ian Campbell
2015-07-23 14:26 ` Jan Beulich
2015-07-23 14:43 ` Ian Campbell [this message]
2015-07-23 14:51 ` Jan Beulich
2015-07-23 14:58 ` Ian Campbell
2015-07-23 15:28 ` Jan Beulich
2015-07-23 15:31 ` Wei Liu
2015-07-23 15:37 ` Jan Beulich
2015-07-23 15:59 ` Ian Campbell
2015-07-23 16:11 ` Jan Beulich
2015-07-23 16:23 ` Ian Campbell
2015-07-24 7:47 ` Jan Beulich
2015-07-24 7:56 ` Wei Liu
2015-07-24 8:09 ` Jan Beulich
2015-07-24 8:50 ` Ian Campbell
2015-07-23 15:04 ` Fabio Fantoni
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1437662602.24746.6.camel@citrix.com \
--to=ian.campbell@citrix.com \
--cc=Ian.Jackson@eu.citrix.com \
--cc=JBeulich@suse.com \
--cc=anthony.perard@citrix.com \
--cc=wei.liu2@citrix.com \
--cc=xen-devel@lists.xenproject.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).