KVM Archive on lore.kernel.org
 help / color / Atom feed
From: Jim Mattson <jmattson@google.com>
To: bugzilla-daemon@bugzilla.kernel.org
Cc: kvm list <kvm@vger.kernel.org>
Subject: Re: [Bug 208767] New: kernel stack overflow due to Lazy update IOAPIC on an x86_64 *host*, when gpu is passthrough to macos guest vm
Date: Mon, 3 Aug 2020 13:39:09 -0700
Message-ID: <CALMp9eRNYG+wO4CEZwnK-f0s7NmvcWhqHhSKn-Pbaf7Uxxi9KQ@mail.gmail.com> (raw)
In-Reply-To: <bug-208767-28872@https.bugzilla.kernel.org/>

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?

  parent reply index

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-08-02  9:01 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 ` Jim Mattson [this message]
2020-08-03 20:39 ` bugzilla-daemon
2020-08-04  0:25 ` bugzilla-daemon
2020-08-06  9:02 ` bugzilla-daemon
2020-08-06  9:09 ` 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=CALMp9eRNYG+wO4CEZwnK-f0s7NmvcWhqHhSKn-Pbaf7Uxxi9KQ@mail.gmail.com \
    --to=jmattson@google.com \
    --cc=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

KVM Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/kvm/0 kvm/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 kvm kvm/ https://lore.kernel.org/kvm \
		kvm@vger.kernel.org
	public-inbox-index kvm

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.kvm


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git