From: bugzilla-daemon@kernel.org
To: kvm@vger.kernel.org
Subject: [Bug 216349] Kernel panic in a Ubuntu VM running on Proxmox
Date: Wed, 10 Aug 2022 15:43:22 +0000 [thread overview]
Message-ID: <bug-216349-28872-yrDvb3ppxQ@https.bugzilla.kernel.org/> (raw)
In-Reply-To: <bug-216349-28872@https.bugzilla.kernel.org/>
https://bugzilla.kernel.org/show_bug.cgi?id=216349
--- Comment #3 from John Park (jdpark.au@gmail.com) ---
(In reply to Dr. David Alan Gilbert from comment #2)
> Are you doing live migration? And if so, between which host CPUs?
Thanks for your response. No, I'm not performing any migration. The VM is
static and only running Docker. The host CPU is an Intel N5105. It's not doing
anything too intensive with VM CPU sitting at around 10% and the Host CPU
sitting at around 5% (powersave governor set).
The CPU governer was initially set to 'performance' which I've since changed to
'powersave' using the intel_pstate driver but this hasn't improved the
situation.
There's quite a few people on the Proxmox forums (links below) running the same
CPU who have also encountered the same issue. Could there be an issue with the
kernel and this particular CPU?
https://forum.proxmox.com/threads/vm-freezes-irregularly.111494/
https://forum.proxmox.com/threads/vms-freezing-randomly.113037/
https://forum.proxmox.com/threads/ubuntu-20-04-und-22-04-vms-bleiben-zuf%C3%A4llig-h%C3%A4ngen-bsd-vms-nicht.113358/
https://forum.proxmox.com/threads/ubuntu-20-04-04-machine-freezes.112507/
https://forum.proxmox.com/threads/proxmox-vms-crashing-freezing-on-intel-n5105-cpu.113177/
https://forum.proxmox.com/threads/pfsense-vm-keeps-freezing-crashing.112439/
--
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 prev parent reply other threads:[~2022-08-10 15:43 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 [this message]
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
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-yrDvb3ppxQ@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