All of lore.kernel.org
 help / color / mirror / Atom feed
From: Anthony Liguori <aliguori@us.ibm.com>
To: David Gibson <dwg@au1.ibm.com>, Alexander Graf <agraf@suse.de>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	Avik Sil <aviksil@linux.vnet.ibm.com>
Subject: Re: [Qemu-devel] nvram and boot order
Date: Fri, 19 Oct 2012 09:21:24 -0500	[thread overview]
Message-ID: <876266y23f.fsf@codemonkey.ws> (raw)
In-Reply-To: <20121019082452.GW23523@truffula.fritz.box>

David Gibson <dwg@au1.ibm.com> writes:

> On Thu, Oct 18, 2012 at 08:32:54AM +0200, Alexander Graf wrote:
>> 
>> 
>> On 18.10.2012, at 03:18, Benjamin Herrenschmidt <benh@kernel.crashing.org> wrote:
>> 
>> > On Thu, 2012-10-18 at 11:09 +1100, David Gibson wrote:
>> > 
>> >>>> That's horrible; if you use -boot just once it will clobber a
>> >>>> persistent NVRAM's boot order.  I see that a means of changing the
>> >>>> default boot order from management tools is desirable, but that
>> >>>> shouldn't be the normal behaviour of -boot.  And the objections to (2)
>> >>>> apply even more strongly - we'd need to translate arbitrary -boot
>> >>>> strings to NVRAM representation which may not be at all
>> >>>> straightforward from the information qemu has available.
>> >>> 
>> >>> It may not be straight forward, but it's what makes the most sense from
>> >>> a user's PoV.
>> >> 
>> >> Bollocks.  Using -boot to override the normal boot sequence
>> >> permanently changing the normal boot sequence absoultely does not make
>> >> sense from a user's PoV.
>> > 
>> > I strongly agree with David here. -boot should not change the persistent
>> > state.
>> 
>> I think Anthony and you are looking at 2 different use cases, each
>> with their own sane reasoning.
>> 
>> You want to have the chance to override the boot order temporarily
>> for things like cd boot or quick guest rescue missions.
>> 
>> You also want to be able to permanently change the guest's boot
>> order from a management tool. At that same place you want to be able
>> to display it, so you don't have to boot your vm to know what it
>> would be doing.
>
> That's true to an extent.  However, I vehemently disagree that it's
> arbitrary which one gets the new option.  Neither -boot nor bootindex=
> alter any persistent data now and they should not suddenly start doing
> so.

That's not true.

For the PC, -boot modifies the CMOS memory.  If we persisted CMOS, then
-boot would cause a persistent modification in the boot order.

Regards,

Anthony Liguori

  parent reply	other threads:[~2012-10-19 14:22 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-10-16 19:55 [Qemu-devel] nvram and boot order Anthony Liguori
2012-10-16 20:07 ` 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 [this message]
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=876266y23f.fsf@codemonkey.ws \
    --to=aliguori@us.ibm.com \
    --cc=agraf@suse.de \
    --cc=aviksil@linux.vnet.ibm.com \
    --cc=dwg@au1.ibm.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.