docs/system/bootindex.rst

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,
19 not support ``-boot order=``; on those machines you must always
23 a short-form option like ``-hda`` or ``-cdrom``, so to use
25 into long-form ``-drive`` and ``-device`` option pairs.
28 -------
33 .. parsed-literal::
35   |qemu_system| -drive file=disk1.img,if=none,id=disk1 \\
36                 -device ide-hd,drive=disk1,bootindex=4 \\
37                 -drive file=disk2.img,if=none,id=disk2 \\
38                 -device virtio-blk-pci,drive=disk2,bootindex=3 \\
39                 -netdev type=user,id=net0 \\
40                 -device virtio-net-pci,netdev=net0,bootindex=2 \\
41                 -netdev type=user,id=net1 \\
42                 -device e1000,netdev=net1,bootindex=1
49 -----------
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
56 8 total devices, any number of which may be disks or virtio-net devices.
63 a particular device reliably.  For instance with the PC BIOS, if a SCSI HBA
67 shortcoming of the PC BIOS boot specification.
70 ------------------------------------------
73 with the ``-boot order=...`` (or ``-boot once=...``) parameter. The guest