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: Mon, 11 Mar 2019 09:46:39 +0000 [thread overview]
Message-ID: <20190311094639.GA5991@stefanha-x1.localdomain> (raw)
In-Reply-To: <40280F65B1B0B44E8089ED31C01616EBA394CD10@dggeml529-mbx.china.huawei.com>
[-- Attachment #1: Type: text/plain, Size: 595 bytes --]
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?
Stefan
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 455 bytes --]
next prev parent reply other threads:[~2019-03-11 9:46 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
2019-03-08 2:31 ` Lilijun (Jerry, Cloud Networking)
2019-03-11 9:46 ` Stefan Hajnoczi [this message]
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=20190311094639.GA5991@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).