You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If ``--socket`` is not provided, passt will print the path of the UNIX domain socket QEMU can connect to (``/tmp/passt_1.socket``, ``/tmp/passt_2.socket``,
103
+
...). Then you can connect your QEMU instance to passt:
Where ``$RAMSIZE`` is the memory size of your VM ``-m`` and ``-object memory-backend-memfd,size=`` must match.
124
+
125
+
Migration of passt:
126
+
^^^^^^^^^^^^^^^^^^^
127
+
128
+
When passt is connected to QEMU using the vhost-user interface it can
129
+
be migrated with QEMU and the network connections are not interrupted.
130
+
131
+
As passt runs with no privileges, it relies on passt-repair to save and
132
+
load the TCP connections state, using the TCP_REPAIR socket option.
133
+
The passt-repair helper needs to have the CAP_NET_ADMIN capability, or run as root. If passt-repair is not available, TCP connections will not be preserved.
134
+
135
+
Example of migration of a guest on the same host
136
+
________________________________________________
137
+
138
+
Before being able to run passt-repair, the CAP_NET_ADMIN capability must be set
|qemu_system| [...OPTIONS...] [...VHOST USER OPTIONS...] -incoming tcp:localhost:4444
172
+
173
+
Then in the source guest monitor the migration can be started::
174
+
175
+
(qemu) migrate tcp:localhost:4444
176
+
177
+
A separate passt-repair instance must be started for every migration. In the case of a failed migration, passt-repair also needs to be restarted before trying
0 commit comments