<?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[XCP-ng]]></title><description><![CDATA[Everything related to the virtualization platform]]></description><link>https://xcp-ng.org/forum/category/19</link><generator>RSS for Node</generator><lastBuildDate>Tue, 14 Apr 2026 05:51:24 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/category/19.rss" rel="self" type="application/rss+xml"/><pubDate>Mon, 06 Apr 2026 07:54:18 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[CPU Usage of empty server]]></title><description><![CDATA[
@jerry1333 said:
There is nothing else on that host and this is only host in pool but it's using 30% of cpu all the time?

it's not using 30% of CPU, you see a graph of cumulated (switch is on) core consumption of your 32 cores.
never switch this on. it adds up like that : 32x1%=32%, wrongfully letting you think you are at 30%ish CPU usage.
]]></description><link>https://xcp-ng.org/forum/topic/12055/cpu-usage-of-empty-server</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12055/cpu-usage-of-empty-server</guid><dc:creator><![CDATA[Pilow]]></dc:creator><pubDate>Mon, 06 Apr 2026 07:54:18 GMT</pubDate></item><item><title><![CDATA[XCP-NG upgrade 8.2 to 8.3]]></title><description><![CDATA[To add a bit more detail on the upgrade path: strictly speaking, you do not need to apply outstanding 8.2 patches before upgrading. When you upgrade to 8.3, you are replacing the entire base system with the 8.3 release which already incorporates everything from the 8.2 patch stream. Any 8.2 patches you hadn't yet applied will simply be superseded.
That said, applying them first is still a reasonable approach if you want a clean upgrade history and a fully-patched 8.2 baseline before jumping to 8.3.
A few things worth checking before you start on a production pool:
Check VM compatibility. Run a quick review of your VMs for any that might have specific OS or toolstack dependencies tied to 8.2. Most guests upgrade cleanly but it is worth knowing your environment.
Use rolling pool upgrade if you have more than one host. XCP-ng supports rolling upgrades: you migrate VMs off each host, upgrade it, rejoin the pool, then proceed to the next. This maintains VM availability throughout the process. The XO interface handles this workflow if you have XOA.
Back up before the jump. Export critical VM configurations or snapshots beforehand. If you use Xen Orchestra for backups, trigger a manual full backup job before starting.
The upgrade itself via yum is straightforward: add the 8.3 repo, yum update, reboot. The toolstack and XAPI will handle pool registration after the host comes back up.
After upgrading all hosts, run the post-upgrade checks from the docs (pool metadata sync, storage rescans) and verify HA is healthy if you use it.
]]></description><link>https://xcp-ng.org/forum/topic/12039/xcp-ng-upgrade-8.2-to-8.3</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12039/xcp-ng-upgrade-8.2-to-8.3</guid><dc:creator><![CDATA[RianKellyIT]]></dc:creator><pubDate>Tue, 31 Mar 2026 18:26:52 GMT</pubDate></item><item><title><![CDATA[Cannot shutdown VM or migrate]]></title><description><![CDATA[Not sure the issue, but rebooted the host and everything is fine again. I definitely had rebooted the host twice though after applying the patches and physically unplugged and moved the host.
]]></description><link>https://xcp-ng.org/forum/topic/12035/cannot-shutdown-vm-or-migrate</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12035/cannot-shutdown-vm-or-migrate</guid><dc:creator><![CDATA[crash]]></dc:creator><pubDate>Sun, 29 Mar 2026 23:09:44 GMT</pubDate></item><item><title><![CDATA[Nested virtualization]]></title><description><![CDATA[@olivierlambert Can you provide insights? Is nested virtualization as in running Hyper-V inside a XCP-ng VM expected to work?
]]></description><link>https://xcp-ng.org/forum/topic/11975/nested-virtualization</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11975/nested-virtualization</guid><dc:creator><![CDATA[MajorP93]]></dc:creator><pubDate>Wed, 18 Mar 2026 13:26:42 GMT</pubDate></item><item><title><![CDATA[Hot-adding a resource]]></title><description><![CDATA[Thank you all for your answers—now it's clear.
]]></description><link>https://xcp-ng.org/forum/topic/11972/hot-adding-a-resource</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11972/hot-adding-a-resource</guid><dc:creator><![CDATA[User-cxs]]></dc:creator><pubDate>Tue, 17 Mar 2026 08:22:59 GMT</pubDate></item><item><title><![CDATA[xcp-ng patches install fail]]></title><description><![CDATA[https://xcp-ng.org/forum/topic/11951/just-fyi-current-update-seams-to-break-nut-dependancies
]]></description><link>https://xcp-ng.org/forum/topic/11971/xcp-ng-patches-install-fail</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11971/xcp-ng-patches-install-fail</guid><dc:creator><![CDATA[ph7]]></dc:creator><pubDate>Mon, 16 Mar 2026 05:02:52 GMT</pubDate></item><item><title><![CDATA[Just FYI: current update seams to break NUT dependancies]]></title><description><![CDATA[
@cobordism said:
yum update --disablerepo=* --enablerepo=xcp-ng-base,xcp-ng-updates

It's currently in testing and will move to updates if everything (not only nut) is ok:
yum install --disablerepo=* \
   --enablerepo=xcp-ng-base,xcp-ng-updates,xcp-ng-testing  nut

]]></description><link>https://xcp-ng.org/forum/topic/11951/just-fyi-current-update-seams-to-break-nut-dependancies</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11951/just-fyi-current-update-seams-to-break-nut-dependancies</guid><dc:creator><![CDATA[rzr]]></dc:creator><pubDate>Tue, 10 Mar 2026 21:08:36 GMT</pubDate></item><item><title><![CDATA[Issues with new vm after latest 8.3 updates (priror to release)]]></title><description><![CDATA[No worries, it happens! Glad you found the problem 
]]></description><link>https://xcp-ng.org/forum/topic/11935/issues-with-new-vm-after-latest-8.3-updates-priror-to-release</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11935/issues-with-new-vm-after-latest-8.3-updates-priror-to-release</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Thu, 05 Mar 2026 11:17:55 GMT</pubDate></item><item><title><![CDATA[USB-Passthrough does not survive reboot of VM]]></title><description><![CDATA[@DustinB doesn't it use the exact same mechanism?
I have to find out.
]]></description><link>https://xcp-ng.org/forum/topic/11930/usb-passthrough-does-not-survive-reboot-of-vm</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11930/usb-passthrough-does-not-survive-reboot-of-vm</guid><dc:creator><![CDATA[cg]]></dc:creator><pubDate>Wed, 04 Mar 2026 02:31:30 GMT</pubDate></item><item><title><![CDATA[Deploying firewall to XCP-NG with rescue]]></title><description><![CDATA[@bleader thanks for the tip. You see my knowledge in redhat based systems is almost non existant. Think I'm almost 99% debian and 1% ubuntu (and that not by choice)
So I will take care of redeploying the script as soon as I upgrade, should be easily noticeable since monitoring will loose access and yell at me.
]]></description><link>https://xcp-ng.org/forum/topic/11917/deploying-firewall-to-xcp-ng-with-rescue</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11917/deploying-firewall-to-xcp-ng-with-rescue</guid><dc:creator><![CDATA[ditzy-olive]]></dc:creator><pubDate>Fri, 27 Feb 2026 15:48:36 GMT</pubDate></item><item><title><![CDATA[Issues joining pool with less pif on the newest host]]></title><description><![CDATA[@semarie This pool is still on 8.2.1, we are trying to add this host in order upgrade with little to no downtime.
]]></description><link>https://xcp-ng.org/forum/topic/11898/issues-joining-pool-with-less-pif-on-the-newest-host</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11898/issues-joining-pool-with-less-pif-on-the-newest-host</guid><dc:creator><![CDATA[afmart_dei]]></dc:creator><pubDate>Mon, 23 Feb 2026 18:47:40 GMT</pubDate></item><item><title><![CDATA[Hosts fenced, new master, rebooted slaves not reconnecting to pool]]></title><link>https://xcp-ng.org/forum/topic/11889/hosts-fenced-new-master-rebooted-slaves-not-reconnecting-to-pool</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11889/hosts-fenced-new-master-rebooted-slaves-not-reconnecting-to-pool</guid><pubDate>Fri, 20 Feb 2026 16:52:47 GMT</pubDate></item><item><title><![CDATA[HP DL380 Gen 8 - XCP-ng 8.1.0 Failing to update microcode]]></title><link>https://xcp-ng.org/forum/topic/11879/hp-dl380-gen-8-xcp-ng-8.1.0-failing-to-update-microcode</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11879/hp-dl380-gen-8-xcp-ng-8.1.0-failing-to-update-microcode</guid><pubDate>Wed, 18 Feb 2026 19:09:57 GMT</pubDate></item><item><title><![CDATA[Every virtual machine I restart doesn&#x27;t boot.]]></title><description><![CDATA[@nikade said in Every virtual machine I restart doesn't boot.:

@DustinB yeah im guessing the VDI isn't attached to the VM for some reason, based on the screenshot.
Im also wondering if he ever rebooted the VM's after installing them with PXE 

Right, it's a likely answer... but even then I would've expected his PXE server to just restart the installation process all over again... assuming that the disk is attached to the VM etc and that PXE boot isn't disabled automatically like it is with an ISO after first boot.
haha
]]></description><link>https://xcp-ng.org/forum/topic/11857/every-virtual-machine-i-restart-doesn-t-boot.</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11857/every-virtual-machine-i-restart-doesn-t-boot.</guid><dc:creator><![CDATA[DustinB]]></dc:creator><pubDate>Wed, 11 Feb 2026 05:08:15 GMT</pubDate></item><item><title><![CDATA[VM state is halted but should be running]]></title><description><![CDATA[@olivierlambert New thread is here
]]></description><link>https://xcp-ng.org/forum/topic/11852/vm-state-is-halted-but-should-be-running</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11852/vm-state-is-halted-but-should-be-running</guid><dc:creator><![CDATA[Danp]]></dc:creator><pubDate>Mon, 09 Feb 2026 09:36:31 GMT</pubDate></item><item><title><![CDATA[VM time ahead by 5 hours]]></title><description><![CDATA[@dinhngtu
I think it just have been a bad migration or the Win 11 Template did other things to the windows 10 os.  Since new test vm did not show the time issues, and a fresh migration of the vim with correct template selected did not have the issues either.
I dont know but maybe there is a way to put detect the correct VM template or make note.  I didnt think using the win 11 template would have caused issues since using the "wrong" template on  vm creation does not have the same effect.
]]></description><link>https://xcp-ng.org/forum/topic/11821/vm-time-ahead-by-5-hours</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11821/vm-time-ahead-by-5-hours</guid><dc:creator><![CDATA[acebmxer]]></dc:creator><pubDate>Sun, 01 Feb 2026 13:35:32 GMT</pubDate></item><item><title><![CDATA[Windows 11 (Win11_25H2_English_x64.iso) Fails to Install]]></title><description><![CDATA[@busthead said in Windows 11 (Win11_25H2_English_x64.iso) Fails to Install:

It appears I missed the key press to start setup 

Dont you know your are not suppose to blink when doing working.  You might miss something 
Glad you figured it out.
]]></description><link>https://xcp-ng.org/forum/topic/11804/windows-11-win11_25h2_english_x64.iso-fails-to-install</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11804/windows-11-win11_25h2_english_x64.iso-fails-to-install</guid><dc:creator><![CDATA[acebmxer]]></dc:creator><pubDate>Wed, 28 Jan 2026 05:59:33 GMT</pubDate></item><item><title><![CDATA[Create new virtual machine?]]></title><description><![CDATA[@drwhite85
I suggest watching some youtube videos about xcp-ng.  I guest Lawrence Systems - https://www.youtube.com/watch?v=2wMmSm_ZeZ4  He has other videos that go into more depth
]]></description><link>https://xcp-ng.org/forum/topic/11798/create-new-virtual-machine</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11798/create-new-virtual-machine</guid><dc:creator><![CDATA[acebmxer]]></dc:creator><pubDate>Mon, 26 Jan 2026 03:03:30 GMT</pubDate></item><item><title><![CDATA[The Lowest Priority Bug Ever? (&#x2F;etc&#x2F;udev&#x2F;rules.d&#x2F;z10-xen-vcpu-hotplug.rules)]]></title><description><![CDATA[Worth asking @Team-OS-Platform-Release
]]></description><link>https://xcp-ng.org/forum/topic/11788/the-lowest-priority-bug-ever-etc-udev-rules.d-z10-xen-vcpu-hotplug.rules</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11788/the-lowest-priority-bug-ever-etc-udev-rules.d-z10-xen-vcpu-hotplug.rules</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Fri, 23 Jan 2026 19:21:38 GMT</pubDate></item><item><title><![CDATA[botched pool patching and now we can&#x27;t change pool master]]></title><description><![CDATA[Resolved. Patched the rest of the hosts. Restarted all the toolstacks for good measure. I can move the master role now, and deploy new VMs.
]]></description><link>https://xcp-ng.org/forum/topic/11754/botched-pool-patching-and-now-we-can-t-change-pool-master</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11754/botched-pool-patching-and-now-we-can-t-change-pool-master</guid><dc:creator><![CDATA[randyrue]]></dc:creator><pubDate>Fri, 09 Jan 2026 20:54:54 GMT</pubDate></item><item><title><![CDATA[Lost VMs disk after using new SR]]></title><description><![CDATA[Resolved by rebuild, and doing VM backup and metadata to trunas dataset....
Start Backup earlier. Be better then me
]]></description><link>https://xcp-ng.org/forum/topic/11733/lost-vms-disk-after-using-new-sr</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11733/lost-vms-disk-after-using-new-sr</guid><dc:creator><![CDATA[DaleDibbadel]]></dc:creator><pubDate>Tue, 30 Dec 2025 04:30:25 GMT</pubDate></item><item><title><![CDATA[Red Hat Linux 10.1 ISO Won&#x27;t Boot in UEFI Mode]]></title><description><![CDATA[Actually Alma Linux does have a variant for v2 CPUs so they can run 10.0. Just look for x86_64 v2 on the downloads page.
]]></description><link>https://xcp-ng.org/forum/topic/11732/red-hat-linux-10.1-iso-won-t-boot-in-uefi-mode</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11732/red-hat-linux-10.1-iso-won-t-boot-in-uefi-mode</guid><dc:creator><![CDATA[john.c]]></dc:creator><pubDate>Tue, 30 Dec 2025 03:21:47 GMT</pubDate></item><item><title><![CDATA[Xapi#getResource &#x2F;rrd_updates (on xcp-dl380-gen10) 0%]]></title><description><![CDATA[
]]></description><link>https://xcp-ng.org/forum/topic/11662/xapi-getresource-rrd_updates-on-xcp-dl380-gen10-0</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11662/xapi-getresource-rrd_updates-on-xcp-dl380-gen10-0</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Tue, 09 Dec 2025 14:17:52 GMT</pubDate></item><item><title><![CDATA[suggestions for upgrade path XCP-ng 8.2.1 -&gt; XCP-ng 8.3.0]]></title><description><![CDATA[Great! Keep us posted 
]]></description><link>https://xcp-ng.org/forum/topic/11653/suggestions-for-upgrade-path-xcp-ng-8.2.1-xcp-ng-8.3.0</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11653/suggestions-for-upgrade-path-xcp-ng-8.2.1-xcp-ng-8.3.0</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Sat, 06 Dec 2025 20:37:19 GMT</pubDate></item><item><title><![CDATA[log_fs_usage &#x2F; &#x2F;var&#x2F;log directory on pool master filling up constantly]]></title><description><![CDATA[Another thing that I noticed: despite enabling remote syslog (to graylog) for all XCP-ng hosts in the pool /var/log gets filled up to 100%.
Adding remote syslog seem to not change usage of /var/log at all.
Official XCP-ng documentation states otherwise here: https://docs.xcp-ng.org/installation/install-xcp-ng/#installation-on-usb-drives
The linked part of the documentation indicates that configuring remote syslog can be a possible solution for /var/log space constraints which seems to be not the case.
I feel like logging could use some investigation by Vates in general.
]]></description><link>https://xcp-ng.org/forum/topic/11630/log_fs_usage-var-log-directory-on-pool-master-filling-up-constantly</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11630/log_fs_usage-var-log-directory-on-pool-master-filling-up-constantly</guid><dc:creator><![CDATA[MajorP93]]></dc:creator><pubDate>Mon, 01 Dec 2025 17:23:46 GMT</pubDate></item></channel></rss>