From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 209253] Loss of connectivity on guest after important host <-> guest traffic
Date: Fri, 23 Oct 2020 08:40:51 +0000 [thread overview]
Message-ID: <bug-209253-28872-Qehx8qD6rd@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209253-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209253
--- Comment #6 from Justin Gatzen (justin.gatzen@gmail.com) ---
Thanks, I will revert that commit and report back. This commit was backported
to kernel 5.8.4, which would jive with my (unproven) suspicion that 5.8.2 was
unaffected.
Also, to clarify, the second stack trace on my previous post (Comment #4) could
have infact been a VFIO VM. There were several VMs running with vhost/virtio
net communicating with each other and it was not clear which VM triggered it.
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-10-23 8:40 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-13 18:39 [Bug 209253] New: Loss of connectivity on guest after important host <-> guest traffic bugzilla-daemon
2020-10-12 0:07 ` [Bug 209253] " bugzilla-daemon
2020-10-17 15:59 ` bugzilla-daemon
2020-10-20 14:28 ` bugzilla-daemon
2020-10-22 16:14 ` bugzilla-daemon
2020-10-22 22:26 ` bugzilla-daemon
2020-10-23 8:40 ` bugzilla-daemon [this message]
2020-10-23 18:23 ` bugzilla-daemon
2020-10-23 19:05 ` bugzilla-daemon
2020-10-23 22:28 ` bugzilla-daemon
2020-10-27 12:51 ` bugzilla-daemon
2020-10-28 17:12 ` bugzilla-daemon
2020-10-28 20:35 ` bugzilla-daemon
2020-10-28 20:37 ` bugzilla-daemon
2020-10-28 20:52 ` bugzilla-daemon
2020-10-28 23:41 ` bugzilla-daemon
2020-10-30 22:13 ` bugzilla-daemon
2020-10-30 22:53 ` bugzilla-daemon
2020-11-10 18:35 ` bugzilla-daemon
2020-11-10 18:52 ` bugzilla-daemon
2020-11-10 22:43 ` bugzilla-daemon
2020-11-16 11:21 ` bugzilla-daemon
2020-12-04 22:49 ` bugzilla-daemon
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=bug-209253-28872-Qehx8qD6rd@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@bugzilla.kernel.org \
--cc=kvm@vger.kernel.org \
/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).