On Wed, Oct 19, 2016 at 01:06:05PM -0400, Cole Robinson wrote:
> On 10/03/2016 11:49 AM, Daniel P. Berrange wrote:
> > Currently qemu.conf contains a nvram parameter which
> > lists firmware code files and the corresponding nvram
> > file path. We need to know which architecture and
> > features
On 10/03/2016 11:49 AM, Daniel P. Berrange wrote:
> Currently qemu.conf contains a nvram parameter which
> lists firmware code files and the corresponding nvram
> file path. We need to know which architecture and
> features are associated with each firmware file for
> future enhancement. This
On Wed, Oct 19, 2016 at 02:52:20PM +0100, Richard W.M. Jones wrote:
> On Wed, Oct 19, 2016 at 02:22:19PM +0100, Daniel P. Berrange wrote:
> > Oh, but that's outside scope of libvirt then - we're not looking to
> > expose APIs to help people run QEMU directly.
>
> Well, yes, but that doesn't mean
On Wed, Oct 19, 2016 at 02:22:19PM +0100, Daniel P. Berrange wrote:
> Oh, but that's outside scope of libvirt then - we're not looking to
> expose APIs to help people run QEMU directly.
Well, yes, but that doesn't mean we cannot cooperate. These wouldn't
be libvirt APIs, just a standard
On Wed, Oct 19, 2016 at 02:13:52PM +0100, Richard W.M. Jones wrote:
> On Wed, Oct 19, 2016 at 01:18:07PM +0100, Daniel P. Berrange wrote:
> > On Wed, Oct 19, 2016 at 01:07:25PM +0100, Richard W.M. Jones wrote:
> > > Unfortunately it's a case of so near and yet so far. You're proposing
> > > this
On Wed, Oct 19, 2016 at 01:18:07PM +0100, Daniel P. Berrange wrote:
> On Wed, Oct 19, 2016 at 01:07:25PM +0100, Richard W.M. Jones wrote:
> > Unfortunately it's a case of so near and yet so far. You're proposing
> > this essentially static and non-secret data be stored in
> >
On Wed, Oct 19, 2016 at 01:07:25PM +0100, Richard W.M. Jones wrote:
> On Mon, Oct 03, 2016 at 04:49:47PM +0100, Daniel P. Berrange wrote:
> > --- a/src/qemu/qemu.conf
> > +++ b/src/qemu/qemu.conf
> > @@ -595,16 +595,22 @@
> > # using this master file as image. Each UEFI firmware can,
> > #
On Mon, Oct 03, 2016 at 04:49:47PM +0100, Daniel P. Berrange wrote:
> --- a/src/qemu/qemu.conf
> +++ b/src/qemu/qemu.conf
> @@ -595,16 +595,22 @@
> # using this master file as image. Each UEFI firmware can,
> # however, have different variables store. Therefore the nvram is
> # a list of
On 10/03/2016 11:49 AM, Daniel P. Berrange wrote:
> Currently qemu.conf contains a nvram parameter which
> lists firmware code files and the corresponding nvram
> file path. We need to know which architecture and
> features are associated with each firmware file for
> future enhancement. This
Currently qemu.conf contains a nvram parameter which
lists firmware code files and the corresponding nvram
file path. We need to know which architecture and
features are associated with each firmware file for
future enhancement. This extends the syntax in a
backwards compatible manner to record
10 matches
Mail list logo
