CNV-62386: Updated VM NIC hot plug/unplug docs

Author: Shikha Jhala

modules/virt-hot-plugging-bridge-network-interface-cli.adoc

@@ -12,8 +12,7 @@ Hot plug a secondary network interface to a virtual machine (VM) while the VM is
 
 * A network attachment definition is configured in the same namespace as your VM.
 * You have installed the `virtctl` tool.
-* You have installed the OpenShift CLI (`oc`).
-* You have permission to create and list `VirtualMachineInstanceMigration` objects.
+* You have installed the {oc-first}.
 
 .Procedure
 
@@ -24,12 +23,7 @@ Hot plug a secondary network interface to a virtual machine (VM) while the VM is
 $ virtctl start <vm_name> -n <namespace>
 ----
 
-. Use the following command to add the new network interface to the running VM. Editing the VM specification adds the new network interface to the VM and virtual machine instance (VMI) configuration but does not attach it to the running VM.
-+
-[source,terminal]
-----
-$ oc edit vm <vm_name>
-----
+. Use your preferred text editor to edit the `VirtualMachine` manifest, as shown in the following example:
 +
 .Example VM configuration
 [source,yaml]
@@ -61,13 +55,18 @@ template:
 <2> Specifies the name of the network. This must be the same as the `name` of the new network interface that you defined in the `template.spec.domain.devices.interfaces` list. 
 <3> Specifies the name of the `NetworkAttachmentDefinition` object. 
 
+. Save your changes and exit the editor.
 
-. To attach the network interface to the running VM, live migrate the VM by running the following command:
+. For the new configuration to take effect, apply the changes by running the following command. Applying the changes triggers automatic VM live migration and attaches the network interface to the running VM.
 +
 [source,terminal]
 ----
-$ virtctl migrate <vm_name>
+$ oc apply -f <filename>.yaml
 ----
++
+where:
+
+<filename>:: Specifies the name of your `VirtualMachine` manifest YAML file.
 
 .Verification
 
@@ -90,7 +89,7 @@ kubevirt-migrate-vm-lj62q   Running           vm-fedora
 kubevirt-migrate-vm-lj62q   Succeeded         vm-fedora
 ----
 
-. Verify that the new interface is added to the VM by checking the VMI status:
+. Verify that the new interface is added to the VM by checking the status of the virtual machine instance (VMI):
 +
 [source,terminal]
 ----

modules/virt-hot-unplugging-bridge-network-interface-cli.adoc

@@ -18,17 +18,11 @@ Hot unplugging is not supported for Single Root I/O Virtualization (SR-IOV) inte
 * Your VM must be running.
 * The VM must be created on a cluster running {VirtProductName} 4.14 or later.
 * The VM must have a bridge network interface attached.
-* You have permission to create and list `VirtualMachineInstanceMigration` objects.
 * You have installed the {oc-first}.
 
 .Procedure
 
-. Edit the VM specification to hot unplug a secondary network interface. Setting the interface state to `absent` detaches the network interface from the guest, but the interface still exists in the pod.
-+
-[source,terminal]
-----
-$ oc edit vm <vm_name>
-----
+. Using your preferred text editor, edit the `VirtualMachine` manifest file and set the interface state to `absent`. Setting the interface state to `absent` detaches the network interface from the guest, but the interface still exists in the pod.
 +
 .Example VM configuration
 [source,yaml]
@@ -58,9 +52,15 @@ template:
 ----
 <1> Set the interface state to `absent` to detach it from the running VM. Removing the interface details from the VM specification does not hot unplug the secondary network interface.
 
-. Remove the interface from the pod by migrating the VM:
+. Save your changes and exit the editor.
+
+. For the new configuration to take effect, apply the changes by running the following command. Applying the changes triggers automatic VM live migration and removes the interface from the pod.
 +
 [source,terminal]
 ----
-$ virtctl migrate <vm_name>
+$ oc apply -f <filename>.yaml
 ----
++
+where:
+
+<filename>:: Specifies the name of your `VirtualMachine` manifest YAML file.