On Tue, Mar 19, 2019 at 09:51:17AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> After more detail test, I found two results:
> 1) This route entry's lost can be reproduced on both virtio-net and
> pass-through physical devices.
> 2) The link down event is handled by a service named NetworkM
mail.com]
> Sent: Wednesday, March 13, 2019 10:55 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: qemu-devel@nongnu.org; wangxin (U)
> ; wangyunjian
>
> Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when
> vhost-user reconnect
>
> On Tue, Mar 12,
; Cc: qemu-devel@nongnu.org; wangxin (U)
> > ; wangyunjian
> >
> > 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 +, 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)
> Cc: qemu-devel@nongnu.org; wangxin (U)
> ; wangyunjian
>
> Subject: Re: [Qemu-devel] Question about VM
On Fri, Mar 08, 2019 at 02:31:12AM +, 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
to:stefa...@gmail.com]
> Sent: Wednesday, March 06, 2019 6:07 PM
> To: Lilijun (Jerry, Cloud Networking)
> Cc: qemu-devel@nongnu.org; wangxin (U)
> ; wangyunjian
>
> Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when
> vhost-user reconnect
>
&
On Mon, Mar 04, 2019 at 08:26:23AM +, Lilijun (Jerry, Cloud Networking)
wrote:
> I am running my VM using vhost-user NIC with OVS-DPDK. The steps of my
> question is shown as follows:
> 1) In the VM, I add one route entry manually on the vNIC eth0 using the
> linux tool route.
>
Hi all,
I am running my VM using vhost-user NIC with OVS-DPDK. The steps of my
question is shown as follows:
1) In the VM, I add one route entry manually on the vNIC eth0 using the
linux tool route.
2) When restarting openvswitch service for the crash of the ovs-vswitchd,
qem
