// Module included in the following assemblies:
//
// * virt/vm_networking/virt-hot-swap-vm-secondary-network.adoc

:_mod-docs-content-type: REFERENCE
[id="virt-vm-nw-hot-swap-limitations_{context}"]
= Hot swap limitations

[role="_abstract"]
{VirtProductName} supports hot swapping for VMs that are connected to an OVN-Kubernetes localnet and a Linux bridge secondary network.

Consider the following limitations before hot swapping a VM secondary network:

* Hot swapping only works for VMs that are live migratable.
* Network connectivity might be interrupted during the live migration process.
* If you update network references for multiple VMs, the updates might be queued because only a limited number of live migrations can run in parallel across the cluster.
* You cannot hot swap to a new network binding type or a Container Network Interface (CNI) plugin. For example, you cannot change from bridge binding to SR-IOV binding.
* The target `NetworkAttachmentDefinition` and `ClusterUserDefinedNetwork` objects must be valid and all referenced resources such as bridges, VLANs, and network resources must exist. Migration completes even if the network configuration is invalid, but the VM will lose network connectivity.
* This feature applies only to secondary networks attached by using `NetworkAttachmentDefinition` or `ClusterUserDefinedNetwork` manifests. You cannot hot swap the primary pod network, regardless of whether it uses the default cluster network or a custom primary user-defined network.
* If the new network requires a different IP configuration, such as a different subnet or gateway, you must reconfigure the guest operating system network settings. The hot swap does not automatically update the guest network configuration.


