From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 215977] New: kvm BUG: kernel NULL pointer dereference, address: 000000000000000b
Date: Sat, 14 May 2022 18:18:22 +0000 [thread overview]
Message-ID: <bug-215977-28872@https.bugzilla.kernel.org/> (raw)
https://bugzilla.kernel.org/show_bug.cgi?id=215977
Bug ID: 215977
Summary: kvm BUG: kernel NULL pointer dereference, address:
000000000000000b
Product: Virtualization
Version: unspecified
Kernel Version: 5.17.7
Hardware: Intel
OS: Linux
Tree: Mainline
Status: NEW
Severity: normal
Priority: P1
Component: kvm
Assignee: virtualization_kvm@kernel-bugs.osdl.org
Reporter: dabo+kernel.org@devconsole.de
Regression: No
Created attachment 300957
--> https://bugzilla.kernel.org/attachment.cgi?id=300957&action=edit
journalctl -o cat -k -b -1
Hi,
I encountered a bug in Arch Linux after kernel upgrade from 5.17.1-arch1-1 to
5.17.7-arch1-1, when libvirtd starts a kvm accelerated qemu vm. Downgrading to
5.17.1 fixes it.
Please find journal in attachment.
Thank you.
Daniel
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
next reply other threads:[~2022-05-14 18:18 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-14 18:18 bugzilla-daemon [this message]
2022-05-16 15:33 ` [Bug 215977] kvm BUG: kernel NULL pointer dereference, address: 000000000000000b 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-215977-28872@https.bugzilla.kernel.org/ \
--to=bugzilla-daemon@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