<?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[Development]]></title><description><![CDATA[The place to discuss new additions into XCP-ng]]></description><link>https://xcp-ng.org/forum/category/7</link><generator>RSS for Node</generator><lastBuildDate>Sun, 13 Sep 2026 22:48:17 GMT</lastBuildDate><atom:link href="https://xcp-ng.org/forum/category/7.rss" rel="self" type="application/rss+xml"/><pubDate>Wed, 26 Aug 2026 15:39:40 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[XCP-NG 9.0 Support for GRAID Tech GPU-accelerated RAID cards.]]></title><description><![CDATA[This was sent to me yesterday!!
See our Engineering Team lead's response:
We evaluated XCP-ng 8.3 some time ago, but its dom0 kernel was too old for our driver to work properly. Running SupremeRAID inside a DomU should be feasible and is similar to the approach we previously proposed for VMware. However, with XCP-ng 8.3, we did not find a practical native path to export the SupremeRAID VD back to dom0 and use it as an XCP-ng SR. Using iSCSI for this purpose would add significant protocol and networking overhead, which is not ideal for high-performance NVMe storage.
I revisited XCP-ng 9.0 and the current Xen/XAPI development. A more promising approach is to run SupremeRAID in a dedicated AlmaLinux VM with the GPU and NVMe drives passed through, then use Xen's native xen-blkback interface to export the SupremeRAID block device back to dom0. Dom0 would see the exported VD as a normal Xen block device, which could then potentially be used to create a standard XCP-ng LVM SR.
This approach is much more attractive than iSCSI or NVMe/TCP because the data path uses Xen's blkif shared-memory interface rather than a network protocol. xen-blkback itself is an established Xen mechanism, and Xen supports using a separate domain as a block backend. However, XCP-ng does not currently provide complete first-class lifecycle management for this configuration, so we still need to validate the exact behavior on XCP-ng 9.0, particularly persistent attachment, storage VM startup ordering, and recovery after a host or storage VM reboot.
If they can help confirm that the GPU and NVMe drives can be passed through to the storage VM, SupremeRAID can run normally there, and the resulting VD can be exported through xen-blkback to dom0 and used as an XCP-ng SR, I think this could be a very solid architecture for SupremeRAID on XCP-ng.
As for write durability, SupremeRAID always operates in write-through mode. An I/O is acknowledged only after all associated data, including parity, has been committed to the drives. Therefore, acknowledged writes do not depend on data or parity remaining only in volatile GPU or host memory
Can you do the initial testing with SupremeRAID PRO within your environment?
I will begin the initial testing and builds with 4 nodes:
1 &amp; 2 are HP DL380 Gen10 - 2x Xeon Gold 6151 36 Cores 384GB RAM 4 3.84Tb PCI4.0 NVMe per node. Twinstore Testing - Run the Build environment on these
3 is a HP Dl360 Gen10 2x Xeon Gold 6151 36 Cores 512Gb RAM 4x1.92TB NVMe Drives

SuperServer SYS-122H-TN- X14 2x Xeon 6740 96 cores, 512GB RAM, GRAID Card - 4x Pci5.0 7.68TB drives SupremeRAID.

All the nodes have 2x100Gbps ports, 2x25Gbps ports. Arista Backed network.
]]></description><link>https://xcp-ng.org/forum/topic/12436/xcp-ng-9.0-support-for-graid-tech-gpu-accelerated-raid-cards.</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12436/xcp-ng-9.0-support-for-graid-tech-gpu-accelerated-raid-cards.</guid><dc:creator><![CDATA[hydromike]]></dc:creator><pubDate>Wed, 26 Aug 2026 15:39:40 GMT</pubDate></item><item><title><![CDATA[Custom Provider support for Parallels RAS CPF integration]]></title><description><![CDATA[@rvreugde I believe this is already being reviewed internally.
]]></description><link>https://xcp-ng.org/forum/topic/12355/custom-provider-support-for-parallels-ras-cpf-integration</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12355/custom-provider-support-for-parallels-ras-cpf-integration</guid><dc:creator><![CDATA[Danp]]></dc:creator><pubDate>Tue, 14 Jul 2026 07:26:42 GMT</pubDate></item><item><title><![CDATA[How to reliably determine VDI format (vhd, qcow2, raw) via XAPI across versions]]></title><description><![CDATA[@dthenot Thanks a lot for the information. I did some more testing on my end and I've now noticed differences in handling VDI format across different SR types (local LVM and EXT). Should I expect even more differences across remote SR types like LVMoHBA or NFS or are these differences more like block based vs file system based SRs?
Any way, it looks like I have to consult the following keys:

image-format
vdi_type
type

In my tests, local EXT SRs tend to have only one of them, while local LVM SRs tend to have first two or all three, depends which one was used when creating the VDI.
]]></description><link>https://xcp-ng.org/forum/topic/12259/how-to-reliably-determine-vdi-format-vhd-qcow2-raw-via-xapi-across-versions</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12259/how-to-reliably-determine-vdi-format-vhd-qcow2-raw-via-xapi-across-versions</guid><dc:creator><![CDATA[bvitnik]]></dc:creator><pubDate>Thu, 04 Jun 2026 21:26:25 GMT</pubDate></item><item><title><![CDATA[89 vulnerabilities in XAPI / Citrix XenServer]]></title><description><![CDATA[Xen Project covered this as XSA-489.
]]></description><link>https://xcp-ng.org/forum/topic/12105/89-vulnerabilities-in-xapi-citrix-xenserver</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12105/89-vulnerabilities-in-xapi-citrix-xenserver</guid><dc:creator><![CDATA[TeddyAstie]]></dc:creator><pubDate>Mon, 27 Apr 2026 17:34:41 GMT</pubDate></item><item><title><![CDATA[Consideration for other HCI storage in v9?]]></title><link>https://xcp-ng.org/forum/topic/12079/consideration-for-other-hci-storage-in-v9</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12079/consideration-for-other-hci-storage-in-v9</guid><pubDate>Mon, 13 Apr 2026 15:45:19 GMT</pubDate></item><item><title><![CDATA[Build XCP-ng ISO - issue at create-installimg]]></title><description><![CDATA[Thank you so much for your feedback, @Vagrantin ! 
]]></description><link>https://xcp-ng.org/forum/topic/12078/build-xcp-ng-iso-issue-at-create-installimg</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12078/build-xcp-ng-iso-issue-at-create-installimg</guid><dc:creator><![CDATA[poddingue]]></dc:creator><pubDate>Mon, 13 Apr 2026 14:27:51 GMT</pubDate></item><item><title><![CDATA[iso modification and gpg key check]]></title><description><![CDATA[Nice catch @vagrantin !
Feel free to open a new thread if you have other problems.
]]></description><link>https://xcp-ng.org/forum/topic/12048/iso-modification-and-gpg-key-check</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12048/iso-modification-and-gpg-key-check</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Thu, 02 Apr 2026 04:01:31 GMT</pubDate></item><item><title><![CDATA[PRs for wording cleanup - worth doing?]]></title><description><![CDATA[There's no small contributions, every one of them are great &amp; welcome!
]]></description><link>https://xcp-ng.org/forum/topic/12033/prs-for-wording-cleanup-worth-doing</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/12033/prs-for-wording-cleanup-worth-doing</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Sat, 28 Mar 2026 14:43:21 GMT</pubDate></item><item><title><![CDATA[Rust-based guest-tools... How are things going?]]></title><description><![CDATA[@olivierlambert said in Rust-based guest-tools... How are things going?:

The thing is that it works very well and doesn't need fixes…  I know, not usual right? It was so stable that we left it like that waiting for people coming for bugs and nothing happened… We'll cut a 1.0 in the next weeks/months.

I have indeed seen the stability of it myself. But the lack of updates made me worry anyway. But I'm really looking forward to the promotion to 1.0 as well.
Thanks!
]]></description><link>https://xcp-ng.org/forum/topic/11912/rust-based-guest-tools...-how-are-things-going</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11912/rust-based-guest-tools...-how-are-things-going</guid><dc:creator><![CDATA[probain]]></dc:creator><pubDate>Thu, 26 Feb 2026 19:22:27 GMT</pubDate></item><item><title><![CDATA[Bitten by XSA-474]]></title><description><![CDATA[I have no clue, I usually back it up with XO, its the one called "XO config &amp; pool metadata backup" and only had to restore it once.
]]></description><link>https://xcp-ng.org/forum/topic/11740/bitten-by-xsa-474</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11740/bitten-by-xsa-474</guid><dc:creator><![CDATA[nikade]]></dc:creator><pubDate>Fri, 02 Jan 2026 13:34:20 GMT</pubDate></item><item><title><![CDATA[xcp-ng-8.3 Upcoming behaviour changes ? eg: Usage of history]]></title><description><![CDATA[Hi according to gh, it looks like there is traction on this feature:
https://github.com/xcp-ng/xcp-ng-release/pull/53#discussion_r2642865515
So it might be merged soon...
]]></description><link>https://xcp-ng.org/forum/topic/11697/xcp-ng-8.3-upcoming-behaviour-changes-eg-usage-of-history</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11697/xcp-ng-8.3-upcoming-behaviour-changes-eg-usage-of-history</guid><dc:creator><![CDATA[rzr]]></dc:creator><pubDate>Thu, 18 Dec 2025 13:49:21 GMT</pubDate></item><item><title><![CDATA[Building XCP-ng from source code]]></title><description><![CDATA[@Greg_E said in Building XCP-ng from source code:

@olivierlambert
Ok, thanks. Yes I'm eagerly awaiting XCP-ng 9 for testing.

Hi, check this thread:
https://xcp-ng.org/forum/topic/11698/xcp-ng-9.0-demonstrator-early-preview
More coming...
]]></description><link>https://xcp-ng.org/forum/topic/11425/building-xcp-ng-from-source-code</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11425/building-xcp-ng-from-source-code</guid><dc:creator><![CDATA[rzr]]></dc:creator><pubDate>Wed, 15 Oct 2025 13:48:45 GMT</pubDate></item><item><title><![CDATA[Patch for CVE-2025-27466, CVE-2025-58142, CVE-2025-58143]]></title><description><![CDATA[@bleader just checked the Excel assessment file I got from the security team. They used Crowdstrike (sensor is not installed on xcp-ng hosts).
The funny thing is, the asset that it reports as vulnerable is the VM that is running XOA (official image provided by XCP-NG). It is deployed recently, so everything is up-to-date, but even then I don't understand how it reports the XOA VM as the one containing the vulnerabilities.
]]></description><link>https://xcp-ng.org/forum/topic/11304/patch-for-cve-2025-27466-cve-2025-58142-cve-2025-58143</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11304/patch-for-cve-2025-27466-cve-2025-58142-cve-2025-58143</guid><dc:creator><![CDATA[bjdemon]]></dc:creator><pubDate>Wed, 17 Sep 2025 10:32:49 GMT</pubDate></item><item><title><![CDATA[Permanent USB passthrough for smartcard]]></title><description><![CDATA[Hi,
There is an issue and/or a PR (I don't remember where though) to have a specific extra file to manage user config without overwriting it. Until then, it will be overwritten after updates.
@Team-XAPI-Network could provide the link to the issue (or PR?) and check to make it merged when possible 
]]></description><link>https://xcp-ng.org/forum/topic/11253/permanent-usb-passthrough-for-smartcard</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11253/permanent-usb-passthrough-for-smartcard</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Mon, 08 Sep 2025 11:09:42 GMT</pubDate></item><item><title><![CDATA[Native Ceph RBD SM driver for XCP-ng]]></title><description><![CDATA[New version:
https://github.com/dicode-nl/xcp-ng-ceph-rbd/releases/tag/v20260903
This one includes native Ceph rbd SXM over SMAPIv3!
GitHub updated with the latest commits and changes.
As always, use with caution. I did run a lot of test scenario's but please do test yourself and let me
know your findings!
]]></description><link>https://xcp-ng.org/forum/topic/11233/native-ceph-rbd-sm-driver-for-xcp-ng</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11233/native-ceph-rbd-sm-driver-for-xcp-ng</guid><dc:creator><![CDATA[dicode-nl]]></dc:creator><pubDate>Sun, 31 Aug 2025 20:41:46 GMT</pubDate></item><item><title><![CDATA[Possible to reconnect SR automatically?]]></title><description><![CDATA[@ronan-a Thanks! I've installed the plugin, and configured it. Now to wait until the next power outage. (or until I get time this weekend to test it and annoy my family)
]]></description><link>https://xcp-ng.org/forum/topic/11054/possible-to-reconnect-sr-automatically</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/11054/possible-to-reconnect-sr-automatically</guid><dc:creator><![CDATA[dwhitehead42]]></dc:creator><pubDate>Wed, 09 Jul 2025 00:32:05 GMT</pubDate></item><item><title><![CDATA[Early testable PVH support]]></title><description><![CDATA[@bogikornel As discussed in the thread, pygrub doesn't work.
(It might be fixable, because copying kernel and initrd to dom-0 and directly setting PV-kernel, PV-ramdisk and PV-args works, which is basically what pygrub is supposed to do. But I stopped investigating as pvhgrub is a much better option which acually works.)
You have 3 options

copy kernel and initrd do dom-0 and configure

xe vm-param-set uuid=... domain-type=pvh
xe vm-param-set uuid=... PV-kernel=/dom-0/path/to/kernel
xe vm-param-set uuid=... PV-ramdisk=/dom-0/path/to/initrd
xe vm-param-set uuid=... PV-args="root=... ro console=hvc0 ..."
xe vm-param-clear uuid=... param-name=PV-bootloader

Not a very practical option, just PoC.


use pvh-ovmf, but this requires UEFI-enabled VM (ie. GPT disk layout with EFI partition and some EFI bootloader or kernel directly in EFI with proper config (or as UKI)


use pvhgrub. You need a recent grub2 to build the image for i386-xen_pvh target. Or just get the blob - this one is from Alpine package


curl https://dl-cdn.alpinelinux.org/alpine/edge/main/x86_64/grub-xenhost-2.12-r8.apk | tar -xzf - --strip-components=3 usr/lib/grub-xen/grub-i386-xen_pvh.bin

Save it to dom-0 (e.g. to /var/lib/xcp/guest/grub-i386-xen_pvh.bin) and configure the VM
xe vm-param-set uuid=... domain-type=pvh
xe vm-param-set uuid=... PV-kernel=/var/lib/xcp/guest/grub-i386-xen_pvh.bin
xe vm-param-clear uuid=... param-name=PV-ramdisk
xe vm-param-clear uuid=... param-name=PV-args
xe vm-param-clear uuid=... param-name=PV-bootloader

If the VM has valid grub2 config, it should work. Of course, you need a linux kernel with CONFIG_XEN_PVH enabled.
]]></description><link>https://xcp-ng.org/forum/topic/10862/early-testable-pvh-support</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10862/early-testable-pvh-support</guid><dc:creator><![CDATA[hoh]]></dc:creator><pubDate>Mon, 19 May 2025 15:11:13 GMT</pubDate></item><item><title><![CDATA[SMAPIv3 Zvol odd behavior on XCP-ng pools]]></title><description><![CDATA[Upon further testing, it seems that initiating a rescan of the 0 byte SR fixes the size issue. However, I should not be having to do this but at least it appears to be more easily dealt with than I previously assessed.
]]></description><link>https://xcp-ng.org/forum/topic/10730/smapiv3-zvol-odd-behavior-on-xcp-ng-pools</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10730/smapiv3-zvol-odd-behavior-on-xcp-ng-pools</guid><dc:creator><![CDATA[iFrancisMe]]></dc:creator><pubDate>Wed, 09 Apr 2025 00:05:33 GMT</pubDate></item><item><title><![CDATA[Xen ERMS Patch - Call for performance testing]]></title><description><![CDATA[@TeddyAstie I ran iperf3 tests between two VMs on  Xeon E5-2680v2 and average results were within 2% of each other with the patch being slower. Peak speed was 14.5 vs. 13.7 Gbits/sec.
]]></description><link>https://xcp-ng.org/forum/topic/10726/xen-erms-patch-call-for-performance-testing</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10726/xen-erms-patch-call-for-performance-testing</guid><dc:creator><![CDATA[Andrew]]></dc:creator><pubDate>Tue, 08 Apr 2025 10:10:32 GMT</pubDate></item><item><title><![CDATA[Packer / how to enable VTPM setting ?]]></title><description><![CDATA[@gduperrey Got it, thank you for your assistance, this is super helpful.
]]></description><link>https://xcp-ng.org/forum/topic/10618/packer-how-to-enable-vtpm-setting</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10618/packer-how-to-enable-vtpm-setting</guid><dc:creator><![CDATA[davx8342]]></dc:creator><pubDate>Mon, 17 Mar 2025 13:43:41 GMT</pubDate></item><item><title><![CDATA[xe command line, set notes, tags, resource set?]]></title><description><![CDATA[@olivierlambert Fabulous! This is great news!
]]></description><link>https://xcp-ng.org/forum/topic/10617/xe-command-line-set-notes-tags-resource-set</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10617/xe-command-line-set-notes-tags-resource-set</guid><dc:creator><![CDATA[davx8342]]></dc:creator><pubDate>Mon, 17 Mar 2025 13:36:38 GMT</pubDate></item><item><title><![CDATA[Building the Net Install ISO Documentation?]]></title><description><![CDATA[@LonnieTC Don't try to install XCP-ng as if it's any other Linux OS. It's an appliance, you need to download the XCP-ng ISO directly, install this to your hardware and then setup your management interface (Xen Orchestra). Xen Orchestra is installable to Ubuntu.
]]></description><link>https://xcp-ng.org/forum/topic/10616/building-the-net-install-iso-documentation</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10616/building-the-net-install-iso-documentation</guid><dc:creator><![CDATA[DustinB]]></dc:creator><pubDate>Mon, 17 Mar 2025 08:51:56 GMT</pubDate></item><item><title><![CDATA[[Old thread] XCP-ng Windows PV tools 9.0.9030 Testsign released: now with Rust-based Xen Guest Agent]]></title><description><![CDATA[@dinhngtu Thanks. We plan to migrate all Windows VMs from the Citrix tools down the road and only have a handful of VMs running these so far so will maybe hold off until the next version. Have been running the Linux rust tools for over a year with zero issues.. 
]]></description><link>https://xcp-ng.org/forum/topic/10550/old-thread-xcp-ng-windows-pv-tools-9.0.9030-testsign-released-now-with-rust-based-xen-guest-agent</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10550/old-thread-xcp-ng-windows-pv-tools-9.0.9030-testsign-released-now-with-rust-based-xen-guest-agent</guid><dc:creator><![CDATA[flakpyro]]></dc:creator><pubDate>Thu, 27 Feb 2025 10:42:34 GMT</pubDate></item><item><title><![CDATA[Is the xe utility open source?]]></title><description><![CDATA[xe is a XAPI client, like XO is a XAPI client too. The issue with this, is if you have 1 pool it's OK. If you have many pools, it's a lot better to use XO API.
]]></description><link>https://xcp-ng.org/forum/topic/10516/is-the-xe-utility-open-source</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10516/is-the-xe-utility-open-source</guid><dc:creator><![CDATA[olivierlambert]]></dc:creator><pubDate>Sun, 23 Feb 2025 16:47:49 GMT</pubDate></item><item><title><![CDATA[What OS is XCP-ng 8.3 based on?]]></title><description><![CDATA[Hello everyone,
I absolutely understand the point regarding datacenters. I am using xcp-ng for years in smaller - non datacenter - environments and its great. Therefore I added the nut packages (8.2 and 8.3) and it works like a charm. It's installation is well explained in:
https://xcp-ng.org/forum/topic/4300/performing-automated-shutdown-during-a-power-failure-using-a-usb-ups-with-nut-xcp-ng-8-2/13?_=1742229073030
However, I agree with @Kajetan321 that it would be great if the nut package could be included in the standard "updated" packages repo since its added quite some benefits (imho) for "smaller" IT environments. However, I do not know how much effort it takes to maintain that.
]]></description><link>https://xcp-ng.org/forum/topic/10250/what-os-is-xcp-ng-8-3-based-on</link><guid isPermaLink="true">https://xcp-ng.org/forum/topic/10250/what-os-is-xcp-ng-8-3-based-on</guid><dc:creator><![CDATA[FritzGerald]]></dc:creator><pubDate>Tue, 14 Jan 2025 15:19:24 GMT</pubDate></item></channel></rss>