qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Avik Sil <aviksil@linux.vnet.ibm.com>
To: Alexander Graf <agraf@suse.de>
Cc: Benjamin Herrenschmidt <benh@au1.ibm.com>,
	"qemu-ppc@nongnu.org List" <qemu-ppc@nongnu.org>,
	Nikunj A Dadhania <nikunj@linux.vnet.ibm.com>,
	Gleb Natapov <gleb@redhat.com>,
	qemu-devel qemu-devel <qemu-devel@nongnu.org>
Subject: Re: [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting
Date: Thu, 04 Oct 2012 18:05:15 +0530	[thread overview]
Message-ID: <506D8283.6090604@linux.vnet.ibm.com> (raw)
In-Reply-To: <751E4F90-614C-41A7-844A-6280BA05345D@suse.de>

>>>>> So you want to hack around the problem. If -boot is specified what
>>>>> device are you going to boot from?
>>>>
>>>> It is going to boot from the device specified in -boot as default_boot_order is set to 0 in that case.
>>>
>>> Imagine you have 2 controllers:
>>>
>>>    * vio
>>>    * virtio
>>>
>>> and you specify -boot c. Which device are you going to boot from?
>>
>> Currently, by default SLOF boots from the first disk it discovers in the device tree.
>
> So you want to replace one broken scheme with another broken scheme? :)

Ha ha, actually we hit this issue in some different context with respect 
to nvram boot-device which I mentioned in [1]. The patch is a workaround 
for that issue only.

Regards,
Avik

>
>
> Alex
>
>
>
[1] http://lists.nongnu.org/archive/html/qemu-ppc/2012-10/msg00020.html

  reply	other threads:[~2012-10-04 12:35 UTC|newest]

Thread overview: 30+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <50641A82.4030708@linux.vnet.ibm.com>
     [not found] ` <1348738150.24701.21.camel@pasglop>
2012-09-27  9:33   ` [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting Alexander Graf
2012-09-27  9:35     ` Benjamin Herrenschmidt
2012-09-27  9:39       ` Alexander Graf
2012-09-27  9:51     ` Gleb Natapov
2012-09-27 10:05       ` Nikunj A Dadhania
2012-09-27 10:13         ` Gleb Natapov
2012-09-27 10:34           ` Nikunj A Dadhania
2012-09-27 10:38             ` Gleb Natapov
2012-09-27 10:21       ` Benjamin Herrenschmidt
2012-09-27 10:35         ` Gleb Natapov
2012-09-28  6:12       ` Jordan Justen
2012-10-04 10:55       ` Avik Sil
2012-10-04 11:22         ` Gleb Natapov
2012-10-04 11:29           ` Avik Sil
2012-10-04 11:30             ` Alexander Graf
2012-10-04 12:18               ` Avik Sil
2012-10-04 12:21                 ` Alexander Graf
2012-10-04 12:35                   ` Avik Sil [this message]
2012-10-04 12:37                     ` Alexander Graf
2012-10-04 12:38                       ` Gleb Natapov
2012-10-05  4:45                       ` Nikunj A Dadhania
2012-10-04 11:32             ` Gleb Natapov
2012-10-04 11:59               ` Avik Sil
2012-10-05  0:34         ` David Gibson
2012-10-05  0:43           ` Alexander Graf
2012-10-05  0:48             ` David Gibson
2012-10-05  9:12             ` Benjamin Herrenschmidt
2012-10-05 10:32               ` Alexander Graf
2012-10-05  5:30           ` Nikunj A Dadhania
2012-10-05  5:44             ` Avik Sil

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=506D8283.6090604@linux.vnet.ibm.com \
    --to=aviksil@linux.vnet.ibm.com \
    --cc=agraf@suse.de \
    --cc=benh@au1.ibm.com \
    --cc=gleb@redhat.com \
    --cc=nikunj@linux.vnet.ibm.com \
    --cc=qemu-devel@nongnu.org \
    --cc=qemu-ppc@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).