Date: Wed, 12 Jan 2022 07:42:32 +0000 From: bugzilla-noreply@freebsd.org To: virtualization@FreeBSD.org Subject: [Bug 254513] virtio_random: random_harvestq spinning on a CPU with Q35 virtio random device Message-ID: <bug-254513-27103-l4R12QPHFp@https.bugs.freebsd.org/bugzilla/> In-Reply-To: <bug-254513-27103@https.bugs.freebsd.org/bugzilla/> References: <bug-254513-27103@https.bugs.freebsd.org/bugzilla/>
next in thread | previous in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D254513 Dennis Noordsij <dennis.noordsij@alumni.helsinki.fi> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dennis.noordsij@alumni.hels | |inki.fi --- Comment #32 from Dennis Noordsij <dennis.noordsij@alumni.helsinki.fi> -= -- (Coming here via #261127 - "ifconfig wg0 destroy" also triggering this prob= lem) Can confirm this is (still) happening on Hetzner (CPX) VPS's with 13.0-RELEASE-p6 Blacklisting virtio_random fixes (works around) the issue. Regarding ready installation images; I usually boot the rescue mode and ins= tall manually by creating partitions and untarring the base system, so perhaps Hetzner/Vultr provide installation media where virtio_random is already pre-blacklisted). Have a system available for any testing/debugging, or even just try to dete= ct if the issue would occur and not load the driver, if someone wants to point= me in the right direction. --=20 You are receiving this mail because: You are the assignee for the bug. You are on the CC list for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-254513-27103-l4R12QPHFp>