From 95d82e058e712c72aade88d29e6500ae1971132d Mon Sep 17 00:00:00 2001 From: danielclowers Date: Fri, 17 Jul 2026 11:10:17 -0400 Subject: [PATCH] CNV-87875: Add web console procedure for hot swapping VM secondary network --- ...ping-vm-secondary-network-web-console.adoc | 33 +++++++++++++++++++ .../virt-hot-swap-vm-secondary-network.adoc | 4 ++- 2 files changed, 36 insertions(+), 1 deletion(-) create mode 100644 modules/virt-hot-swapping-vm-secondary-network-web-console.adoc diff --git a/modules/virt-hot-swapping-vm-secondary-network-web-console.adoc b/modules/virt-hot-swapping-vm-secondary-network-web-console.adoc new file mode 100644 index 000000000000..c51d50f7acb4 --- /dev/null +++ b/modules/virt-hot-swapping-vm-secondary-network-web-console.adoc @@ -0,0 +1,33 @@ +// Module included in the following assemblies: +// +// * virt/vm_networking/virt-hot-swap-vm-secondary-network.adoc + +:_mod-docs-content-type: PROCEDURE +[id="virt-hot-swapping-vm-secondary-network-web-console_{context}"] += Hot swapping a virtual machine secondary network by using the web console + +[role="_abstract"] +You can hot swap the secondary network of a running virtual machine (VM) by using the {product-title} web console. Hot swapping the secondary network preserves the workload and avoids the need for a VM reboot. + +.Prerequisites + +* The VM is running and is live migratable. +* The target `NetworkAttachmentDefinition` object exists in the same namespace as the VM. If you created a `ClusterUserDefinedNetwork` object, verify that the cluster user-defined network controller has created the corresponding `NetworkAttachmentDefinition` object. + +.Procedure + +. Navigate to *Virtualization* -> *VirtualMachines* in the web console. +. Click a running VM to view the *VirtualMachine details* page. +. Click the *Configuration* tab and then click the *Network interfaces* tab. +. Click the Options menu {kebab} beside the network interface that you want to modify and select *Edit*. +. Select the target network from the *Network* list. +. Click *Save*. ++ +The network interface row displays a *Pending* label. A warning banner indicates that the VM has pending network changes. The pending changes are applied during the next live migration or reboot. + +.Verification + +. On the *VirtualMachine details* page, click the *Diagnostics* tab. +. Check the *Status conditions* table and verify that the `MigrationRequired` condition is listed with the reason `AutoMigrationDueToLiveUpdate`. ++ +After the live migration completes, the `MigrationRequired` condition disappears and the *Pending* label is removed from the network interface. diff --git a/virt/vm_networking/virt-hot-swap-vm-secondary-network.adoc b/virt/vm_networking/virt-hot-swap-vm-secondary-network.adoc index ed6ca8745ac8..f4ffe00f5ea2 100644 --- a/virt/vm_networking/virt-hot-swap-vm-secondary-network.adoc +++ b/virt/vm_networking/virt-hot-swap-vm-secondary-network.adoc @@ -7,7 +7,7 @@ include::_attributes/common-attributes.adoc[] toc::[] [role="_abstract"] -You can change the secondary network of a virtual machine (VM) without rebooting your VM. The change is transparent to the guest operating system, preserving properties like the MAC address. +You can change the secondary network of a virtual machine (VM) without rebooting your VM. The change is transparent to the guest operating system, preserving properties such as the MAC address. By hot swapping the secondary network, you can move a running VM to a different network segment or VLAN and apply new network policies or reconfigure network topology without interrupting the workload. {VirtProductName} supports hot swapping for VMs that are connected to an OVN-Kubernetes localnet and a Linux bridge secondary network. @@ -17,6 +17,8 @@ include::modules/virt-vm-nw-hot-swap-limitations.adoc[leveloffset=+1] include::modules/virt-live-updating-vm-nad-udn.adoc[leveloffset=+1] +include::modules/virt-hot-swapping-vm-secondary-network-web-console.adoc[leveloffset=+1] + [role="_additional-resources"] [id="additional-resources_{context}"]