migrated VM’s vCPU doesn’t update

To get higher clock speeds for a VM (Windows Server 2019), I migrated it with vMotion from one ESXi host to another. The problem is the VM’s vCPU (on the target, faster CPU host) still shows up with the source host’s CPU. The source was 1.8 GHz and the target is 3.5 GHz. How do I fix this?

View Reddit by seenlivingView Source

Related Articles


  1. I think Windows detects the max clock speed upon bootup, but I don’t think it really matters.

    VMware will give the VM clock cycles if it has them. Windows isn’t directly controlling the CPU in a virtualized world.

    On a physical server Windows would adjust clock speed based on load, but in a virtual world that doesn’t happen at all.

    I think you should see better performance from the faster processor regardless of what windows shows you.

Leave a Reply