> From: Stefan Hajnoczi
> Sent: Tuesday, December 11, 2018 8:27 AM
> To: Jorgen Hansen ; Dexuan Cui
>
> Cc: netdev@vger.kernel.org; Lepton Wu
> Subject: Re: [PATCH] VSOCK: bind to random port for VMADDR_PORT_ANY
>
> On Mon, Dec 10, 2018 at 11:02:35PM -0800, Lepton Wu
> On Mon, Dec 10, 2018 at 11:02:35PM -0800, Lepton Wu wrote:
> > 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 th
On Mon, Dec 10, 2018 at 11:02:35PM -0800, Lepton Wu wrote:
> 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 tryin