From ba9b7c8375aac784fbe23beaeb91484ddd8e6829 Mon Sep 17 00:00:00 2001 From: Thomas Huth Date: Mon, 11 Nov 2024 11:55:06 +0100 Subject: [PATCH 3/9] docs/system/bootindex: Make it clear that s390x can also boot from virtio-net RH-Author: Thomas Huth RH-MergeRequest: 297: [c10s] Fixes for the new s390x "boot order" feature RH-Jira: RHEL-68444 RH-Acked-by: Miroslav Rezanina RH-Commit: [2/8] ae20c66e424d64840012b4725166a1bde2579cbc (thuth/qemu-kvm-cs9) Let's make it clear that s390x can also boot from virtio-net, to avoid that people think that s390x can only boot from disk devices. Reported-by: Boris Fiuczynski Message-ID: <20241111105506.264640-1-thuth@redhat.com> Reviewed-by: Prasad Pandit Reviewed-by: Boris Fiuczynski Signed-off-by: Thomas Huth (cherry picked from commit b8c5fdc6588f82d95807be0eb2215d215a3ba16e) --- docs/system/bootindex.rst | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/system/bootindex.rst b/docs/system/bootindex.rst index 988f7b3beb..5e1b33ee22 100644 --- a/docs/system/bootindex.rst +++ b/docs/system/bootindex.rst @@ -53,7 +53,7 @@ booting. For instance, the x86 PC BIOS boot specification allows only one disk to be bootable. If boot from disk fails for some reason, the x86 BIOS won't retry booting from other disk. It can still try to boot from floppy or net, though. In the case of s390x BIOS, the BIOS will try up to -8 total devices, any number of which may be disks. +8 total devices, any number of which may be disks or virtio-net devices. Sometimes, firmware cannot map the device path QEMU wants firmware to boot from to a boot method. It doesn't happen for devices the firmware -- 2.39.3