From: Laine Stump <laine@redhat.com>
To: qemu-devel@nongnu.org
Cc: "libvir-list@redhat.com" <libvir-list@redhat.com>,
seabios@seabios.org, Amos Kong <akong@redhat.com>
Subject: Re: [Qemu-devel] [libvirt] [Qemu PATCH v2] add a boot option to do strict boot
Date: Wed, 09 Jan 2013 12:28:57 -0500 [thread overview]
Message-ID: <50EDA8D9.6000003@redhat.com> (raw)
In-Reply-To: <20130109152201.GO20716@redhat.com>
On 01/09/2013 10:22 AM, Daniel P. Berrange wrote:
> On Wed, Jan 09, 2013 at 08:14:07AM -0700, Eric Blake wrote:
>> On 01/09/2013 01:39 AM, Amos Kong wrote:
>>> Current seabios will try to boot from selected devices first,
>>> if they are all failed, seabios will also try to boot from
>>> un-selected devices.
>>>
>>> We need to make it configurable. I already posted a seabios
>>> patch to add a new device type to halt booting. Qemu can add
>>> "HALT" at the end of bootindex string, then seabios will halt
>>> booting after trying to boot from selected devices.
>>>
>>> This option only effects when boot priority is changed by
>>> bootindex options, the old style(-boot order=..) will still
>>> try to boot from un-selected devices.
>>>
>>> v2: add HALT entry in get_boot_devices_list()
>>> define boot_strict to bool
>>>
>>> Signed-off-by: Amos Kong <akong@redhat.com>
>>> ---
>> Libvirt will need to expose an attribute that lets the user control
>> whether to use this new option; how do we probe via QMP whether the new
>> -boot strict=on command-line option is available?
> While libvirt should make use of this, we don't need to
> expose it in the XML. This new behaviour is what we wanted
> to have all along, so we should just enable it.
I agree that this is the way it *should* always work, but apparently
there are people who depend on the old behavior, so just doing a blanket
switch to the new behavior could lead to setups that no longer work
"properly" after an upgrade, which unfortunately means that existing
functionality needs to be maintained, and "correct" functionality must
be triggered by a config switch (maybe Gleb can expand on the use cases
that require this if more details are needed, as it's him I heard this from)
next prev parent reply other threads:[~2013-01-09 17:29 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-09 7:34 [Qemu-devel] [Qemu PATCH] add a boot option to do strict boot Amos Kong
2013-01-09 7:54 ` Gleb Natapov
2013-01-09 8:39 ` [Qemu-devel] [Qemu PATCH v2] " Amos Kong
2013-01-09 9:56 ` Gleb Natapov
2013-01-09 15:14 ` Eric Blake
2013-01-09 15:22 ` [Qemu-devel] [libvirt] " Daniel P. Berrange
2013-01-09 17:28 ` Laine Stump [this message]
2013-01-09 17:46 ` Gleb Natapov
2013-01-09 15:52 ` [Qemu-devel] " Amos Kong
[not found] ` <1974277572.9315720.1358868212597.JavaMail.root@redhat.com>
[not found] ` <20130122155229.GA9465@t430s.nay.redhat.com>
[not found] ` <50FEB79E.1040206@redhat.com>
[not found] ` <878v7ldqh0.fsf@codemonkey.ws>
[not found] ` <20130123104144.GA2419@t430s.nay.redhat.com>
[not found] ` <20130128031934.GA3986@t430s.nay.redhat.com>
2013-03-04 10:20 ` [Qemu-devel] [RFC] introduce a general query-config cmd Amos Kong
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=50EDA8D9.6000003@redhat.com \
--to=laine@redhat.com \
--cc=akong@redhat.com \
--cc=libvir-list@redhat.com \
--cc=qemu-devel@nongnu.org \
--cc=seabios@seabios.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).