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 <fiuczy@linux.ibm.com>
Signed-off-by: Thomas Huth <thuth@redhat.com>
---
 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.47.0

On 11/11/24 11:55, Thomas Huth wrote:
> 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 <fiuczy@linux.ibm.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>   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

LGTM
Reviewed-by: Boris Fiuczynski <fiuczy@linux.ibm.com>

-- 
Mit freundlichen Grüßen/Kind regards
    Boris Fiuczynski

IBM Deutschland Research & Development GmbH
Vorsitzender des Aufsichtsrats: Wolfgang Wendt
Geschäftsführung: David Faller
Sitz der Gesellschaft: Böblingen
Registergericht: Amtsgericht Stuttgart, HRB 243294

On Mon, 11 Nov 2024 at 16:25, Thomas Huth <thuth@redhat.com> wrote:
> 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 <fiuczy@linux.ibm.com>
> Signed-off-by: Thomas Huth <thuth@redhat.com>
> ---
>  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.

Looks okay.
Reviewed-by: Prasad Pandit <pjp@fedoraproject.org>

Thank you.
---
  - Prasad