From: Eric Blake <eblake@redhat.com>
To: ChenLiang <chenliang88@huawei.com>,
"qemu-devel@nongnu.org" <qemu-devel@nongnu.org>
Cc: Paolo Bonzini <pbonzini@redhat.com>
Subject: Re: [Qemu-devel] [question] Is it, valuable to achieve modify boot index when vm is running?
Date: Wed, 25 Jun 2014 07:27:18 -0600 [thread overview]
Message-ID: <53AACE36.2070906@redhat.com> (raw)
In-Reply-To: <53AAA467.10208@huawei.com>
[-- Attachment #1: Type: text/plain, Size: 856 bytes --]
On 06/25/2014 04:28 AM, ChenLiang wrote:
> hi,all
> Qemu can not modify boot index when vm is running.
So? Boot index is used exactly once - when the domain is started. After
that, you aren't booting any more, so what benefit is there to changing
boot index on the fly?
> It is inconvenience when we install guest os. Is it
> necessary to achieve modify boot index online?
virt-install manages to install guests just fine without changing the
boot index on the fly; it manages to sequence multiple qemu runs with
different boot indices between runs.
> We can add one qmp interface to achieve it.
You're welcome to submit a patch if you think you have a use case; but I
personally don't see the current setup as limiting.
--
Eric Blake eblake redhat com +1-919-301-3266
Libvirt virtualization library http://libvirt.org
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 604 bytes --]
next prev parent reply other threads:[~2014-06-25 13:27 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-06-25 10:28 [Qemu-devel] [question] Is it, valuable to achieve modify boot index when vm is running? ChenLiang
2014-06-25 13:27 ` Eric Blake [this message]
2014-06-25 13:29 ` Paolo Bonzini
2014-06-25 13:46 ` 陈梁
2014-06-25 13:46 ` 陈梁
[not found] ` <043E36F0EEC5164DBB381DFD6AB7D4221777BA92@Bjmail2.kingsoft.cn>
2014-06-26 3:16 ` [Qemu-devel] 答复: " ChenLiang
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=53AACE36.2070906@redhat.com \
--to=eblake@redhat.com \
--cc=chenliang88@huawei.com \
--cc=pbonzini@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).