Correctly adds resource requests/limits to Troubleshooting

Author: Shikha Jhala

backup_and_restore/application_backup_and_restore/troubleshooting.adoc

@@ -26,6 +26,29 @@ include::modules/velero-obtaining-by-accessing-binary.adoc[leveloffset=+1]
 include::modules/oadp-debugging-oc-cli.adoc[leveloffset=+1]
 include::modules/migration-debugging-velero-resources.adoc[leveloffset=+1]
 
+
+
+[id="oadp-pod-crash-resource-request"]
+== Pods crash or restart due to lack of memory or CPU
+
+If a Velero or Restic pod crashes due to a lack of memory or CPU, you can set specific resource requests for either of those resources.
+
+include::modules/oadp-pod-crash-set-resource-request-velero.adoc[leveloffset=+2]
+include::modules/oadp-pod-crash-set-resource-request-restic.adoc[leveloffset=+2]
+
+[IMPORTANT]
+====
+The values for the resource request fields must follow the same format as Kubernetes resource requirements.
+Also, if you do not specify `configuration.velero.podConfig.resourceAllocations` or `configuration.restic.podConfig.resourceAllocations`, the default `resources` specification for a Velero pod or a Restic pod is as follows:
+
+[source,yaml]
+----
+requests:
+  cpu: 500m
+  memory: 128Mi
+----
+====
+
 [id="issues-with-velero-and-admission-workbooks"]
 == Issues with Velero and admission webhooks
 

virt/install/preparing-cluster-for-virt.adoc

@@ -67,6 +67,18 @@ Live migration has the following requirements:
 * Sufficient RAM and network bandwidth.
 * If the virtual machine uses a host model CPU, the nodes must support the virtual machine's host model CPU.
 
+[NOTE]
+====
+You must ensure that there is enough memory request capacity in the cluster to support node drains that result in live migrations. You can determine the approximate required spare memory by using the following calculation:
+
+----
+Product of (Maximum number of nodes that can drain in parallel) and (Highest total VM memory request allocations across nodes)
+----
+
+The default xref:../../virt/live_migration/virt-live-migration-limits.adoc#virt-live-migration-limits[number of migrations that can run in parallel] in the cluster is 5.
+====
+
+
 // The HA section actually belongs to OpenShift, not Virt
 [id="cluster-high-availability-options_{context}"]
 == Cluster high-availability options