Date: Wed, 12 Jan 2022 20:32:23 +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-PokQpzhjhX@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 --- Comment #35 from Dennis Noordsij <dennis.noordsij@alumni.helsinki.fi> -= -- (In reply to Jamie Landeg-Jones from comment #34) Ah OK. For root servers Hetzner provides an additional special "AX" (AMD li= ne) flavored FreeBSD 13 rescue image - though I am not actually sure what the difference is.=20 For the VPS's there is only one FreeBSD rescue image, which includes only a= few necessary modules but not virtio and which works without issue. They do not actually have a FreeBSD installation option for the VPS's - you= can only install FreeBSD via the rescue image (either manually or running bsdinstall[image]) - but mostly what I want to say is that they don't know = what OS you're actually running and there therefore shouldn't be any special KVM settings and it should be the same thing a Linux OS sees. At most the provi= ded bsdinstall blacklists virtio. As far as I have been able to tell, this is the only issue with this (virtu= al) hardware, it even performs surprisingly well. (For reference, this is a CPX11 in Nuremburg) --=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-PokQpzhjhX>