Reducing vCPU isn't done live on Windows
-
I'm doing a couple of tests to trying to figure out quirks and behaviours from XCP-ng side, for a future production (licensed) setup.
So I tried to see what would happen if I would play with the number of vCPUs on two guests.
TL;DR: Reducing vCPUs on Windows requires reboot.On Windows Guest:
OS: Windows Server 25
Guest Agent: 9.2.385.0
Increasing the number of vCPUs up to the max value, is done live and works well. But reducing the vCPUs requires a reboot.However. On a Rocky Linux 10 installation. The reducing works immediately live and online as expected.
This might very well be a limitation of how Windows does things internally. But I thought it interesting enouch to report about anyway.
Hello! It looks like you're interested in this conversation, but you don't have an account yet.
Getting fed up of having to scroll through the same posts each visit? When you register for an account, you'll always come back to exactly where you were before, and choose to be notified of new replies (either via email, or push notification). You'll also be able to save bookmarks and upvote posts to show your appreciation to other community members.
With your input, this post could be even better 💗
Register Login