bhyve Idle Windows 11 bhyve guests high CPU usage

I am in the process of moving off of Proxmox and into FreeBSD 14.1 / bhyve for my home vm server. (Using vm-bhyve)
I have noticed that Windows 11 guests seem to use considerably more cpu resources at idle than my Linux, Windows 10, and Windows Server 2022 VMs.

I have 1 migrated W11 VM, and 1 Fresh Install. Acording to btop they average 50 to 100% cpu resources. From within the Guest Task manager shows only 5% CPU usage or so...

The VM server is a 11th Gen Intel I5 11700K (12 core System)

The Linux Server, Win 10, and Win Server 2022 are fresh Installs as well, and average 2 to 5% cpu at idle.

Has anyone else seen this before. I have tried googling, and searching the forum, but could not find any related content...

Here are the config files for the 2 win 11, and the win 10 guests.

Migrated Win 11 guest
Code:
root@bhyve-prod:/vm-tank/vm # cat W11-Work/W11-Work.conf

loader="uefi"
graphics="yes"
xhci_mouse="yes"

cpu=6
cpu_sockets=1
cpu_cores=6
cpu_threads=1

memory=16G

graphics_res="1600x900"

ahci_device_limit="8"

network0_type="virtio-net"
network0_switch="public"

disk0_type="nvme"
disk0_name="disk0.raw"

utctime="no"
uuid="eb21588f-49c3-11ef-ad46-b04f130cce6d"
network0_mac="06:39:2D:11:D9:AD"

Fresh Win 11 Guest
Code:
root@bhyve-prod:/vm-tank/vm # cat levon-work/levon-work.conf 

loader="uefi"
graphics="yes"
xhci_mouse="yes"


cpu=4
cpu_sockets=1
cpu_cores=4
cpu_threads=1

memory=8G

ahci_device_limit="8"

network0_type="virtio-net"
network0_switch="public"

disk0_type="nvme"
disk0_name="disk0.img"

disk1_type="ahci-cd"
disk1_dev="custom"
disk1_name="/vm-tank/vm/.iso/virtio-win-0.1.248.iso"


utctime="no"

uuid="9f9c78b4-4e2f-11ef-87a9-b04f130cce6d"
network0_mac="58:9c:fc:0c:c2:fc"

Fresh Win 10 Guest
Code:
root@bhyve-prod:/vm-tank/vm # cat win10/win10.conf
 
loader="uefi"
graphics="yes"
xhci_mouse="yes"

graphics_wait="yes"

cpu=6
cpu_sockets=1
cpu_cores=6
cpu_threads=1

memory=8G

ahci_device_limit="8"

#network0_type="e1000"
network0_type="virtio-net"
network0_switch="public"

disk0_type="ahci-hd"
disk0_name="disk0.img"

disk10_type="nvme"
disk10_name="disk1.img"

utctime="no"
uuid="56ddce24-4e28-11ef-87a9-b04f130cce6d"
network0_mac="58:9c:fc:0f:3f:e9"

Thanks!
 

Attachments

  • bhyve-Win11.png
    bhyve-Win11.png
    504 KB · Views: 88
On a separate test system at my office (FBSD 14.1, and BVCP latest) The win11 VM is still using on average 18 to 20 % cpu...
Better than the other system, but still much higher than the Win10, WinSvr 2022, or Linux Machines...

1722555406002.png

1722555419517.png
 
我也有同样的问题,win10/server2022都正常,win11/server2025就非常卡顿,CPU占用高,同样找不到答案,你是我找到唯一说到这个问题的。
而且我使用的是FreeBSD13.3(truenas13.3),我开始还期望着升级到14.1会正常,但看到你14.1依然这个问题,绝望。
无法解决我可能会考虑pve+lxc。


I have the same problem. Win10/server2022 are normal, but Win11/server2025 is very slow and the CPU usage is high. I can't find the answer either. You are the only one I found who talked about this problem.
And I am using FreeBSD13.3 (truenas13.3). I initially expected that upgrading to 14.1 would work, but seeing that you still have this problem with 14.1, I feel desperate.
If I can't solve it, I might consider pve+lxc.
 
I'm noticing some pretty interesting behavior with Windows 11 VM's in Bhyve myself. I'm not really seeing crazy CPU usage, but it is running VERY sluggishly. Originally, I had 4 vCPU's and 8GB RAM (like I do with most other WIndows VM's) and it was so slow it was unusable. So, I threw 8 vCPU's and 16GB RAM at it and it did improve the responsiveness, but it is still very slow. I also changed to "GOOD" quality settings instead of "BEST" which disabled some things like the BG image to improve speed a little. And also disabled all the visual effects I could find in Windows 11. This also helped but not enough to have a usable VM (connecting via RDP with Remmina.)

On a side note, all previous versions of Windows run very well for me in Bhyve. So, I'm guessing this is something that needs to be addressed upstream as the VM configuration, host resources and network don't appear to be the problem.
 
Back
Top