qemu-devel.nongnu.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Hajnoczi <stefanha@gmail.com>
To: "Lilijun (Jerry, Cloud Networking)" <jerry.lilijun@huawei.com>
Cc: "qemu-devel@nongnu.org" <qemu-devel@nongnu.org>,
	"wangxin (U)" <wangxinxin.wang@huawei.com>,
	wangyunjian <wangyunjian@huawei.com>
Subject: Re: [Qemu-devel] Question about VM inner route entry's lost when vhost-user reconnect
Date: Wed, 6 Mar 2019 10:06:46 +0000	[thread overview]
Message-ID: <20190306100646.GI22159@stefanha-x1.localdomain> (raw)
In-Reply-To: <40280F65B1B0B44E8089ED31C01616EBA3947B1A@dggeml529-mbx.china.huawei.com>

[-- Attachment #1: Type: text/plain, Size: 1010 bytes --]

On Mon, Mar 04, 2019 at 08:26:23AM +0000, 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. 
>      2) When restarting openvswitch service for the crash of the ovs-vswitchd, qemu's vhost-user reconnected successfully after 40s.  
>      3) Here VM's vNIC will receive link down and up events, the interval between the two events is about 40s.
>      3) But that route entry disappeared and that will cause user's network traffic interruption and the service failed.
> 
>      Is there some work on this problem?  Can we keep the vNIC's link up status when do vhost-user's reconnecting work?

Can you add the custom route to the network management tool inside the
guest so that it will be reinstated when the link comes back up?

The details of how to do this depend on the guest's distro.

Stefan

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]

  reply	other threads:[~2019-03-06 10:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-04  8:26 [Qemu-devel] Question about VM inner route entry's lost when vhost-user reconnect Lilijun (Jerry, Cloud Networking)
2019-03-06 10:06 ` Stefan Hajnoczi [this message]
2019-03-08  2:31   ` Lilijun (Jerry, Cloud Networking)
2019-03-11  9:46     ` Stefan Hajnoczi
2019-03-12  2:01       ` Lilijun (Jerry, Cloud Networking)

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20190306100646.GI22159@stefanha-x1.localdomain \
    --to=stefanha@gmail.com \
    --cc=jerry.lilijun@huawei.com \
    --cc=qemu-devel@nongnu.org \
    --cc=wangxinxin.wang@huawei.com \
    --cc=wangyunjian@huawei.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).