From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 208767] kernel stack overflow due to Lazy update IOAPIC on an x86_64 *host*, when gpu is passthrough to macos guest vm
Date: Tue, 04 Aug 2020 00:25:20 +0000 [thread overview]
Message-ID: <bug-208767-28872-Y6VSHtcuoi@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-208767-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=208767
--- Comment #5 from Yani Stoyanov (yaweb@mail.bg) ---
(In reply to Jim Mattson from comment #4)
> On Sun, Aug 2, 2020 at 2:01 AM <bugzilla-daemon@bugzilla.kernel.org> wrote:
> >
> > https://bugzilla.kernel.org/show_bug.cgi?id=208767
> >
> > Bug ID: 208767
> > Summary: kernel stack overflow due to Lazy update IOAPIC on an
> > x86_64 *host*, when gpu is passthrough to macos guest
> > vm
> > Product: Virtualization
> > Version: unspecified
> > Kernel Version: 5.6 up to and including 5.7
> > Hardware: All
> > OS: Linux
> > Tree: Mainline
> > Status: NEW
> > Severity: normal
> > Priority: P1
> > Component: kvm
> > Assignee: virtualization_kvm@kernel-bugs.osdl.org
> > Reporter: yaweb@mail.bg
> > Regression: No
> >
> > I have fedora 32 host with latest kernel on a double xeon v5 2630
> workstation
> > asus board and few vm with assigned gpus to them (linux windows and macos).
>
> I didn't think the Mac OS X license agreement permitted running it on
> non-Apple hardware. Has this changed?
Jim Mattson, I guess official it is not support by as I wrote in the
description of the issue the problem is in the mentioned function. I tested it
and if comment the lines
if (edge && kvm_apicv_activated(ioapic->kvm))
ioapic_lazy_update_eoi(ioapic, irq);
It boots fine, if the function invocation is not commented I kernel stack
overflow so the bug is for it it should not matter what case it right?
--
You are receiving this mail because:
You are watching the assignee of the bug.
next prev parent reply other threads:[~2020-08-04 0:25 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-02 9:01 [Bug 208767] New: kernel stack overflow due to Lazy update IOAPIC on an x86_64 *host*, when gpu is passthrough to macos guest vm bugzilla-daemon
2020-08-02 9:03 ` [Bug 208767] " bugzilla-daemon
2020-08-02 9:19 ` bugzilla-daemon
2020-08-02 10:36 ` bugzilla-daemon
2020-08-02 17:45 ` bugzilla-daemon
2020-08-03 9:43 ` bugzilla-daemon
2020-08-03 20:39 ` [Bug 208767] New: " Jim Mattson
2020-08-03 20:39 ` [Bug 208767] " bugzilla-daemon
2020-08-04 0:25 ` bugzilla-daemon [this message]
2020-08-06 9:02 ` bugzilla-daemon
2020-08-06 9:09 ` bugzilla-daemon
2020-10-07 22:45 ` bugzilla-daemon
2021-02-03 20:32 ` bugzilla-daemon
2022-04-29 3:14 ` 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-208767-28872-Y6VSHtcuoi@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).