From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from eggs.gnu.org ([208.118.235.92]:44574) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJkeV-0007gr-6B for qemu-devel@nongnu.org; Thu, 04 Oct 2012 08:35:50 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1TJkeK-0007IO-4U for qemu-devel@nongnu.org; Thu, 04 Oct 2012 08:35:43 -0400 Received: from e23smtp06.au.ibm.com ([202.81.31.148]:47715) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1TJkeJ-0007G4-Ih for qemu-devel@nongnu.org; Thu, 04 Oct 2012 08:35:32 -0400 Received: from /spool/local by e23smtp06.au.ibm.com with IBM ESMTP SMTP Gateway: Authorized Use Only! Violators will be prosecuted for from ; Thu, 4 Oct 2012 22:33:48 +1000 Message-ID: <506D8283.6090604@linux.vnet.ibm.com> Date: Thu, 04 Oct 2012 18:05:15 +0530 From: Avik Sil MIME-Version: 1.0 References: <50641A82.4030708@linux.vnet.ibm.com> <1348738150.24701.21.camel@pasglop> <20120927095136.GI23096@redhat.com> <506D6B20.7020508@linux.vnet.ibm.com> <20121004112217.GA27396@redhat.com> <506D7317.40906@linux.vnet.ibm.com> <49B19A15-2864-4354-BA5E-66CBA139FD84@suse.de> <506D7EA4.6040300@linux.vnet.ibm.com> <751E4F90-614C-41A7-844A-6280BA05345D@suse.de> In-Reply-To: <751E4F90-614C-41A7-844A-6280BA05345D@suse.de> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: Re: [Qemu-devel] [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , To: Alexander Graf Cc: Benjamin Herrenschmidt , "qemu-ppc@nongnu.org List" , Nikunj A Dadhania , Gleb Natapov , qemu-devel qemu-devel >>>>> 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