From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 207489] Kernel panic due to Lazy update IOAPIC EOI on an x86_64 *host*, when two (or more) PCI devices from different IOMMU groups are passed to Windows 10 guest, upon guest boot into Windows, with more than 4 VCPUs
Date: Wed, 06 May 2020 14:14:10 +0000 [thread overview]
Message-ID: <bug-207489-28872-LwGE9Uk2y2@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207489-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207489
--- Comment #14 from Pol Van Aubel (linux-kernel@polvanaubel.com) ---
Ah, I hadn't noticed that commit yet. I'll check if it fixes my instance of the
issue as well (but judging by Paolo's analysis I think it will). If so, what's
the proper procedure here, wait until that makes it into a release or just mark
this as RESOLVED now?
--
You are receiving this mail because:
You are on the CC list for the bug.
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-05-06 14:14 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-04-28 20:55 [Bug 207489] New: Kernel panic due to Lazy update IOAPIC EOI on an x86_64 *host*, when two (or more) PCI devices from different IOMMU groups are passed to Windows 10 guest, upon guest boot into Windows, with more than 4 VCPUs bugzilla-daemon
2020-04-28 21:00 ` [Bug 207489] " bugzilla-daemon
2020-04-28 21:01 ` bugzilla-daemon
2020-04-28 21:02 ` bugzilla-daemon
2020-04-28 21:02 ` bugzilla-daemon
2020-04-28 21:02 ` bugzilla-daemon
2020-04-28 21:03 ` bugzilla-daemon
2020-04-30 17:18 ` bugzilla-daemon
2020-04-30 18:10 ` bugzilla-daemon
2020-05-01 18:23 ` bugzilla-daemon
2020-05-02 9:22 ` bugzilla-daemon
2020-05-03 7:27 ` bugzilla-daemon
2020-05-04 10:10 ` bugzilla-daemon
2020-05-06 13:44 ` bugzilla-daemon
2020-05-06 14:02 ` bugzilla-daemon
2020-05-06 14:14 ` bugzilla-daemon [this message]
2020-05-12 15:20 ` bugzilla-daemon
2020-07-21 7:24 ` bugzilla-daemon
2020-08-22 14:33 ` bugzilla-daemon
2020-08-22 14:34 ` bugzilla-daemon
2021-02-03 16:16 ` 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-207489-28872-LwGE9Uk2y2@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).