RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Document URL: 

Chapter 8. Cloning virtual machines Red Hat Enterprise Linux 8 | Red Hat Customer Portal
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/cloning-virtual-machines_configuring-and-managing-virtualization


Section Number and Name: 

8.2. Creating a virtual machine template

Describe the issue: 

The following URL in RHEL provides specific details on manually removing unique information from a VM to make it a template.

Chapter 4. Cloning Virtual Machines Red Hat Enterprise Linux 7 | Red Hat Customer Portal
https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/cloning_virtual_machines

But the same information is not present in RHEL 8 docs creating confusion for the Customer on the steps to follow.

Suggestions for improvement: 

Request for the instructions to manually remove unique information

Additional information:

The firstboot is replaced with gnome-initial-setup in RHEL8.
To configure the virtual machine to run configuration wizards on the next boot, we can remove the gnome-initial-setup-done file.

# rm ~/.config/gnome-initial-setup-done

It looks other configuration steps in RHEL7's document can use for my RHEL8.

Ryosuke.

Hello Anitha, my apologies for the delay in responding.

Just to clarify, do I understand it correctly that you're requesting we add a RHEL 7 equivalent of the VM templating instructions that we have in RHEL 8 [1] to the RHEL 7 virt documentation [2] ?

[1] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/8/html/configuring_and_managing_virtualization/cloning-virtual-machines_configuring-and-managing-virtualization#preparing-a-virtual-machine-template_cloning-virtual-machines
[2] https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/html/virtualization_deployment_and_administration_guide/cloning_virtual_machines

Thank you, and have an excellent day!
Jirka