From: Kashyap Chamarthy <kchamart@redhat.com>
To: "Daniel P. Berrangé" <berrange@redhat.com>
Cc: libvir-list@redhat.com, qemu-devel@nongnu.org,
"Philippe Mathieu-Daudé" <f4bug@amsat.org>
Subject: Re: [PATCH v2] docs: expand firmware descriptor to allow flash without NVRAM
Date: Mon, 31 Jan 2022 16:21:36 +0100 [thread overview]
Message-ID: <Yff+gCndUlijqMsz@paraplu> (raw)
In-Reply-To: <Yffz/v/7b6jJOBwi@redhat.com>
On Mon, Jan 31, 2022 at 02:36:46PM +0000, Daniel P. Berrangé wrote:
> On Mon, Jan 31, 2022 at 03:00:33PM +0100, Kashyap Chamarthy wrote:
> > On Mon, Jan 31, 2022 at 12:55:09PM +0000, Daniel P. Berrangé wrote:
[...]
> > I briefly wondered if in this "combined" mode whether the no. of
> > duplicate copies can ever fill up the storage. I doubt that, as the
> > combined size of _VARS + _CODE is just about 2MB. So it only starts
> > mattering if you're running tens of thousands of guests.
>
> When guest root / data disk sizes are measured in 100's of MB, or
> GBs, I struggle to get worried about even a 16 MB OVMF blob being
> copied per guest.
Heh, fair enough.
> The firmware can be provided in qcow2 format too, so if really
> concerned, just create a qcow2 file with a backing store pointing
> to the readonly master, so you're only paying the price of the
> delta for any guest VARs writes. That's more efficient than what
> we do today with copying the separate raw format VARS.fd file.
That's nice, I didn't know the qcow2 possibility in this context. For
some reason I assumed the file format always has to be raw here. Your
qcow2 point above should be documented, if it isn't already. Although
I don't know the right place for it.
[...]
--
/kashyap
next prev parent reply other threads:[~2022-01-31 15:24 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-31 12:55 [PATCH v2] docs: expand firmware descriptor to allow flash without NVRAM Daniel P. Berrangé
2022-01-31 14:00 ` Kashyap Chamarthy
2022-01-31 14:36 ` Daniel P. Berrangé
2022-01-31 15:21 ` Kashyap Chamarthy [this message]
2022-01-31 15:35 ` Daniel P. Berrangé
2022-01-31 15:58 ` Kashyap Chamarthy
2022-02-01 13:30 ` Gerd Hoffmann
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=Yff+gCndUlijqMsz@paraplu \
--to=kchamart@redhat.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=libvir-list@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 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).