From: "Daniel P. Berrangé" <berrange@redhat.com>
To: "Jason A. Donenfeld" <Jason@zx2c4.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [PATCH] hw/i386: pass RNG seed to e820 setup table
Date: Fri, 8 Jul 2022 13:00:29 +0100 [thread overview]
Message-ID: <YsgcXWuE2HIbFvN6@redhat.com> (raw)
In-Reply-To: <20220630113717.1893529-1-Jason@zx2c4.com>
On Thu, Jun 30, 2022 at 01:37:17PM +0200, Jason A. Donenfeld wrote:
> Tiny machines optimized for fast boot time generally don't use EFI,
> which means a random seed has to be supplied some other way, in this
> case by the e820 setup table, which supplies a place for one. This
> commit adds passing this random seed via the table. It is confirmed to
> be working with the Linux patch in the link.
IIUC, this approach will only expose the random seed when QEMU
is booted using -kernel + -initrd args.
I agree with what you say about most VMs not using UEFI right now.
I'd say the majority of general purpose VMs are using SeaBIOS
still. The usage of -kernel + -initrd, is typically for more
specialized use cases.
IOW, exposing random seed via the setup table feels like it'll
have a somewhat limited benefit.
Can we get an approach that exposes a random seed regardless of
whether using -kernel, or seabios, or uefi, or $whatever firmware ?
Perhaps (ab)use 'fw_cfg', which is exposed for any x86 VM no matter
what config it has for booting ?
With regards,
Daniel
--
|: https://berrange.com -o- https://www.flickr.com/photos/dberrange :|
|: https://libvirt.org -o- https://fstop138.berrange.com :|
|: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
next prev parent reply other threads:[~2022-07-08 12:03 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-30 11:37 [PATCH] hw/i386: pass RNG seed to e820 setup table Jason A. Donenfeld
2022-07-08 11:42 ` [PATCH v2] " Jason A. Donenfeld
2022-07-08 12:00 ` Daniel P. Berrangé [this message]
2022-07-08 12:04 ` [PATCH] " Jason A. Donenfeld
2022-07-08 14:14 ` Daniel P. Berrangé
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=YsgcXWuE2HIbFvN6@redhat.com \
--to=berrange@redhat.com \
--cc=Jason@zx2c4.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).