From: Anthony Liguori <aliguori@us.ibm.com>
To: qemu-devel@nongnu.org
Cc: David Gibson <david@gibson.dropbear.id.au>,
Alex Graf <agraf@suse.de>, Avik Sil <aviksil@linux.vnet.ibm.com>
Subject: [Qemu-devel] nvram and boot order
Date: Tue, 16 Oct 2012 14:55:21 -0500 [thread overview]
Message-ID: <87wqyqyyxi.fsf@codemonkey.ws> (raw)
We discussed nvram and it's interaction with boot order in today's KVM
call. Here's the outcome. This list is completely incremental so it's
fine to start with 1-4, for instance, as long as we eventually get to 6.
Today, on x86, we implement up to (5) but we don't persist NVRAM.
1) We should modify QEMUMachine to specify that a machine does not want
a default boot order. Ideally, this would be done by adding a new
default_boot_order that is set to "cad" explicitly in all machines
allowing a machine to remove that entry. At any rate, this allows a
machine to receive a NULL boot order when -boot isn't used and take an
appropriate action accordingly.
2) In the absence of a persistent NVRAM, a ephemeral NVRAM should be
generated with a reasonable default boot order.
3) In the absence of -boot or ,bootindex=, the system should boot from
order specified in NVRAM.
4) If -boot is specified, the parameter should alter the contents of
NVRAM to change the boot order to what is specified by -boot.
5) If ,bootorder is specified, it should take predence over -boot.
6) ,bootorder= should also alter the contents of NVRAM to determine the
boot order.
Regards,
Anthony Liguori
next reply other threads:[~2012-10-16 19:56 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-16 19:55 Anthony Liguori [this message]
2012-10-16 20:07 ` [Qemu-devel] nvram and boot order Benjamin Herrenschmidt
2012-10-16 20:55 ` Anthony Liguori
2012-10-26 6:27 ` David Gibson
2012-10-17 13:48 ` Gleb Natapov
2012-10-16 20:13 ` Peter Maydell
2012-10-16 23:12 ` Anthony Liguori
2012-10-17 1:01 ` David Gibson
2012-10-17 0:58 ` David Gibson
2012-10-17 18:17 ` Anthony Liguori
2012-10-18 0:09 ` David Gibson
2012-10-18 1:18 ` Benjamin Herrenschmidt
2012-10-18 6:32 ` Alexander Graf
2012-10-19 8:24 ` David Gibson
2012-10-19 8:40 ` Alexander Graf
2012-10-25 4:14 ` David Gibson
2012-10-19 14:21 ` Anthony Liguori
2012-10-19 14:36 ` Peter Maydell
2012-10-19 18:11 ` Benjamin Herrenschmidt
2012-10-19 17:29 ` Blue Swirl
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=87wqyqyyxi.fsf@codemonkey.ws \
--to=aliguori@us.ibm.com \
--cc=agraf@suse.de \
--cc=aviksil@linux.vnet.ibm.com \
--cc=david@gibson.dropbear.id.au \
--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).