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: Tue, 21 Jul 2020 07:24:45 +0000 [thread overview]
Message-ID: <bug-207489-28872-8jxLISC1ka@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-207489-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=207489
Yani Stoyanov (yaweb@mail.bg) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |yaweb@mail.bg
--- Comment #16 from Yani Stoyanov (yaweb@mail.bg) ---
Kernel 5.8+
on Fedora 32
I have the same issue with macos (sierra and catalina) virtual machines with
passed through gpus.
What I do to identify the problem:
Try adding different cards to the mac vm's no matter amd/nvidia the vm hangs
and if you try to restart/force restart it the whole libvirt process hangs.
I get the same kernel overflow as mentioned in the bug.
How I am sure its the same problem:
I checked out the kernel source comment the problematic:
if (edge && kvm_apicv_activated(ioapic->kvm))
ioapic_lazy_update_eoi(ioapic, irq);
Rebuild the kernel and try with my version and it was working fine. I also try
kernel 5.5.19 where it was fine also since it didn't have the check.
I assume macos have some special way of treating the interrupts but since I am
new to the linux kernel and linux as hole I can not identify what exactly case
the problem.
--
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-07-21 7:24 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
2020-05-12 15:20 ` bugzilla-daemon
2020-07-21 7:24 ` bugzilla-daemon [this message]
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-8jxLISC1ka@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.