<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[Reducing vCPU isn't done live on Windows]]></title><description><![CDATA[<p dir="auto">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.</p>
<p dir="auto">So I tried to see what would happen if I would play with the number of vCPUs on two guests.<br />
TL;DR: Reducing vCPUs on Windows requires reboot.</p>
<p dir="auto">On Windows Guest:<br />
OS: Windows Server 25<br />
Guest Agent: 9.2.385.0<br />
Increasing the number of vCPUs up to the max value, is done live and works well. <strong>But reducing the vCPUs requires a reboot</strong>.</p>
<p dir="auto">However. On a Rocky Linux 10 installation. The reducing works immediately live and online as expected.</p>
<p dir="auto">This might very well be a limitation of how Windows does things internally. But I thought it interesting enouch to report about anyway.</p>
]]></description><link>https://xcp-ng.org/forum/topic/12491/reducing-vcpu-isn-t-done-live-on-windows</link><generator>RSS for Node</generator><lastBuildDate>Fri, 25 Sep 2026 08:06:52 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/topic/12491.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 25 Sep 2026 06:24:52 GMT</pubDate><ttl>60</ttl></channel></rss>