Lines Matching +full:no +full:- +full:map

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,
14 boot priority. There is no particular order in which devices with no
19 not support ``-boot order=``; on those machines you must always
22 There is no way to set a ``bootindex`` property if you are using
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 -----------
56 8 total devices, any number of which may be disks or virtio-net devices.
58 Sometimes, firmware cannot map the device path QEMU wants firmware to
66 possible to map from boot method back to a specific target.  This is a
70 ------------------------------------------
73 with the ``-boot order=...`` (or ``-boot once=...``) parameter. The guest