From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216349] Kernel panics in VMs running on an Intel N5105 on Proxmox
Date: Thu, 27 Oct 2022 23:55:43 +0000 [thread overview]
Message-ID: <bug-216349-28872-LeI8HW096D@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216349-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216349
Patrick Li (patrick@papaq.org) changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |patrick@papaq.org
--- Comment #14 from Patrick Li (patrick@papaq.org) ---
There are a lot of people reporting this issue on the Proxmox forum and I am
one of them.
Tried 5.19.16 kernel a few days ago, it behaved a lot better than 5.15. Guest
kernel panic after 3.5 days instead of a few hours, but still happens.
There are reports of 5.13 being unaffected, ie, problem started from 5.15. But
I can't personally confirm this.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are watching the assignee of the bug.
prev parent reply other threads:[~2022-10-27 23:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-10 12:13 [Bug 216349] New: Kernel panic in a Ubuntu VM running on Proxmox bugzilla-daemon
2022-08-10 13:44 ` [Bug 216349] " bugzilla-daemon
2022-08-10 14:29 ` bugzilla-daemon
2022-08-10 15:43 ` bugzilla-daemon
2022-08-11 5:50 ` bugzilla-daemon
2022-08-11 5:52 ` bugzilla-daemon
2022-08-11 8:18 ` bugzilla-daemon
2022-08-11 8:29 ` bugzilla-daemon
2022-08-13 2:55 ` bugzilla-daemon
2022-08-13 2:59 ` bugzilla-daemon
2022-08-13 13:30 ` bugzilla-daemon
2022-08-17 14:35 ` bugzilla-daemon
2022-08-17 15:37 ` bugzilla-daemon
2022-08-22 5:01 ` [Bug 216349] Kernel panics in VMs running on an Intel N5105 " bugzilla-daemon
2022-08-24 12:33 ` bugzilla-daemon
2022-10-27 23:55 ` 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-216349-28872-LeI8HW096D@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 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.