<?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[Xen Orchestra]]></title><description><![CDATA[All Xen Orchestra related questions&#x2F;reports]]></description><link>https://xcp-ng.org/forum/category/12</link><generator>RSS for Node</generator><lastBuildDate>Tue, 14 Apr 2026 11:46:40 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/category/12.rss" rel="self" type="application/rss+xml"/><pubDate>Tue, 07 Apr 2026 18:18:10 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[load-balancer : Affinity to Host groups]]></title><description><![CDATA[Why not using anti affinity with the load balancer? This way, you can have multiple groups of VMs that won't run at the same place
]]></description><link>https://xcp-ng.org/forum/topic/12061/load-balancer-affinity-to-host-groups</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12061/load-balancer-affinity-to-host-groups</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Tue, 07 Apr 2026 18:18:10 GMT</pubDate></item><item><title><![CDATA[How do I apply host patches in XO-6?]]></title><description><![CDATA[@DustinB thank you!
I suspected as much, but as my wife points out all the time, I am terrible at finding things, so I figured I would ask.  
]]></description><link>https://xcp-ng.org/forum/topic/12057/how-do-i-apply-host-patches-in-xo-6</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12057/how-do-i-apply-host-patches-in-xo-6</guid><dc:creator><![CDATA[BrantleyHobbs]]></dc:creator><pubDate>Mon, 06 Apr 2026 14:32:59 GMT</pubDate></item><item><title><![CDATA[XOA Unable to connect xo server every 30s]]></title><description><![CDATA[Support tunnel is active but I have troubles to access support "Oops, something went wrong! Don't worry, our team is already on it".
I'll keep trying, thanks.
]]></description><link>https://xcp-ng.org/forum/topic/12052/xoa-unable-to-connect-xo-server-every-30s</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12052/xoa-unable-to-connect-xo-server-every-30s</guid><dc:creator><![CDATA[jerry1333]]></dc:creator><pubDate>Sat, 04 Apr 2026 13:20:46 GMT</pubDate></item><item><title><![CDATA[Axios NPM attack]]></title><description><![CDATA[I think I added it after the video ^^ (between the recording and the official release)
]]></description><link>https://xcp-ng.org/forum/topic/12041/axios-npm-attack</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12041/axios-npm-attack</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Wed, 01 Apr 2026 09:19:30 GMT</pubDate></item><item><title><![CDATA[ACL V2 is coming soon and we need your feedbacks!]]></title><link>https://xcp-ng.org/forum/topic/12036/acl-v2-is-coming-soon-and-we-need-your-feedbacks</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12036/acl-v2-is-coming-soon-and-we-need-your-feedbacks</guid><pubDate>Mon, 30 Mar 2026 12:03:55 GMT</pubDate></item><item><title><![CDATA[Removed VM - Now have unhealthy VDI]]></title><description><![CDATA[UPDATE: its been 2 days and as I suspected the VDI is still waiting to coalesce at a length of 1, The GC does not seem to be cleaning it up.
Does anyone have suggestions for how to remove this orphaned VDI and base copy.  I'm not interested in saving the VM just cleaning up the remnants of the botched migration and removal.
]]></description><link>https://xcp-ng.org/forum/topic/11997/removed-vm-now-have-unhealthy-vdi</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11997/removed-vm-now-have-unhealthy-vdi</guid><dc:creator><![CDATA[Zenon1823]]></dc:creator><pubDate>Sun, 22 Mar 2026 21:59:26 GMT</pubDate></item><item><title><![CDATA[HOST_NOT_ENOUGH_FREE_MEMORY]]></title><description><![CDATA[@Danp Okay thanks you
]]></description><link>https://xcp-ng.org/forum/topic/11979/host_not_enough_free_memory</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11979/host_not_enough_free_memory</guid><dc:creator><![CDATA[User-cxs]]></dc:creator><pubDate>Fri, 20 Mar 2026 12:20:25 GMT</pubDate></item><item><title><![CDATA[Loss of connection during an action BUG]]></title><description><![CDATA[@User-cxs peut etre un clnflit IP ou la VM prenait l'IP du master...
courage pour la suite ! 
]]></description><link>https://xcp-ng.org/forum/topic/11978/loss-of-connection-during-an-action-bug</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11978/loss-of-connection-during-an-action-bug</guid><dc:creator><![CDATA[Pilow]]></dc:creator><pubDate>Thu, 19 Mar 2026 11:14:44 GMT</pubDate></item><item><title><![CDATA[XOSTOR]]></title><description><![CDATA[But thank you for your time all the same.
]]></description><link>https://xcp-ng.org/forum/topic/11974/xostor</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11974/xostor</guid><dc:creator><![CDATA[User-cxs]]></dc:creator><pubDate>Tue, 17 Mar 2026 14:40:07 GMT</pubDate></item><item><title><![CDATA[After Update XO wont start]]></title><description><![CDATA[@geometry game 2 This usually happens when dependencies are out of sync after pulling updates. Did you try removing node_modules and the lock file and then running yarn install again before starting XO?
]]></description><link>https://xcp-ng.org/forum/topic/11948/after-update-xo-wont-start</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11948/after-update-xo-wont-start</guid><dc:creator><![CDATA[Oreckman]]></dc:creator><pubDate>Tue, 10 Mar 2026 16:59:03 GMT</pubDate></item><item><title><![CDATA[Created VM from Fast Clone, Now How to Separate]]></title><description><![CDATA[@hawkpro I believe it will be worse with continuous replication because your replica will be in a shut down state. When you decide to start it, you will have to shut down the original VM and start the replica. You will have a downtime during shut down and start up sequence.
Downtime during VM migration is a necessity so there is nothing unexpected there. All types of migrations require a VM to be suspended for some time (usually seconds) during the switchover from one host or SR to the other host or SR.
If you have extended downtimes of your VM migrations, then something is not quite right with your setup.
]]></description><link>https://xcp-ng.org/forum/topic/11939/created-vm-from-fast-clone-now-how-to-separate</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11939/created-vm-from-fast-clone-now-how-to-separate</guid><dc:creator><![CDATA[bvitnik]]></dc:creator><pubDate>Fri, 06 Mar 2026 15:53:34 GMT</pubDate></item><item><title><![CDATA[Migrations after updates]]></title><description><![CDATA[Hi @acebmxer,
I've made some tests with a small infrastructure, which helped me understand the behaviour you encounter.
With the performance plan, the load balancer can trigger migrations in the following cases:

to better satisfy affinity or anti-affinity constraints
if a host has a memory or CPU usage exceeds a threshold (85% of the CPU critical threshold, of 1.2 times the free memory critical threshold)
with vCPU balancing behaviour, if the vCPU/CPU ratio differs too much from one host to another AND at least one host has more vCPUs than CPUs
with preventive behaviour, if CPU usage differs too much from one host to another AND at least one host has more than 25% CPU usage

After a host restart, your VMs will be unevenly distributed, but this will not trigger a migration if there are no anti-affinity constraints to satisfy, if no memory or CPU usage thresholds are exceeded, and if no host has more CPUs than vCPUs.
If you want migrations to happen after a host restart, you should probably try using the "preventive" behaviour, which can trigger migrations even if thresholds are not reached. However it's based on CPU usage, so if your VMs use a lot of memory but don't use much CPU, this might not be ideal as well.
We've received very few feedback about the "preventive" behaviour, so we'd be happy to have yours. 
As we said before, lowering the critical thresholds might also be a solution, but I think it will make the load balancer less effective if you encounter heavy load a some point.
]]></description><link>https://xcp-ng.org/forum/topic/11937/migrations-after-updates</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11937/migrations-after-updates</guid><dc:creator><![CDATA[Bastien Nollet]]></dc:creator><pubDate>Thu, 05 Mar 2026 20:17:59 GMT</pubDate></item><item><title><![CDATA[Unable to connect to V5]]></title><description><![CDATA[
@olivierlambert said:
I think it was fixed since, are you sure you are using an uptodate XO?

Commit 0be23
Anyway was directing attention to the GitHub issue, which was opened. The issue has another reference to it.
]]></description><link>https://xcp-ng.org/forum/topic/11928/unable-to-connect-to-v5</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11928/unable-to-connect-to-v5</guid><dc:creator><![CDATA[john.c]]></dc:creator><pubDate>Tue, 03 Mar 2026 17:53:25 GMT</pubDate></item><item><title><![CDATA[IPMI Info Outlet Air temp missing.]]></title><description><![CDATA[@acebmxer I’m sorry to say that if those Dells are at your workplace, the wrong edition of iDRAC was purchased. You see with at the very least iDRAC 9 access to the full granular IPMI sensor data, was placed behind an edition paywall by Dell Technologies. Outlet temperature is just one of the feeds, missing from the Enterprise or lower edition of iDRAC 9. You’ll get the temperature readings from the Dell iDRAC web browser based interface, but not IPMI with iDRAC 9 Enterprise.
To obtain the full IPMI sensor data you need the Datacenter edition.
]]></description><link>https://xcp-ng.org/forum/topic/11927/ipmi-info-outlet-air-temp-missing.</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11927/ipmi-info-outlet-air-temp-missing.</guid><dc:creator><![CDATA[john.c]]></dc:creator><pubDate>Tue, 03 Mar 2026 17:16:03 GMT</pubDate></item><item><title><![CDATA[VDIS not showing in XO5, but are in XO6 and on the VM itself ?]]></title><description><![CDATA[@kent you would have to rollback to early december 2025 XO/XOA (before the 10 of december)
quite a long way
I'm just waiting the devs to eventually fix it as we have other way to manage VDIs (API calls)
]]></description><link>https://xcp-ng.org/forum/topic/11920/vdis-not-showing-in-xo5-but-are-in-xo6-and-on-the-vm-itself</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11920/vdis-not-showing-in-xo5-but-are-in-xo6-and-on-the-vm-itself</guid><dc:creator><![CDATA[Pilow]]></dc:creator><pubDate>Sat, 28 Feb 2026 19:25:58 GMT</pubDate></item><item><title><![CDATA[XOA SocketError: Other side Closed]]></title><link>https://xcp-ng.org/forum/topic/11913/xoa-socketerror-other-side-closed</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11913/xoa-socketerror-other-side-closed</guid><pubDate>Fri, 27 Feb 2026 02:59:09 GMT</pubDate></item><item><title><![CDATA[Install XO from sources.]]></title><description><![CDATA[@AlexanderK
The ronivay script requires you to select an option (#2 to update).
I look at things this way, it's good to have more people working on scripts like this.
]]></description><link>https://xcp-ng.org/forum/topic/11895/install-xo-from-sources.</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11895/install-xo-from-sources.</guid><dc:creator><![CDATA[Greg_E]]></dc:creator><pubDate>Sun, 22 Feb 2026 18:34:30 GMT</pubDate></item><item><title><![CDATA[XOA Create VM and Delete VM Struggling..... Tasks Getting Stuck.....?]]></title><description><![CDATA[@MichaelCropper
Truenas on bare metal just as storage, XCP-NG is also bare metal on 3 hosts to make a pool. That's the minimum if you want to enable High Availability, it also works really well as a "normal" pool which is what I have.
Rolling Pool functions are great, click the button and the system moves the VMS off of the host that need updates, reboots, moves VMs off of the next host, repeat. Only works with Shared storage.
]]></description><link>https://xcp-ng.org/forum/topic/11894/xoa-create-vm-and-delete-vm-struggling.....-tasks-getting-stuck.....</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11894/xoa-create-vm-and-delete-vm-struggling.....-tasks-getting-stuck.....</guid><dc:creator><![CDATA[Greg_E]]></dc:creator><pubDate>Sun, 22 Feb 2026 01:45:33 GMT</pubDate></item><item><title><![CDATA[XOA - Memory Usage]]></title><description><![CDATA[@florent @mathieura Support ticket opened - Ticket#7756329
As noted in ticket Yes that is ok.  Just note this is production systems.
]]></description><link>https://xcp-ng.org/forum/topic/11892/xoa-memory-usage</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11892/xoa-memory-usage</guid><dc:creator><![CDATA[acebmxer]]></dc:creator><pubDate>Sat, 21 Feb 2026 20:55:26 GMT</pubDate></item><item><title><![CDATA[Commit 109e376 Implications]]></title><description><![CDATA[Latest XO can be new tested along XCP-ng (with OpenSSL 3):
https://xcp-ng.org/forum/topic/9964/xcp-ng-8-3-updates-announcements-and-testing/363
Feedback welcome
]]></description><link>https://xcp-ng.org/forum/topic/11887/commit-109e376-implications</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11887/commit-109e376-implications</guid><dc:creator><![CDATA[rzr]]></dc:creator><pubDate>Fri, 20 Feb 2026 12:08:36 GMT</pubDate></item><item><title><![CDATA[Second IP for Hosts Interface]]></title><description><![CDATA[@jqueiroz said in Second IP for Hosts Interface:

I have a situation where I would like to add a second IPv4 address to the management interface of a host.
I am installing a host that will be used in another location and I would like to add the address of that location to the management interface before shipping the machine there.
Is it possible to do this, or should I continue using the current procedure (making the necessary configurations and change the address shortly before shutting down the machine and packing it for transport)?

there is a nuance between secondary IP and secondary MANAGEMENT IP
if you have multiple NICS, you could add &amp; configure the destination site IP on it, but it is not flagged management yet.
once the server gets on the new site, you could access web ui by this IP address (or SSH)
and then either go to web console/xs server or SSH and do the necessary to change management to the good PIF/IP ?
]]></description><link>https://xcp-ng.org/forum/topic/11862/second-ip-for-hosts-interface</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11862/second-ip-for-hosts-interface</guid><dc:creator><![CDATA[Pilow]]></dc:creator><pubDate>Wed, 11 Feb 2026 22:54:14 GMT</pubDate></item><item><title><![CDATA[VM metadata import fail &amp; stuck]]></title><description><![CDATA[@henri9813 Ahh alright, I understand now! Thanks for clarifying.
]]></description><link>https://xcp-ng.org/forum/topic/11817/vm-metadata-import-fail-stuck</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11817/vm-metadata-import-fail-stuck</guid><dc:creator><![CDATA[nikade]]></dc:creator><pubDate>Sat, 31 Jan 2026 08:19:51 GMT</pubDate></item><item><title><![CDATA[Rolling Updates Failed]]></title><description><![CDATA[Hi!
ISO-SR over HBA/FC would be very nice, especially when migration form a SAN vmware-System to XCP-NG.
One other thing is altering. Errors like "VM cannot be migrated" or similar should not be silent but should be very visible / even mailed to the admin.
Another thing (could be cosmetical though) in my opinion is that a failed Rolling upgrade remains visible with a half fulled progress bar in the task-view. this is confusing.
]]></description><link>https://xcp-ng.org/forum/topic/11814/rolling-updates-failed</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11814/rolling-updates-failed</guid><dc:creator><![CDATA[jacob.becker]]></dc:creator><pubDate>Thu, 29 Jan 2026 18:30:16 GMT</pubDate></item><item><title><![CDATA[V5 works fine with XenServer 8.4, v6 doesnt work?]]></title><description><![CDATA[@MathieuRA
As announced, I have now installed branch  xo6/update-site-dashboard and it seems to be working. It no longer loads endlessly and shows me that I haven't configured anything yet 
Thank you very much!
]]></description><link>https://xcp-ng.org/forum/topic/11812/v5-works-fine-with-xenserver-8.4-v6-doesnt-work</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11812/v5-works-fine-with-xenserver-8.4-v6-doesnt-work</guid><dc:creator><![CDATA[ElFritto]]></dc:creator><pubDate>Thu, 29 Jan 2026 07:15:08 GMT</pubDate></item><item><title><![CDATA[XOA Audit Log shows Failed logins for LDAP&#x2F;AD on successful connections]]></title><description><![CDATA[Hi,
Thanks for your feedback! Let me ping @bastien-nollet or @pdonias maybe
]]></description><link>https://xcp-ng.org/forum/topic/11811/xoa-audit-log-shows-failed-logins-for-ldap-ad-on-successful-connections</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11811/xoa-audit-log-shows-failed-logins-for-ldap-ad-on-successful-connections</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Wed, 28 Jan 2026 22:14:31 GMT</pubDate></item></channel></rss>