doc: remove outdated vsock snapshot info
We have recently added support for diff snapshots
for microVMs with vsock devices but the doc still
mentions that this is an unsupported scenario.
@@ -519,14 +519,12 @@ handle being snapshotted [here](https://lkml.org/lkml/2020/10/16/629).
## Known Issues
-### Vsock device limitations
+### Vsock device limitation
-1. Vsock must be inactive during snapshot:
-
- Vsock device can break if snapshotted while having active connections.
-Firecracker snapshots do not capture any inflight network or vsock (through the
-linux unix domain socket backend) traffic that has left or not yet entered
-Firecracker.
+Vsock must be inactive during snapshot. Vsock device can break if snapshotted
+while having active connections. Firecracker snapshots do not capture any
+inflight network or vsock (through the linux unix domain socket backend)
+traffic that has left or not yet entered Firecracker.
The above, coupled with the fact that Vsock control protocol is not resilient
to vsock packet loss, leads to Vsock device breakage when doing a snapshot while
@@ -546,7 +544,3 @@ section 5.10.6.6 Device Events.
Firecracker handles sending the `reset` event to the vsock driver,
thus the customers are no longer responsible for closing
active connections.
-
-1. _Incremental/diff_ snapshots are not yet supported for Vsock devices.
- Creating a `diff` snapshot on a microVM with a `vsock` device configured
- is not allowed.
\ No newline at end of file
