|
From: | Avik Sil |
Subject: | Re: [Qemu-ppc] Qemu boot device precedence over nvram boot-device setting |
Date: | Thu, 04 Oct 2012 17:48:44 +0530 |
User-agent: | Mozilla/5.0 (X11; Linux x86_64; rv:15.0) Gecko/20120911 Thunderbird/15.0.1 |
I looked at the bootindex stuff and found that when the bootindex is specified for the disk and cdrom it generates a string like: "/spapr-vio-bridge/spapr-vscsi/address@hidden/address@hidden,1 /spapr-vio-bridge/spapr-vscsi/address@hidden/address@hidden,0" Now converting/translating this to OF device path is going to be much trickier and might not be proper. So I propose a simple solution by introducing a global flag that checks if explicit -boot parameter is provided or not. The presence of this parameter is verified in SLOF firmware. The flag had to be introduced as boot_devices defaults to "cad" instead of null and passed to machine->init().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.
Regards, Avik
Alex
[Prev in Thread] | Current Thread | [Next in Thread] |