From: Lepton Wu <ytht....@gmail.com> Date: Tue, 11 Dec 2018 11:12:55 -0800
> The old code always starts from fixed port for VMADDR_PORT_ANY. Sometimes > when VMM crashed, there is still orphaned vsock which is waiting for > close timer, then it could cause connection time out for new started VM > if they are trying to connect to same port with same guest cid since the > new packets could hit that orphaned vsock. We could also fix this by doing > more in vhost_vsock_reset_orphans, but any way, it should be better to start > from a random local port instead of a fixed one. > > Signed-off-by: Lepton Wu <ytht....@gmail.com> Applied, thanks.
