Re: [Qemu-devel] Question about VM inner route entry's lost when vhost-user reconnect

[Lilijun (Jerry, Cloud Networking)]

> -----Original Message-----
> From: Stefan Hajnoczi [mailto:stefa...@gmail.com]
> Sent: Monday, March 11, 2019 5:47 PM
> To: Lilijun (Jerry, Cloud Networking) <jerry.lili...@huawei.com>
> Cc: qemu-devel@nongnu.org; wangxin (U)
> <wangxinxin.w...@huawei.com>; wangyunjian
> <wangyunj...@huawei.com>
> Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when
> vhost-user reconnect
> 
> On Fri, Mar 08, 2019 at 02:31:12AM +0000, Lilijun (Jerry, Cloud Networking)
> wrote:
> > This problem is related with backend vhost-user socket abnormal cases, we
> shouldn't ask customers to configure it manually for backend's issues or
> depends on guest OS's network configuration.
> 
> In Step 1 you said:
> 
> > > >      1) In the VM, I add one route entry manually on the vNIC eth0
> > > > using the
> > > linux tool route.
> 
> You configured the route manually inside the guest.  Seems like a guest
> problem to me.
> 
> If this was a physical machine that lost connectivity due to a link event, 
> what
> would happen?

Yes, the configuration can be recovered manually by customers.

But in the virtualization machines, this configuration's lost is a result of 
backend process's software unexpected bugs or version update. So I think we 
need hide this change to customers.
> 
> Stefan