<?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[Management]]></title><description><![CDATA[VMs, hosts, pools, networks and all other usual management tasks.]]></description><link>https://xcp-ng.org/forum/category/23</link><generator>RSS for Node</generator><lastBuildDate>Mon, 15 Jun 2026 16:41:26 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/category/23.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 10 Jun 2026 23:35:29 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[XOA host got disconnected and cannot re-add with error connect ECONNREFUSED x.x.x.x:443]]></title><description><![CDATA[Hi,
IP conflict?
]]></description><link>https://xcp-ng.org/forum/topic/12273/xoa-host-got-disconnected-and-cannot-re-add-with-error-connect-econnrefused-x.x.x.x-443</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12273/xoa-host-got-disconnected-and-cannot-re-add-with-error-connect-econnrefused-x.x.x.x-443</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Wed, 10 Jun 2026 23:35:29 GMT</pubDate></item><item><title><![CDATA[Tag-Based Automation Plugin: Tag-Based VM Performance &amp; Permission Management via assigned tag(s)]]></title><description><![CDATA[@julienXOvates Noted, thank you!
]]></description><link>https://xcp-ng.org/forum/topic/12265/tag-based-automation-plugin-tag-based-vm-performance-permission-management-via-assigned-tag-s</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12265/tag-based-automation-plugin-tag-based-vm-performance-permission-management-via-assigned-tag-s</guid><dc:creator><![CDATA[johnnezero]]></dc:creator><pubDate>Mon, 08 Jun 2026 02:29:36 GMT</pubDate></item><item><title><![CDATA[CBR start operation is blocked]]></title><description><![CDATA[Hello. Thank you for your input. I am aware, that this is more of a warning message, than a error. I´m just trying to figure out, what is my best way to go here.
My plan was:

Setup a repljob for the vm in a lets say hourly interval
On the day of the migration, shutdown the vm and start the last replication manually
Disable the cr job
Start the replicated vm on the new pool, check it and if all is ok, use it as new vm, otherwise start the old vm.

The documentation says "If you want to start a VM on your destination host without breaking the CR jobs". Tbh i dont care about breaking the job. If everything works fine, i dont need it anymore, if not, i can setup a new job pretty fast. I was just wondering, if the new vm will stay in "blocked mode" for ever.
Kind regards
]]></description><link>https://xcp-ng.org/forum/topic/12251/cbr-start-operation-is-blocked</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12251/cbr-start-operation-is-blocked</guid><dc:creator><![CDATA[Milenko]]></dc:creator><pubDate>Mon, 01 Jun 2026 10:36:25 GMT</pubDate></item><item><title><![CDATA[Create a new SR: qcow2 failure]]></title><description><![CDATA[
@florent said:
where does this disk comes from

From my Redhat 10

@florent said:
if you have access to your SR from the outside, you can also put the qcow2 file directly

I create a VM to be a NFS to access the 3 HDs, the qcow disks are on the Redhat 10 that I was trying to import from.  Do you mean I put the qcow disks on one of the HDs and access them when I create a VM?
]]></description><link>https://xcp-ng.org/forum/topic/12225/create-a-new-sr-qcow2-failure</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12225/create-a-new-sr-qcow2-failure</guid><dc:creator><![CDATA[nasheayahu]]></dc:creator><pubDate>Mon, 18 May 2026 05:23:16 GMT</pubDate></item><item><title><![CDATA[Attach a Physical HD to a VM?]]></title><description><![CDATA[
@dthenot said:
you will also likely need to give the host-uuid of the host the disk is on

Thanks, and I'm assuming this UUID or Machine ID from:
[14:45 xcp-kbbn NAS]# dmidecode --type SYSTEM
# dmidecode 3.0
Getting SMBIOS data from sysfs.
SMBIOS 3.3.0 present.
# SMBIOS implementations newer than version 3.0 are not
# fully supported by this version of dmidecode.

Handle 0x0001, DMI type 1, 27 bytes
System Information
        Manufacturer: ASUS
        Product Name: System Product Name
        Version: System Version
        Serial Number: System Serial Number
        UUID: E7AE9723-CB08-A278-5C45-7C10C9473BD0
        Wake-up Type: Power Switch
        SKU Number: SKU
        Family: To be filled by O.E.M.

OR
[12:46 xcp-kbbn NAS]# hostnamectl
   Static hostname: xcp-kbbn
         Icon name: computer-desktop
           Chassis: desktop
        Machine ID: c668f529e66c42b9815fe12f3401df82
           Boot ID: dd70b200b25341c688aee9fbc58d20a2
    Virtualization: xen
  Operating System: XCP-ng 8.3
            Kernel: Linux 4.19.0+1
      Architecture: x86-64

the command would look like this correct:
xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=E7AE9723-CB08-A278-5C45-7C10C9473BD0 or c668f529e66c42b9815fe12f3401df82

UPDATE:  I tried the new command but I got these error messages:
[14:45 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=E7AE9723-CB08-A278-5C45-7C10C9473BD0
The uuid you supplied was invalid.
type: host
uuid: E7AE9723-CB08-A278-5C45-7C10C9473BD0
[15:14 xcp-kbbn NAS]# ls
[15:19 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=c668f529e66c42b9815fe12f3401df82
The uuid you supplied was invalid.
type: host
uuid: c668f529e66c42b9815fe12f3401df82

then I was successful (I believe with you confirmation) when I left our the host-uuid param:
[15:19 xcp-kbbn NAS]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks"
b802722e-67ac-5aba-8d6c-e565d2d7fa0d

and then it was listed as a SR:
[image: 1779139583485-screenshot-from-2026-05-18-15-24-03.png]
now to the next task command:
xe sr-scan uuid=b802722e-67ac-5aba-8d6c-e565d2d7fa0d

was successful, but I have another Question, the size of the device is not showing, is this normal being that it was done this way?
UPDATE 2.0:  I just discovered the xe command:
[15:27 xcp-kbbn NAS]# xe host-list
uuid ( RO)                : 9a5e5bb3-bdb9-41ea-9505-6f6fe630f369
          name-label ( RW): xcp-kbbn

the uuid does not match the ones provided above, do I need to remove the SR and do it over again using this uuid?  I will give it a try using another folder....
UPDATE 2.1: I executed the command using the above uuid:
[15:35 xcp-kbbn srv]# xe sr-create type=udev device-config:location=/srv/NAS name-label="NAS Disks" host-uuid=9a5e5bb3-bdb9-41ea-9505-6f6fe630f369
6fc531a0-19a0-b9c1-c78e-c687fce5ff84

and was successful, but now my question for the device size, is it normal or not due to creating it this way?
UPDATE 2.2: I forgot to do:
ln -s /dev/sda /srv/NAS/sda #although it might be better to use a stable identifier if you have multiple disks
xe sr-scan uuid=&lt;UUID of the udev SR&gt;

be right back.....
UPDATE 3.0: Success, I have all HDs attached to my VM, access all files and the sizes are reported!  :
[image: 1779147782991-screenshot-from-2026-05-18-17-25-38.png]
List of attached disks:
[image: 1779147797114-screenshot-from-2026-05-18-17-18-07.png]
The VM:
[image: 1779148373193-screenshot-from-2026-05-18-17-51-19.png]
Thanks for your help!... 
]]></description><link>https://xcp-ng.org/forum/topic/12224/attach-a-physical-hd-to-a-vm</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12224/attach-a-physical-hd-to-a-vm</guid><dc:creator><![CDATA[nasheayahu]]></dc:creator><pubDate>Sun, 17 May 2026 23:22:40 GMT</pubDate></item><item><title><![CDATA[Tag-Based Automation: Manage VM CPU Priority via assigned tag.]]></title><description><![CDATA[@johnnezero The full HTML versions will render much better. The PDF conversion is less than perfect. iIll try to get those uploaded, as well.
]]></description><link>https://xcp-ng.org/forum/topic/12215/tag-based-automation-manage-vm-cpu-priority-via-assigned-tag.</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12215/tag-based-automation-manage-vm-cpu-priority-via-assigned-tag.</guid><dc:creator><![CDATA[tjkreidl]]></dc:creator><pubDate>Thu, 14 May 2026 02:48:24 GMT</pubDate></item><item><title><![CDATA[Old VM:s shows up]]></title><description><![CDATA[Hi!
I think what you're seeing may be stale entries in the XAPI database, ghost records that can survive upgrades or host reconfigurations. 
From what I've read, xe vm-destroy uuid=&lt;vm-uuid&gt; removes the record without touching any storage, which seems like what you need here; the xe CLI reference confirms storage is left intact.
I think you can get the UUID first with xe vm-list name-label="Before Ubuntu Update" (replacing the name with whichever one you're after).
I'm not entirely sure why xsconsole would show them but XO wouldn't, so if the VMs don't turn up in xe vm-list, it might be worth a mention to Team-XAPI-Network, they'll know the right way to dig into XAPI state.
]]></description><link>https://xcp-ng.org/forum/topic/12207/old-vm-s-shows-up</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12207/old-vm-s-shows-up</guid><dc:creator><![CDATA[poddingue]]></dc:creator><pubDate>Mon, 11 May 2026 11:51:04 GMT</pubDate></item><item><title><![CDATA[Understanding Auto Power On | Auto Start]]></title><description><![CDATA[@poddingue there is a notion of appliance too (group of VMs)
https://docs.xcp-ng.org/appendix/cli_reference/#appliance-commands
where you can start/stop a group of VMs, never tried it, doesn't seem to have a boot order in the vAPP neither
]]></description><link>https://xcp-ng.org/forum/topic/12149/understanding-auto-power-on-auto-start</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12149/understanding-auto-power-on-auto-start</guid><dc:creator><![CDATA[Pilow]]></dc:creator><pubDate>Tue, 05 May 2026 15:03:04 GMT</pubDate></item><item><title><![CDATA[&quot;app.getLicenses is not a function&quot; when I try to add a node to my pool]]></title><description><![CDATA[@bvivi57 xo do check license if you have xostor installed, since it need some magic to work at a lot of steps ( like the rolling pool updates)
this is the expected behavior with a manually installed xostor ( cc @julienxovates  for information )
]]></description><link>https://xcp-ng.org/forum/topic/12141/app.getlicenses-is-not-a-function-when-i-try-to-add-a-node-to-my-pool</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12141/app.getlicenses-is-not-a-function-when-i-try-to-add-a-node-to-my-pool</guid><dc:creator><![CDATA[florent]]></dc:creator><pubDate>Tue, 05 May 2026 06:28:20 GMT</pubDate></item><item><title><![CDATA[RPU Failure on 8.3: Yum HTTPS 500 Error for xo-lite package (Hung Task)]]></title><description><![CDATA[@julienXOvates Got it.
I didn't get a chance to work on this over the weekend, so sometime this week, I'll just bounce the host and see if it comes back.  Right now, while I can SSH into it, the admin console appears to be frozen and unresponsive (over iLO).
]]></description><link>https://xcp-ng.org/forum/topic/12136/rpu-failure-on-8.3-yum-https-500-error-for-xo-lite-package-hung-task</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12136/rpu-failure-on-8.3-yum-https-500-error-for-xo-lite-package-hung-task</guid><dc:creator><![CDATA[kagbasi-wgsdac]]></dc:creator><pubDate>Fri, 01 May 2026 08:40:44 GMT</pubDate></item><item><title><![CDATA[Difference between Pool&#x27;s CPU usage stats and Host CPU usage stats]]></title><description><![CDATA[
@delacosta456 said:
the pool host maximum limit is 3200% right

right
]]></description><link>https://xcp-ng.org/forum/topic/12099/difference-between-pool-s-cpu-usage-stats-and-host-cpu-usage-stats</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12099/difference-between-pool-s-cpu-usage-stats-and-host-cpu-usage-stats</guid><dc:creator><![CDATA[Pilow]]></dc:creator><pubDate>Fri, 24 Apr 2026 08:32:08 GMT</pubDate></item><item><title><![CDATA[XenClean | Cleanup Failed on Windows Server 2022 VM]]></title><description><![CDATA[@dinhngtu Thanks for the fast response, as always.
]]></description><link>https://xcp-ng.org/forum/topic/12096/xenclean-cleanup-failed-on-windows-server-2022-vm</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12096/xenclean-cleanup-failed-on-windows-server-2022-vm</guid><dc:creator><![CDATA[kagbasi-wgsdac]]></dc:creator><pubDate>Thu, 23 Apr 2026 09:27:12 GMT</pubDate></item><item><title><![CDATA[xo-disk-cli on latest XOA node.js problem]]></title><description><![CDATA[@Andrew Yeah but XOA is still using it hence my interest in aligning my XO-CE instance with XOA as close as possible.
]]></description><link>https://xcp-ng.org/forum/topic/12063/xo-disk-cli-on-latest-xoa-node.js-problem</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12063/xo-disk-cli-on-latest-xoa-node.js-problem</guid><dc:creator><![CDATA[MajorP93]]></dc:creator><pubDate>Wed, 08 Apr 2026 11:27:53 GMT</pubDate></item><item><title><![CDATA[How to unbind trial license]]></title><description><![CDATA[Hello @tsukraw , normally your client should be able to bind the new license on their XOA. BTW, you talk about binding the license to a pool but an XOA license is bound to an XOA. I suggest your customer open a support  ticket so we can help them with that issue.
]]></description><link>https://xcp-ng.org/forum/topic/12058/how-to-unbind-trial-license</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12058/how-to-unbind-trial-license</guid><dc:creator><![CDATA[gregoire]]></dc:creator><pubDate>Mon, 06 Apr 2026 21:20:13 GMT</pubDate></item><item><title><![CDATA[Rolling Pool Update and Affinity Host]]></title><description><![CDATA[Yes indeed, that's expected. XAPI affinity is on VM boot, not in the VM life. Then, it's the work of the load balancer.
]]></description><link>https://xcp-ng.org/forum/topic/12032/rolling-pool-update-and-affinity-host</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12032/rolling-pool-update-and-affinity-host</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Sat, 28 Mar 2026 01:53:00 GMT</pubDate></item><item><title><![CDATA[Double CR backup]]></title><description><![CDATA[Ping @Team-XO-Backend
]]></description><link>https://xcp-ng.org/forum/topic/12012/double-cr-backup</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12012/double-cr-backup</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Thu, 26 Mar 2026 11:48:01 GMT</pubDate></item><item><title><![CDATA[Lates commit breaks install]]></title><description><![CDATA[@gregbinsd
let us know.
If you do use my script.  It pulls nodejs from NodeSource so it may not install the latest 24.15.0 tls.  If you specific 24.15.0 it will install that version.  If you need to change node version with my script use the rebuild option.
]]></description><link>https://xcp-ng.org/forum/topic/12002/lates-commit-breaks-install</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12002/lates-commit-breaks-install</guid><dc:creator><![CDATA[acebmxer]]></dc:creator><pubDate>Tue, 24 Mar 2026 15:08:00 GMT</pubDate></item><item><title><![CDATA[VM Unable to Attach ISOs After Reverting Snapshot]]></title><description><![CDATA[@dinhngtu Yeah, I suspected that as well.  So I inspected the SR and it showed connected to both hosts (at least in the XO UI - I didn't drop to the CLI to really confirm).
By altering my workflow a bit and slowing down, I seem to have found the right "sweet spot" of delay and the issue hasn't resurfaced.  Here's what I'm doing now, when I need to revert the snapshots of all three VMs:

In the XO VM list, I select the three VMs and power them off at the same time.
I then start with VM1 and eject the ISO, VM2 and eject the ISO, then VM3 and eject the ISO.  By the time I circle back to VM1 for the next step, about 10-15 secs have elapsed.
I then start with VM1 and revert the snapshot, and repeat the same on VM2 and VM3.  By the time I circle back to VM1 for the next step, another 10-15 secs have elapsed.
I re-attach the ISO to all three VMs in sequence.  Another 10-15 secs elapse.
I then start with VM1 and power all three VMs sequentially.

The entire workflow takes about 30-45 secs, and I'm finding that by doing this, the issue hasn't resurfaced.
]]></description><link>https://xcp-ng.org/forum/topic/11996/vm-unable-to-attach-isos-after-reverting-snapshot</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11996/vm-unable-to-attach-isos-after-reverting-snapshot</guid><dc:creator><![CDATA[kagbasi-wgsdac]]></dc:creator><pubDate>Sun, 22 Mar 2026 12:45:32 GMT</pubDate></item><item><title><![CDATA[OPNsense in VM - VIF discrepancies]]></title><link>https://xcp-ng.org/forum/topic/11956/opnsense-in-vm-vif-discrepancies</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11956/opnsense-in-vm-vif-discrepancies</guid><pubDate>Thu, 12 Mar 2026 01:20:55 GMT</pubDate></item><item><title><![CDATA[Is there a way to turn off xentools vulnerable message for non-admins?]]></title><description><![CDATA[Good question! Ping @pdonias I assume 
]]></description><link>https://xcp-ng.org/forum/topic/11925/is-there-a-way-to-turn-off-xentools-vulnerable-message-for-non-admins</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11925/is-there-a-way-to-turn-off-xentools-vulnerable-message-for-non-admins</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Tue, 03 Mar 2026 12:29:52 GMT</pubDate></item><item><title><![CDATA[Deteching Host is Failing with Error]]></title><description><![CDATA[Just go to Settings &gt; Servers tab in XO and remove the entry associated with this pool.
]]></description><link>https://xcp-ng.org/forum/topic/11911/deteching-host-is-failing-with-error</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11911/deteching-host-is-failing-with-error</guid><dc:creator><![CDATA[Danp]]></dc:creator><pubDate>Thu, 26 Feb 2026 15:26:45 GMT</pubDate></item><item><title><![CDATA[VM Disk Not Migrating due to Backup Running]]></title><description><![CDATA[@olivierlambert It's even older than that. 
https://github.com/vatesfr/xen-orchestra/blob/master/CHANGELOG.v5.md#5540-2020-12-29
https://xen-orchestra.com/blog/xen-orchestra-5-54/
]]></description><link>https://xcp-ng.org/forum/topic/11888/vm-disk-not-migrating-due-to-backup-running</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11888/vm-disk-not-migrating-due-to-backup-running</guid><dc:creator><![CDATA[Danp]]></dc:creator><pubDate>Fri, 20 Feb 2026 15:25:05 GMT</pubDate></item><item><title><![CDATA[Unable to copy template]]></title><description><![CDATA[While I was updating all the pools, a micro-update for 5 packages was released again. They come out every week now. 
Same issue with basic migration. Now it impossible.
]]></description><link>https://xcp-ng.org/forum/topic/11859/unable-to-copy-template</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11859/unable-to-copy-template</guid><dc:creator><![CDATA[Tristis Oris]]></dc:creator><pubDate>Wed, 11 Feb 2026 10:23:57 GMT</pubDate></item><item><title><![CDATA[Unable to remove non-existent SR]]></title><description><![CDATA[@Danp damned, i forget about this button) Now it works, thanks.
]]></description><link>https://xcp-ng.org/forum/topic/11851/unable-to-remove-non-existent-sr</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11851/unable-to-remove-non-existent-sr</guid><dc:creator><![CDATA[Tristis Oris]]></dc:creator><pubDate>Mon, 09 Feb 2026 09:15:41 GMT</pubDate></item><item><title><![CDATA[XO Update fails]]></title><description><![CDATA[@florent
Thanks again for your assistance, greatly appreciated.
]]></description><link>https://xcp-ng.org/forum/topic/11850/xo-update-fails</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11850/xo-update-fails</guid><dc:creator><![CDATA[Whitebeard]]></dc:creator><pubDate>Mon, 09 Feb 2026 02:16:02 GMT</pubDate></item></channel></rss>