All of lore.kernel.org
 help / color / mirror / Atom feed
From: Andrea Bolognani <abologna@redhat.com>
To: Laszlo Ersek <lersek@redhat.com>, qemu-devel@nongnu.org
Cc: marcel@redhat.com, drjones@redhat.com, kraxel@redhat.com
Subject: Re: [Qemu-devel] [PATCH v5 2/2] mach-virt: Provide sample configuration files
Date: Wed, 08 Feb 2017 20:47:27 +0100	[thread overview]
Message-ID: <1486583247.3641.34.camel@redhat.com> (raw)
In-Reply-To: <7952cdc6-9852-7a5e-27bd-2d2d1a859866@redhat.com>

On Wed, 2017-02-08 at 20:34 +0100, Laszlo Ersek wrote:
> > > Also, I can't verify the exact pathnames for Fedora.
> > 
> > https://koji.fedoraproject.org/koji/rpminfo?rpmID=8491933 ;)
> 
> Ahhh, it's *very* good that you provided this reference, because now I
> see that the file names below are incorrect. Namely, for aarch64 guests,
> you have to use the files that are padded to 64MB, *not* the files as
> they fall out of the edk2 build process.

Go figure... Thanks for spotting that!

[...]
> > # Depending on the OS distribution you're using on the
> > # host, the name of the package containing the firmware
> > # binary and variable store, as well as the paths to the
> 
> red flag: please say "variable store *template*"

Right. Missed it, sorry.

[...]
> > # Fedora:
> > #   edk2-aarch64                          (package)
> > #   /usr/share/edk2/aarch64/QEMU_EFI.fd   (binary)
> > #   /usr/share/edk2/aarch64/QEMU_VARS.fd  (template)
> > #
> > # RHELSA:
> > #   AAVMF                                 (package)
> > #   /usr/share/AAVMF/AAVMF_CODE.fd        (binary)
> > #   /usr/share/AAVMF/AAVMF_VARS.fd        (varstore)
> 
> Two comments:
> 
> - Under Fedora, you have (template), which is cool, (varstore) is bad. :)

That just shows that I'm getting really tired and I should
step away from the keyboard for the day :/

> - Again, the files you note above for Fedora are 2MB and 768KB in size,
> respectively, which is wrong. The files you note for RHELSA are both
> 64MB in size, which is right. Fedora ships the according files as well,
> but their names are different:
> 
> /usr/share/edk2/aarch64/QEMU_EFI-pflash.raw      (binary)
> /usr/share/edk2/aarch64/vars-template-pflash.raw (varstore template)

Consider it fixed!

(Those filenames, though... Ewww.)

-- 
Andrea Bolognani / Red Hat / Virtualization

  reply	other threads:[~2017-02-08 19:47 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-08 17:35 [Qemu-devel] [PATCH v5 0/2] docs: Improve sample configuration files Andrea Bolognani
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 1/2] q35: " Andrea Bolognani
2017-02-08 17:35 ` [Qemu-devel] [PATCH v5 2/2] mach-virt: Provide " Andrea Bolognani
2017-02-08 18:11   ` Laszlo Ersek
2017-02-08 18:49     ` Andrea Bolognani
2017-02-08 19:34       ` Laszlo Ersek
2017-02-08 19:47         ` Andrea Bolognani [this message]
2017-02-09  9:49     ` Andrew Jones
2017-02-09 10:52       ` Andrea Bolognani
2017-02-08 18:32   ` Peter Maydell
2017-02-08 19:23     ` Laszlo Ersek
2017-02-08 19:40       ` Peter Maydell
2017-02-08 19:28     ` Andrea Bolognani
2017-02-08 19:36       ` Peter Maydell
2017-02-08 19:49         ` Laszlo Ersek
2017-02-09 13:53         ` Andrea Bolognani
2017-02-09 14:14           ` Andrew Jones
2017-02-08 19:36       ` Laszlo Ersek
2017-02-09  9:42   ` Andrew Jones
2017-02-09  9:57     ` Peter Maydell
2017-02-09 10:51       ` Andrea Bolognani
2017-02-09 12:28         ` Andrew Jones
2017-02-09 13:27           ` Andrea Bolognani
2017-02-09 14:08             ` Andrew Jones
2017-02-09 14:56               ` Andrea Bolognani
2017-02-09 15:26                 ` Gerd Hoffmann
2017-02-09 15:10           ` Andrea Bolognani
2017-02-09 15:35             ` Andrew Jones
2017-02-09 16:11               ` Andrea Bolognani
2017-02-09 16:36                 ` Andrew Jones
2017-02-09 17:06                   ` Andrea Bolognani
2017-02-09 18:05                     ` Andrew Jones

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=1486583247.3641.34.camel@redhat.com \
    --to=abologna@redhat.com \
    --cc=drjones@redhat.com \
    --cc=kraxel@redhat.com \
    --cc=lersek@redhat.com \
    --cc=marcel@redhat.com \
    --cc=qemu-devel@nongnu.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.