Lines Matching full:the

4 QEMU can tell QEMU-aware guest firmware (like the x86 PC BIOS)
6 A simple way to set this order is to use the ``-boot order=`` option,
8 property on the individual block or net devices you specify
9 on the QEMU command line.
11 The ``bootindex`` properties are used to determine the order in which
12 firmware will consider devices for booting the guest OS. If the
13 ``bootindex`` property is not set for a device, it gets the lowest
18 Some guest machine types (for instance the s390x machines) do
44 Given the command above, firmware should try to boot from the e1000 NIC
45 first.  If this fails, it should try the virtio NIC next; if this fails
46 too, it should try the virtio disk, and then the IDE disk.
52 booting.  For instance, the x86 PC BIOS boot specification allows only one
53 disk to be bootable.  If boot from disk fails for some reason, the x86 BIOS
55 floppy or net, though. In the case of s390x BIOS, the BIOS will try up to
58 Sometimes, firmware cannot map the device path QEMU wants firmware to
59 boot from to a boot method.  It doesn't happen for devices the firmware
61 booting, and the same option ROM is used for booting from more then one
62 device, the firmware may not be able to ask the option ROM to boot from
63 a particular device reliably.  For instance with the PC BIOS, if a SCSI HBA
65 the option ROM will have a boot method for each of them, but it is not
67 shortcoming of the PC BIOS boot specification.
72 Note that it does not make sense to use the bootindex property together
73 with the ``-boot order=...`` (or ``-boot once=...``) parameter. The guest
74 firmware implementations normally either support the one or the other,
75 but not both parameters at the same time. Mixing them will result in
76 undefined behavior, and thus the guest firmware will likely not boot
77 from the expected devices.