Merge pull request #52097 from SNiemann15/lso_bypathid

[BZ2115693] Add LSO note to add serial number for IBM Z

Author: stevsmit

modules/persistent-storage-local-create-cr.adoc

@@ -25,6 +25,7 @@ Local volumes cannot be created by dynamic provisioning. Instead, persistent vol
 Do not use different storage class names for the same device. Doing so will create multiple persistent volumes (PVs).
 ====
 +
+--
 .Example: Filesystem
 [source,yaml]
 ----
@@ -54,14 +55,20 @@ spec:
 <2> Optional: A node selector containing a list of nodes where the local storage volumes are attached. This example uses the node hostnames, obtained from `oc get node`. If a value is not defined, then the Local Storage Operator will attempt to find matching disks on all available nodes.
 <3> The name of the storage class to use when creating persistent volume objects. The Local Storage Operator automatically creates the storage class if it does not exist. Be sure to use a storage class that uniquely identifies this set of local volumes.
 <4> The volume mode, either `Filesystem` or `Block`, that defines the type of local volumes.
++
+[NOTE]
+====
+A raw block volume (`volumeMode: Block`) is not formatted with a file system. Use this mode only if any application running on the pod can use raw block devices.
+====
 <5> The file system that is created when the local volume is mounted for the first time.
 <6> The path containing a list of local storage devices to choose from.
 <7> Replace this value with your actual local disks filepath to the `LocalVolume` resource `by-id`, such as `/dev/disk/by-id/wwn`. PVs are created for these local disks when the provisioner is deployed successfully.
 +
 [NOTE]
 ====
-A raw block volume (`volumeMode: block`) is not formatted with a file system. You should use this mode only if any application running on the pod can use raw block devices.
+If you are running {product-title} on {ibmzProductName} with {op-system-base} KVM, you must assign a serial number to your VM disk. Otherwise, the VM disk can not be identified after reboot. You can use the `virsh edit <VM>` command to add the `<serial>mydisk</serial>` definition.
 ====
+--
 +
 .Example: Block
 [source,yaml]
@@ -83,7 +90,7 @@ spec:
           - ip-10-0-144-180
   storageClassDevices:
     - storageClassName: "localblock-sc" <3>
-      volumeMode: Block  <4>
+      volumeMode: Block <4>
       devicePaths: <5>
         - /path/to/device <6>
 ----
@@ -93,7 +100,11 @@ spec:
 <4> The volume mode, either `Filesystem` or `Block`, that defines the type of local volumes.
 <5> The path containing a list of local storage devices to choose from.
 <6> Replace this value with your actual local disks filepath to the `LocalVolume` resource `by-id`, such as `dev/disk/by-id/wwn`. PVs are created for these local disks when the provisioner is deployed successfully.
-
++
+[NOTE]
+====
+If you are running {product-title} on {ibmzProductName} with {op-system-base} KVM, you must assign a serial number to your VM disk. Otherwise, the VM disk can not be identified after reboot. You can use the `virsh edit <VM>` command to add the `<serial>mydisk</serial>` definition.
+====
 
 . Create the local volume resource in your {product-title} cluster. Specify the file you just created:
 +