From: Gerd Hoffmann <kraxel@redhat.com>
To: Kashyap Chamarthy <kchamart@redhat.com>
Cc: libvir-list@redhat.com,
"Daniel P. Berrangé" <berrange@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: Tue, 1 Feb 2022 14:30:36 +0100 [thread overview]
Message-ID: <20220201133036.kwep2tw5mvcjbyt2@sirius.home.kraxel.org> (raw)
In-Reply-To: <Yff+gCndUlijqMsz@paraplu>
On Mon, Jan 31, 2022 at 04:21:36PM +0100, Kashyap Chamarthy wrote:
> 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.
Main advantage of the split is that it is much easier to update the
firmware code without smashing the guest vars, not so much the disk
space requirements.
take care,
Gerd
prev parent reply other threads:[~2022-02-01 18:06 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
2022-01-31 15:35 ` Daniel P. Berrangé
2022-01-31 15:58 ` Kashyap Chamarthy
2022-02-01 13:30 ` Gerd Hoffmann [this message]
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=20220201133036.kwep2tw5mvcjbyt2@sirius.home.kraxel.org \
--to=kraxel@redhat.com \
--cc=berrange@redhat.com \
--cc=f4bug@amsat.org \
--cc=kchamart@redhat.com \
--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).