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: Mon, 16 Nov 2020 11:21:32 +0000 [thread overview]
Message-ID: <bug-209253-28872-uchzhHZVjc@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-209253-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=209253
Mair O'Nire (maironire@gmail.com) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |maironire@gmail.com
--- Comment #23 from Mair O'Nire (maironire@gmail.com) ---
Hi all.
I'm new here, registered exactly to track this bug.
I've got a new laptop recently, HP Omen 2020, with AMD Ryzen 4800H and Nvidia
1660Ti, and whilst was trying to setup kvm virtualized system I ran into the
same issue. During investigation I've found Ian's report, and then this one,
too.
Backtraces were very similar to other posted above, all at fs/eventfd.c:74, but
sometimes with different origin. So I decided to give Alex's patch a try, and
built mainline kernel with this patch applied. Mine host kernel was
5.8.[6,17,18], Fedora 33, and they all seems to be affected. Guest is Windows
10.
So, I do confirm - patch works, system became stable, and there was no crashes
for about a week, nor under regular work load, neither while running
benchmarks. Before the fix guest uptime varied from 2 to 10 minutes and then
crash. Moreover, I had to reboot host to get Nvidia back to work in vm again.
Thanks Alex, Ian, and others, you guys doin' a great work if you don't know
this already :)
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-11-16 12:37 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
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 [this message]
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-uchzhHZVjc@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.