From: Janne Huttunen <janne.huttunen@nokia.com>
To: Gerd Hoffmann <kraxel@redhat.com>
Cc: qemu-devel@nongnu.org
Subject: Re: [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property
Date: Wed, 15 Mar 2017 08:58:25 +0200 [thread overview]
Message-ID: <1489561105.24841.25.camel@nokia.com> (raw)
In-Reply-To: <1489510640.8844.18.camel@redhat.com>
> > - Does this approach make sense? Any better ideas?
>
> What is the use case?
The short answer: emulating real hardware.
Since real HW has this capability, there exist certain
auxiliary systems that are built on it. Having similar
semantics available in QEMU allows me to build a virtual
machine that works with these systems without modifying
them in any way.
Also, the support I'm after already almost was in QEMU
('-boot once='). It just didn't quite provide the
functionality I wanted i.e. the 'bootindex' like operation.
This patch series tries to bridge that gap. But hey, I
wasn't sure if this was useful for other people too, and
that's why the RFC.
In principle I agree with you that in some specific cases
QEMU has other means of doing things that necessarily don't
exist in real HW. Obviously systems that are built for real
HW don't use any such QEMU specific methods. Again, in some
specific cases it might be possible to get close enough
semantics without real "boot once" support and in others it
probably won't be. Note that part of the semantics I'm after
is that the "boot once" order can be set while the system is
up and running. It may or may not be strictly necessary
depending on the specific use case, but that's the way the
real HW works.
next prev parent reply other threads:[~2017-03-15 6:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-14 12:50 [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 1/6] Re-factor bootdevice list handling, pt1 Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 2/6] Re-factor bootdevice list handling, pt2 Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 3/6] Add support for "bootonceindex" property Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 4/6] Clear the boot once list after it has been used Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 5/6] Support "bootonceindex" property for virtio-net interfaces Janne Huttunen
2017-03-14 12:50 ` [Qemu-devel] [RFC][PATCH 6/6] Support "bootonceindex" property for SCSI disks Janne Huttunen
2017-03-14 16:57 ` [Qemu-devel] [RFC][PATCH 0/6] "bootonceindex" property Gerd Hoffmann
2017-03-15 6:58 ` Janne Huttunen [this message]
2017-03-15 7:24 ` Gerd Hoffmann
2017-03-16 9:46 ` Janne Huttunen
2017-03-16 9:59 ` Gerd Hoffmann
2017-03-21 17:48 ` Eric Blake
2017-03-22 5:42 ` Markus Armbruster
2017-03-21 17:55 ` Paolo Bonzini
2017-03-22 6:36 ` Janne Huttunen
2017-03-22 8:43 ` Paolo Bonzini
2017-03-22 9:00 ` Huttunen, Janne (Nokia - FI/Espoo)
2017-03-22 10:51 ` Laszlo Ersek
2017-03-22 13:58 ` Janne Huttunen
2017-03-22 14:36 ` Laszlo Ersek
2017-03-22 15:19 ` Janne Huttunen
2017-03-22 15:29 ` Laszlo Ersek
2017-03-23 6:53 ` Janne Huttunen
2017-03-23 9:13 ` Laszlo Ersek
[not found] ` <CACaajQsrkuZeC6WYXdEBJY=FEkTQ9iY_i8E-d5j7JqK5DDUuOw@mail.gmail.com>
2017-03-15 7:21 ` Vasiliy Tolstov
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=1489561105.24841.25.camel@nokia.com \
--to=janne.huttunen@nokia.com \
--cc=kraxel@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 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.