Bug 2221953

Summary: Nowhere we state that creating a disk image with Image Builder creates BIOS+UEFI bootable images
Product: Red Hat Enterprise Linux 8 Reporter: Renaud Métrich <rmetrich>
Component: DocumentationAssignee: Eliane Ramos Pereira <elpereir>
Documentation sub component: default QA Contact: RHEL DPM <rhel-docs>
Status: CLOSED CURRENTRELEASE Docs Contact:
Severity: medium    
Priority: high CC: rhel-docs
Version: 8.8Keywords: Documentation
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-07-19 14:33:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Renaud Métrich 2023-07-11 11:35:25 UTC 
Document URL:

https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/composing_a_customized_rhel_system_image/preparing-and-deploying-kvm-guest-images-with-image-builder_composing-a-customized-rhel-system-image#doc-wrapper

Chapter 8. Preparing and deploying KVM guest images using image builder

Description:

when Image Builder generates a disk image, the partitioning is done to have a "dually bootable" image: BIOS mode or UEFI mode.
For this to happen, the partition table is created in GPT and a BIOSBOOT partition is created, along with the UEFI partition.

This seems to be confusing for customers that specify their own partition layour, because they do not expect to get these additional partitions.

Request:

Add a paragraph explaining the description above.