Displaying 4 results from an estimated 4 matches for "host_old_cid".
2016 Mar 03
4
virtio-vsock live migration
...getsockopt() to extract socket state information from the host
kernel.
A new instance of the application is started on the destination host and
given the state so it can restore the connection. The setsockopt()
syscall is used to restore socket state information.
The guest is given a list of <host_old_cid, host_new_cid, host_port,
guest_port> tuples for established connections that must not be reset
when the guest CID update notification is received. These connections
will carry on as if nothing changed.
Note that the connection's remote address is updated from host_old_cid
to host_new_cid....
2016 Mar 03
4
virtio-vsock live migration
...getsockopt() to extract socket state information from the host
kernel.
A new instance of the application is started on the destination host and
given the state so it can restore the connection. The setsockopt()
syscall is used to restore socket state information.
The guest is given a list of <host_old_cid, host_new_cid, host_port,
guest_port> tuples for established connections that must not be reset
when the guest CID update notification is received. These connections
will carry on as if nothing changed.
Note that the connection's remote address is updated from host_old_cid
to host_new_cid....
2016 Mar 10
0
virtio-vsock live migration
...e information from the host
> kernel.
>
> A new instance of the application is started on the destination host and
> given the state so it can restore the connection. The setsockopt()
> syscall is used to restore socket state information.
>
> The guest is given a list of <host_old_cid, host_new_cid, host_port,
> guest_port> tuples for established connections that must not be reset
> when the guest CID update notification is received. These connections
> will carry on as if nothing changed.
>
> Note that the connection's remote address is updated from host...
2016 Mar 14
0
[virtio-dev] virtio-vsock live migration
...e information from the host
> kernel.
>
> A new instance of the application is started on the destination host and
> given the state so it can restore the connection. The setsockopt()
> syscall is used to restore socket state information.
>
> The guest is given a list of <host_old_cid, host_new_cid, host_port,
> guest_port> tuples for established connections that must not be reset
> when the guest CID update notification is received. These connections
> will carry on as if nothing changed.
>
> Note that the connection's remote address is updated from host...