All of lore.kernel.org
 help / color / mirror / Atom feed
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: Sun, 02 Aug 2020 10:36:19 +0000	[thread overview]
Message-ID: <bug-208767-28872-hGDRkevsBv@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 #2 from Yani Stoyanov (yaweb@mail.bg) ---
I was thinking the same thing when I saw:
https://bugzilla.kernel.org/show_bug.cgi?id=207489 

I write a comment there but start realizing that the reason for my issue may be
something different since it happens only with my macos vm-s. Currently I am
using kernel-5.7.10-201.fc32.x86_64 which should include the patch. 

And I mentioned bug people are complaining about windows guests. I have 2
windows 10 machines and they are working fine no issues there the problem
appear only on my macos vm.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.

  parent reply	other threads:[~2020-08-02 10:36 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 [this message]
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
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-hGDRkevsBv@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.