diff --git a/CHANGELOG.md b/CHANGELOG.md
index 051addd332d5..58af94cd346f 100644
--- a/CHANGELOG.md
+++ b/CHANGELOG.md
@@ -16,6 +16,9 @@ and this project adheres to
   onwards. Users of Firecracker will need to backport the relevant patches on
   top of their 6.1 kernels to make use of the feature.
 
+- [#4731](https://github.com/firecracker-microvm/firecracker/pull/4731): Added
+  support for modifying the host device name during snapshot restore.
+
 ### Changed
 
 ### Deprecated
diff --git a/docs/snapshotting/network-for-clones.md b/docs/snapshotting/network-for-clones.md
index 59bcb4b2db67..0aca1a944155 100644
--- a/docs/snapshotting/network-for-clones.md
+++ b/docs/snapshotting/network-for-clones.md
@@ -146,6 +146,20 @@ Otherwise, packets originating from the guest might be using old Link Layer
 Address for up to arp cache timeout seconds. After said timeout period,
 connectivity will work both ways even without an explicit flush.
 
+### Renaming host device names
+
+In some environments where the jailer is not being used, restoring a snapshot
+may be tricky because the tap device on the host will not be the same as the tap
+device that the original VM was mapped to when it was snapshotted, as when the
+tap device come from a pool of such devices.
+
+In this case you can use the network_overrides parameter to snapshot restore to
+specify which network device (based on the name inside the VM, such as "eth0")
+maps to which host tap device (e.g. "vmtap01").
+
+This may require reconfiguration of the networking inside the VM so that it is
+still routable externally.
+
 ## Scalability evaluation
 
 We ran synthetic tests to determine the impact of the addtional iptables rules