Migrating from KVM for IBM z Systems to KVM integrated with SUSE Linux Enterprise ServerSUSE Linux Enterprise Server for z Systems and LinuxONE
On March 7, 2017, IBM announced the end of support for their product KVM for IBM z Systems. To learn more, read the official IBM Withdrawal Announcement at https://www-01.ibm.com/common/ssi/rep_ca/8/897/ENUS917-048/ENUS917-048.PDF. Preceding the IBM announcement on March 1, 2017, SUSE announced full support for KVM delivered with SUSE Linux Enterprise Server for z Systems and LinuxONE 12 SP2 and newer versions. You can find more details in the article at https://www.suse.com/communities/blog/virtualization-suse-kvm-support-ibm-z-systems-linuxone/.
Customers that have deployed or are testing KVM for IBM z Systems may have been
using the IBM Redbook
Getting Started with KVM for IBM z Systems at
http://www.redbooks.ibm.com/abstracts/sg248332.html?Open&pdfbookmark . This SUSE Best Practices document will also cover the most important details
about how to migrate a virtual machine from KVM for IBM z Systems to KVM delivered
with SUSE Linux Enterprise Server.
1.0 Installing SUSE Linux Enterprise Server for z Systems and LinuxONE as KVM Host
Like KVM for IBM z Systems, KVM integrated with SUSE Linux Enterprise Server for z Systems and LinuxONE is
supported when installed into an LPAR. The section
Installation on IBM z
Systems of the SUSE Linux Enterprise Server Deployment Guide at https://www.suse.com/documentation/sles-12/book_sle_deployment/data/cha_zseries.html provides information regarding supported hardware and memory requirements for
installing into an LPAR. The section
Overiew of an LPAR Installation at
https://www.suse.com/documentation/sles-12/book_sle_deployment/data/sec_zseries_prep.html#sec_prep_inst_types reviews the preparation and initial steps in starting the SUSE Linux Enterprise
Server Installation System.
A suggested partitioning layout includes separating the storage of the KVM disk images from the operating system. Using the Btrfs file system for the operating system enables rollback capabilities when patching the system. The default location for the KVM disk images is /var/lib/libvirt/images/. It is recommended to use Logical Volume Manager with the XFS file system for KVM disk images.
Enabling the firewall is not a requirement but a security decision for each organization. Discusse with your organization's security group if to enable the firewall.
Software Selection in the installer, use the list below for the
minimum and suggested additional patterns to be installed.
Minimal System (Appliances)
Help and Support Documentation
KVM Virtualization Host and tools
Suggested additional Patterns:
GNOME Desktop Environment & X Window System (needed for managing virtual machines using a GUI)
Make sure to register and fully patch the KVM host either during the initial installation or after the installation is complete.
2.0 Managing KVM Instances
It is recommended to use the SUSE-provided utilities that manage virtual machines
using the libvirt API. The section
Managing Virtual Machines with libvirt
of the Virtualization Guide at https://www.suse.com/documentation/sles-12/book_virt/data/part_virt_libvirt.html provides information about using both command line and GUI based tools. It is
strongly recommended to use the previous link because it contains detailed information
about VM installation and management as well as storage and network management for VMs.
The sections below provide additional information about accessing a particular
2.1 Using the Command Line to Create and Manage Instances
virsh and virt-install are
the command line utilities to manage virtual machines. These utilities are installed
as part of the KVM virtualization host and tools pattern. The section
Virtualization Console Tools at https://www.suse.com/documentation/sles-12/book_virt/data/sec_tools_intro_console.html provides an introdution to these utilites.
The virsh and virsh-installtools can be used both from an SSH session, or in a terminal/console session when working via Virtual Network Computing (VNC).
Connect via SSH to log in to the KVM host to use virsh and virt-install.
2.2 Managing Virtual Machines Using a GUI
Virtual Machine Manager (virt-manager) is the GUI tool
used to manage virtual machines. This utility is installed as part of the KVM
virtualization host and tools pattern. The section
Tools of the Virtualization Guide at https://www.suse.com/documentation/sles-12/book_virt/data/sec_tools_intro_gui.html provides an introduction.
To access the virt-manager GUI, use X11 forwarding via SSH or vncviewer. X11 forwarding is a good option if the connection (local or metropolitan area network) speed between the client and the KVM host has relatively low latency. Use vncviewer if you find that X11 redirection is too slow. Perform the following actions to enable access to virt-manager.
Both X11 forwarding via SSH and vncviewer
Install the suggested additional patterns listed above using YaST or Zypper
For X11 forwarding via SSH
From a client terminal, type ssh -X <KVM hostname>
For vncviewer access to the KVM host
Start YaST and go into
Network Services | Remote Administration (VNC)
Open Port in Firewallif the firewall was enabled during the installation
Allow Remote Administration Without Session Managementand click OK
From a client terminal, type vncviewer <KVM hostname:1>
Log in to the KVM host in the window opened by the previous command
Applications | Utilites | XTerm
Within the X11 forwarding via SSH client terminal and XTerm window in vncviewer window
3.0 Moving an Existing KVM for IBM z Systems Virtual Machine to KVM in SUSE Linux Enterprise Server
The following section explains how to move a KVM for IBM z Systems virtual machine to KVM
integrated with SUSE Linux Enterprise Server. A VM was created on KVM for IBM z Systems
following the section 3.7 of the IBM Redbook
Getting Started with KVM for IBM z
Systems at http://www.redbooks.ibm.com/redbooks/pdfs/sg248332.pdf. This
procedure assumes that the KVM for IBM z Systems VM has a virtual disk file and is
attached to a virtual network defined using libvirt. Below is the XML definition of the
VM and virtual network based on the example in the IBM Redbook.
<domain type='kvm'> <name>s12s2</name> <uuid>97968b48-295e-465a-9265-2cc89f4fb9cd</uuid> <description>IBM KVM to SLES KVM</description> <memory unit='KiB'>524288</memory> <currentMemory unit='KiB'>524288</currentMemory> <vcpu placement='static'>1</vcpu> <os> <type arch='s390x' machine='s390-ccw-kvmibm-1.1.1'>hvm</type> <boot dev='hd'/> </os> <clock offset='utc'/> <on_poweroff>destroy</on_poweroff> <on_reboot>restart</on_reboot> <on_crash>preserve</on_crash> <devices> <emulator>/usr/bin/qemu-system-s390x</emulator> <disk type='file' device='disk'> <driver name='qemu' type='qcow2'/> <source file='/var/lib/libvirt/images/s12s2.img'/> <target dev='vda' bus='virtio'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0002'/> </disk> <interface type='bridge'> <mac address='52:54:00:58:35:20'/> <source bridge='virbr0'/> <model type='virtio'/> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0000'/> </interface> <console type='pty'> <target type='sclp' port='0'/> </console> <memballoon model='virtio'> <address type='ccw' cssid='0xfe' ssid='0x0' devno='0x0001'/> </memballoon> </devices> </domain>
Virtual Network Definition
<network> <name>default</name> <uuid>4e4ab47a-3889-4eba-81d0-dda245a44091</uuid> <forward mode='nat'> <nat> <port start='1024' end='65535'/> </nat> </forward> <bridge name='virbr0' stp='on' delay='0'/> <mac address='52:54:00:c0:47:bc'/> <ip address='192.168.122.1' netmask='255.255.255.0'> <dhcp> <range start='192.168.122.2' end='192.168.122.254'/> </dhcp> </ip> </network>
The VM and network definition for a customer deployment may be considerably different but the basic procedure to move the VM to KVM in SUSE Linux Enterprise Server will be the same, as outlined below.
Connect via SSH to the KVM for IBM z Systems host as root or as the user used to define VMs
Find a VM configured on the KVM for IBM z Systems host that you want to move to a SUSE Linux Enterprise Server KVM host
List all defined VMs with virsh list --all and choose the VM to migrate
Dump the XML definition of the VM to be migrated via the command 'virsh dumpxml <vmname> > ~/<vmname>.xml' (where <vmname> is the name of a VM to move)
View the content of the XML file via the command less ~/<vmname>.xml and make note of the following information
Location of the VM disk file(s) which is <source file= in the above VM definition
The name of the network bridge(s) which is <source bridge= in the above VM definition
Determine the virtual network(s) associated to the VM
List all defined network bridges with virsh net-list --all
Repeat the command virsh net-dumpxml <network name> > ~/net-<network name>.xmlfor each network bridge to dump the XML definition for all of the network bridges
Repeat the command grep -H <network bridge name from the information gathered before> ~/net-*.xml for each network bridge to determine the XML file to migrate
Make note of the filename(s) from the grep output above
Copy the VM disk file(s), the VM xml file and the network xml file(s) to the SUSE Linux Enterprise Server KVM host
Enter the command rsync -S --progress <VM disk file> <VM xml file> <network xml> <SLES KVM Host>:/var/lib/libvirt/images
Connect via SSH to the SUSE Linux Enterprise Server KVM host as root or as the user used to define VMs
Remove the bridge if it already exists on the KVM host
Type virsh net-list --all
Type virsh net-undefine <network name> when the network name is the same as a network name on the KVM for IBM z Systems host
Add the bridge from KVM for IBM z Systems
Define the network name(s) with virsh net-define <network xml file(s)>
Start the network name(s) with virsh net-start <network xml file(s)>
Autostart the network name(s) on system restart with virsh net-autostart <network xml file(s)>
Edit the VM xml file by changing
<type arch='s390x' machine='s390-ccw-kvmibm-1.1.1'>hvm</type>
<type arch='s390x' machine='s390-ccw-virtio'>hvm</type>
Define the VM in SUSE Linux Enterprise Server KVM
Use the command virsh define <VM xml file>
Start and verify the newly migrated VM is running
Start the VM with virsh start <VM name>
Verify that the VM is running with virsh list
Connect via SSH to the VM to verify that networking is working
For basic troubleshooting information review the section
Troubleshooting of the SUSE Linux Enterprise Server Administration
guide at https://www.suse.com/documentation/sles-12/book_sle_admin/data/part_trouble.html . In case of specific issues, opening a support request may be necessary. To receive
support, you need an appropriate subscription with SUSE; for more information, see http://www.suse.com/products/server/services-and-support/ .
4.1 Common Problems and Their Solutions
If there is a solution you want to see added to this section, use the comment field at the top of the HTML version of this document for your feedback. This section will be updated with suggested solutions over time. Please come back and check often.
5.0 Legal Notice
Copyright ©2006– 2017 SUSE LLC and contributors. All rights reserved.
Permission is granted to copy, distribute and/or modify this document under the terms
of the GNU Free Documentation License, Version 1.2 or (at your option) version 1.3; with
the Invariant Section being this copyright notice and license. A copy of the license
version 1.2 is included in the section entitled
GNU Free Documentation
SUSE, the SUSE logo and YaST are registered trademarks of SUSE LLC in the United States and other countries. For SUSE trademarks, see http://www.suse.com/company/legal/.
Linux is a registered trademark of Linus Torvalds. All other names or trademarks mentioned in this document may be trademarks or registered trademarks of their respective owners.
All information found in this document has been compiled with utmost attention to detail. However, this does not guarantee complete accuracy. Neither SUSE LLC, its affiliates, the authors, nor the translators shall be held liable for possible errors or the consequences thereof.
6.0 GNU Free Documentation License
Copyright (C) 2000, 2001, 2002 Free Software Foundation, Inc. 51 Franklin St, Fifth Floor, Boston, MA 02110-1301 USA. Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
The purpose of this License is to make a manual, textbook, or other functional and useful document "free" in the sense of freedom: to assure everyone the effective freedom to copy and redistribute it, with or without modifying it, either commercially or non-commercially. Secondarily, this License preserves for the author and publisher a way to get credit for their work, while not being considered responsible for modifications made by others.
This License is a kind of "copyleft", which means that derivative works of the document must themselves be free in the same sense. It complements the GNU General Public License, which is a copyleft license designed for free software.
We have designed this License to use it for manuals for free software, because free software needs free documentation: a free program should come with manuals providing the same freedoms that the software does. But this License is not limited to software manuals; it can be used for any textual work, regardless of subject matter or whether it is published as a printed book. We recommend this License principally for works whose purpose is instruction or reference.
1. APPLICABILITY AND DEFINITIONS
This License applies to any manual or other work, in any medium, that contains a notice placed by the copyright holder saying it can be distributed under the terms of this License. Such a notice grants a world-wide, royalty-free license, unlimited in duration, to use that work under the conditions stated herein. The "Document", below, refers to any such manual or work. Any member of the public is a licensee, and is addressed as "you". You accept the license if you copy, modify or distribute the work in a way requiring permission under copyright law.
A "Modified Version" of the Document means any work containing the Document or a portion of it, either copied verbatim, or with modifications and/or translated into another language.
A "Secondary Section" is a named appendix or a front-matter section of the Document that deals exclusively with the relationship of the publishers or authors of the Document to the Document's overall subject (or to related matters) and contains nothing that could fall directly within that overall subject. (Thus, if the Document is in part a textbook of mathematics, a Secondary Section may not explain any mathematics.) The relationship could be a matter of historical connection with the subject or with related matters, or of legal, commercial, philosophical, ethical or political position regarding them.
The "Invariant Sections" are certain Secondary Sections whose titles are designated, as being those of Invariant Sections, in the notice that says that the Document is released under this License. If a section does not fit the above definition of Secondary then it is not allowed to be designated as Invariant. The Document may contain zero Invariant Sections. If the Document does not identify any Invariant Sections then there are none.
The "Cover Texts" are certain short passages of text that are listed, as Front-Cover Texts or Back-Cover Texts, in the notice that says that the Document is released under this License. A Front-Cover Text may be at most 5 words, and a Back-Cover Text may be at most 25 words.
A "Transparent" copy of the Document means a machine-readable copy, represented in a format whose specification is available to the general public, that is suitable for revising the document straightforwardly with generic text editors or (for images composed of pixels) generic paint programs or (for drawings) some widely available drawing editor, and that is suitable for input to text formatters or for automatic translation to a variety of formats suitable for input to text formatters. A copy made in an otherwise Transparent file format whose markup, or absence of markup, has been arranged to thwart or discourage subsequent modification by readers is not Transparent. An image format is not Transparent if used for any substantial amount of text. A copy that is not "Transparent" is called "Opaque".
Examples of suitable formats for Transparent copies include plain ASCII without markup, Texinfo input format, LaTeX input format, SGML or XML using a publicly available DTD, and standard-conforming simple HTML, PostScript or PDF designed for human modification. Examples of transparent image formats include PNG, XCF and JPG. Opaque formats include proprietary formats that can be read and edited only by proprietary word processors, SGML or XML for which the DTD and/or processing tools are not generally available, and the machine-generated HTML, PostScript or PDF produced by some word processors for output purposes only.
The "Title Page" means, for a printed book, the title page itself, plus such following pages as are needed to hold, legibly, the material this License requires to appear in the title page. For works in formats which do not have any title page as such, "Title Page" means the text near the most prominent appearance of the work's title, preceding the beginning of the body of the text.
A section "Entitled XYZ" means a named subunit of the Document whose title either is precisely XYZ or contains XYZ in parentheses following text that translates XYZ in another language. (Here XYZ stands for a specific section name mentioned below, such as "Acknowledgements", "Dedications", "Endorsements", or "History".) To "Preserve the Title" of such a section when you modify the Document means that it remains a section "Entitled XYZ" according to this definition.
The Document may include Warranty Disclaimers next to the notice which states that this License applies to the Document. These Warranty Disclaimers are considered to be included by reference in this License, but only as regards disclaiming warranties: any other implication that these Warranty Disclaimers may have is void and has no effect on the meaning of this License.
2. VERBATIM COPYING
You may copy and distribute the Document in any medium, either commercially or noncommercially, provided that this License, the copyright notices, and the license notice saying this License applies to the Document are reproduced in all copies, and that you add no other conditions whatsoever to those of this License. You may not use technical measures to obstruct or control the reading or further copying of the copies you make or distribute. However, you may accept compensation in exchange for copies. If you distribute a large enough number of copies you must also follow the conditions in section 3.
You may also lend copies, under the same conditions stated above, and you may publicly display copies.
3. COPYING IN QUANTITY
If you publish printed copies (or copies in media that commonly have printed covers) of the Document, numbering more than 100, and the Document's license notice requires Cover Texts, you must enclose the copies in covers that carry, clearly and legibly, all these Cover Texts: Front-Cover Texts on the front cover, and Back-Cover Texts on the back cover. Both covers must also clearly and legibly identify you as the publisher of these copies. The front cover must present the full title with all words of the title equally prominent and visible. You may add other material on the covers in addition. Copying with changes limited to the covers, as long as they preserve the title of the Document and satisfy these conditions, can be treated as verbatim copying in other respects.
If the required texts for either cover are too voluminous to fit legibly, you should put the first ones listed (as many as fit reasonably) on the actual cover, and continue the rest onto adjacent pages.
If you publish or distribute Opaque copies of the Document numbering more than 100, you must either include a machine-readable Transparent copy along with each Opaque copy, or state in or with each Opaque copy a computer-network location from which the general network-using public has access to download using public-standard network protocols a complete Transparent copy of the Document, free of added material. If you use the latter option, you must take reasonably prudent steps, when you begin distribution of Opaque copies in quantity, to ensure that this Transparent copy will remain thus accessible at the stated location until at least one year after the last time you distribute an Opaque copy (directly or through your agents or retailers) of that edition to the public.
It is requested, but not required, that you contact the authors of the Document well before redistributing any large number of copies, to give them a chance to provide you with an updated version of the Document.
You may copy and distribute a Modified Version of the Document under the conditions of sections 2 and 3 above, provided that you release the Modified Version under precisely this License, with the Modified Version filling the role of the Document, thus licensing distribution and modification of the Modified Version to whoever possesses a copy of it. In addition, you must do these things in the Modified Version:
Use in the Title Page (and on the covers, if any) a title distinct from that of the Document, and from those of previous versions (which should, if there were any, be listed in the History section of the Document). You may use the same title as a previous version if the original publisher of that version gives permission.
List on the Title Page, as authors, one or more persons or entities responsible for authorship of the modifications in the Modified Version, together with at least five of the principal authors of the Document (all of its principal authors, if it has fewer than five), unless they release you from this requirement.
State on the Title page the name of the publisher of the Modified Version, as the publisher.
Preserve all the copyright notices of the Document.
Add an appropriate copyright notice for your modifications adjacent to the other copyright notices.
Include, immediately after the copyright notices, a license notice giving the public permission to use the Modified Version under the terms of this License, in the form shown in the Addendum below.
Preserve in that license notice the full lists of Invariant Sections and required Cover Texts given in the Document's license notice.
Include an unaltered copy of this License.
Preserve the section Entitled "History", Preserve its Title, and add to it an item stating at least the title, year, new authors, and publisher of the Modified Version as given on the Title Page. If there is no section Entitled "History" in the Document, create one stating the title, year, authors, and publisher of the Document as given on its Title Page, then add an item describing the Modified Version as stated in the previous sentence.
Preserve the network location, if any, given in the Document for public access to a Transparent copy of the Document, and likewise the network locations given in the Document for previous versions it was based on. These may be placed in the "History" section. You may omit a network location for a work that was published at least four years before the Document itself, or if the original publisher of the version it refers to gives permission.
For any section Entitled "Acknowledgements" or "Dedications", Preserve the Title of the section, and preserve in the section all the substance and tone of each of the contributor acknowledgements and/or dedications given therein.
Preserve all the Invariant Sections of the Document, unaltered in their text and in their titles. Section numbers or the equivalent are not considered part of the section titles.
Delete any section Entitled "Endorsements". Such a section may not be included in the Modified Version.
Do not retitle any existing section to be Entitled "Endorsements" or to conflict in title with any Invariant Section.
Preserve any Warranty Disclaimers.
If the Modified Version includes new front-matter sections or appendices that qualify as Secondary Sections and contain no material copied from the Document, you may at your option designate some or all of these sections as invariant. To do this, add their titles to the list of Invariant Sections in the Modified Version's license notice. These titles must be distinct from any other section titles.
You may add a section Entitled "Endorsements", provided it contains nothing but endorsements of your Modified Version by various parties--for example, statements of peer review or that the text has been approved by an organization as the authoritative definition of a standard.
You may add a passage of up to five words as a Front-Cover Text, and a passage of up to 25 words as a Back-Cover Text, to the end of the list of Cover Texts in the Modified Version. Only one passage of Front-Cover Text and one of Back-Cover Text may be added by (or through arrangements made by) any one entity. If the Document already includes a cover text for the same cover, previously added by you or by arrangement made by the same entity you are acting on behalf of, you may not add another; but you may replace the old one, on explicit permission from the previous publisher that added the old one.
The author(s) and publisher(s) of the Document do not by this License give permission to use their names for publicity for or to assert or imply endorsement of any Modified Version.
5. COMBINING DOCUMENTS
You may combine the Document with other documents released under this License, under the terms defined in section 4 above for modified versions, provided that you include in the combination all of the Invariant Sections of all of the original documents, unmodified, and list them all as Invariant Sections of your combined work in its license notice, and that you preserve all their Warranty Disclaimers.
The combined work need only contain one copy of this License, and multiple identical Invariant Sections may be replaced with a single copy. If there are multiple Invariant Sections with the same name but different contents, make the title of each such section unique by adding at the end of it, in parentheses, the name of the original author or publisher of that section if known, or else a unique number. Make the same adjustment to the section titles in the list of Invariant Sections in the license notice of the combined work.
In the combination, you must combine any sections Entitled "History" in the various original documents, forming one section Entitled "History"; likewise combine any sections Entitled "Acknowledgements", and any sections Entitled "Dedications". You must delete all sections Entitled "Endorsements".
6. COLLECTIONS OF DOCUMENTS
You may make a collection consisting of the Document and other documents released under this License, and replace the individual copies of this License in the various documents with a single copy that is included in the collection, provided that you follow the rules of this License for verbatim copying of each of the documents in all other respects.
You may extract a single document from such a collection, and distribute it individually under this License, provided you insert a copy of this License into the extracted document, and follow this License in all other respects regarding verbatim copying of that document.
7. AGGREGATION WITH INDEPENDENT WORKS
A compilation of the Document or its derivatives with other separate and independent documents or works, in or on a volume of a storage or distribution medium, is called an "aggregate" if the copyright resulting from the compilation is not used to limit the legal rights of the compilation's users beyond what the individual works permit. When the Document is included in an aggregate, this License does not apply to the other works in the aggregate which are not themselves derivative works of the Document.
If the Cover Text requirement of section 3 is applicable to these copies of the Document, then if the Document is less than one half of the entire aggregate, the Document's Cover Texts may be placed on covers that bracket the Document within the aggregate, or the electronic equivalent of covers if the Document is in electronic form. Otherwise they must appear on printed covers that bracket the whole aggregate.
Translation is considered a kind of modification, so you may distribute translations of the Document under the terms of section 4. Replacing Invariant Sections with translations requires special permission from their copyright holders, but you may include translations of some or all Invariant Sections in addition to the original versions of these Invariant Sections. You may include a translation of this License, and all the license notices in the Document, and any Warranty Disclaimers, provided that you also include the original English version of this License and the original versions of those notices and disclaimers. In case of a disagreement between the translation and the original version of this License or a notice or disclaimer, the original version will prevail.
If a section in the Document is Entitled "Acknowledgements", "Dedications", or "History", the requirement (section 4) to Preserve its Title (section 1) will typically require changing the actual title.
You may not copy, modify, sublicense, or distribute the Document except as expressly provided for under this License. Any other attempt to copy, modify, sublicense or distribute the Document is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.
10. FUTURE REVISIONS OF THIS LICENSE
The Free Software Foundation may publish new, revised versions of the GNU Free Documentation License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns. See http://www.gnu.org/copyleft/.
Each version of the License is given a distinguishing version number. If the Document specifies that a particular numbered version of this License "or any later version" applies to it, you have the option of following the terms and conditions either of that specified version or of any later version that has been published (not as a draft) by the Free Software Foundation. If the Document does not specify a version number of this License, you may choose any version ever published (not as a draft) by the Free Software Foundation.
ADDENDUM: How to use this License for your documents
Copyright (c) YEAR YOUR NAME. Permission is granted to copy, distribute and/or modify this document under the terms of the GNU Free Documentation License, Version 1.2 or any later version published by the Free Software Foundation; with no Invariant Sections, no Front-Cover Texts, and no Back-Cover Texts. A copy of the license is included in the section entitled "GNU Free Documentation License".
If you have Invariant Sections, Front-Cover Texts and Back-Cover Texts, replace the "with...Texts". line with this:
with the Invariant Sections being LIST THEIR TITLES, with the Front-Cover Texts being LIST, and with the Back-Cover Texts being LIST.
If you have Invariant Sections without Cover Texts, or some other combination of the three, merge those two alternatives to suit the situation.
If your document contains nontrivial examples of program code, we recommend releasing these examples in parallel under your choice of free software license, such as the GNU General Public License, to permit their use in free software.