Hi all,
Recently I installed a fresh copy of FreeBSD 13 as a KVM guest on my Linux server and was wondering why one of the CPU cores is always pegged at 100%.
When issuing the top -SP command, I see that the rand_harvestq process is consuming 100% of CPU3 on my VM and I'm unsure why, it feels like this could be a bug but not sure.
Here's a screenshot of what I'm seeing:
I did some digging and this blogger seems to be experiencing the same problem that I'm facing, the blogger notes that high CPU usage from rand_harvestq happens when the VirtIO RNG is being used. The poster said that this issue was resolved when the "Intel Secure Key RNG" is being used instead. Unfortunately, I don't believe my home server hardware has the Intel Secure Key RNG available.
Was wondering if anyone else has run into this issue as well and may have a potential workaround or a bug report is required.
Any suggestions would be much appreciated.
Thank you.
Recently I installed a fresh copy of FreeBSD 13 as a KVM guest on my Linux server and was wondering why one of the CPU cores is always pegged at 100%.
When issuing the top -SP command, I see that the rand_harvestq process is consuming 100% of CPU3 on my VM and I'm unsure why, it feels like this could be a bug but not sure.
Here's a screenshot of what I'm seeing:
I did some digging and this blogger seems to be experiencing the same problem that I'm facing, the blogger notes that high CPU usage from rand_harvestq happens when the VirtIO RNG is being used. The poster said that this issue was resolved when the "Intel Secure Key RNG" is being used instead. Unfortunately, I don't believe my home server hardware has the Intel Secure Key RNG available.
VirtIO RNG may cause high CPU utilization by rand_harvestq in FreeBSD 13 VM
VirtIO RNG may cause high CPU utilization by rand_harvestq in FreeBSD 13 VM I found my home server suddenly got increased power consumption. Its difference was up to 30W, so it's not obviously error. It was caused by powering up FreeBSD VM on ProxmoxVE, but I had no reasonable reasons. When I...
decomo.info
Was wondering if anyone else has run into this issue as well and may have a potential workaround or a bug report is required.
Any suggestions would be much appreciated.
Thank you.