From: bugzilla-daemon@bugzilla.kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 205247] Kernel panic in network code when booting Windows 10 kvm guest
Date: Thu, 14 Nov 2019 16:26:31 +0000 [thread overview]
Message-ID: <bug-205247-28872-v1Yd3tDqIO@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-205247-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=205247
Michael Weiser (michael@weiser.dinsnail.net) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |michael@weiser.dinsnail.net
--- Comment #2 from Michael Weiser (michael@weiser.dinsnail.net) ---
I can confirm exactly the same error down to the backtrace and (dis-)assembly
sequence. System is Gentoo Linux with 5.3.x kernels up to .9, qemu-4.0.0 and
Windows 10 1903 and 1909 in the guest. Problem also only occurs with e1000e as
virtual NIC and disappears when switching to virtio.
--
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2019-11-14 16:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-18 16:13 [Bug 205247] New: Kernel panic in network code when booting Windows 10 kvm guest bugzilla-daemon
2019-11-14 16:26 ` bugzilla-daemon [this message]
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-205247-28872-v1Yd3tDqIO@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