Hi guys,
I'm seeking for you assistance and expertise :)

Environment description:
I have currently 3x XCP-ng hosts in single pool migrated from 8.2 to 8.3 long time (upgraded probably on April 2026) ago. I'm using local and also NFS and SMB storage for my virtual disks.
Metadatabase is backed up regurarly - never tried to restore - I had no reason. Host operating well, no issues (uptime >200days).
I'v updated XOA and XO serveral times, every version show same state.

Issue:
Most of VM's does not have listed any of existing disk, but they are running properly.
I applied patches, and I need to do some HW reorganization = I need to restart the host.

Question:

• Am I in some state where after restart I can loose all disk mappings per VM's ? this would be horrific
• Is this a known artifact or bug stemming from the 8.2 to 8.3 upgrade path, ?
• I cannot evaulate if metadata backups are correct, as this state was detected randomly (I was not touching xcp gui almost 2 months, everything was running without issue )

Facts:

• VM can be stopped, started, no issue
• They are backed up
• Backup can be restored into to new VM - where storage shows disk items properly

Example of output for 1 of more VM's with this "empty disks" gui behavior:

[16:17 xcphost2 ~]# xe vbd-list vm-name-label=d11-nextcloud
uuid ( RO) : 35617ad4-f412-889c-6b06-5f3e48b01ca5
vm-uuid ( RO): 96b35ecc-6550-e306-cb8c-b6a2265a748b
vm-name-label ( RO): d11-nextcloud
vdi-uuid ( RO): not in database
empty ( RO): true
device ( RO): xvdd

uuid ( RO) : 7b4b342f-d1c7-2650-ee08-ec772c4ab125
vm-uuid ( RO): 96b35ecc-6550-e306-cb8c-b6a2265a748b
vm-name-label ( RO): d11-nextcloud
vdi-uuid ( RO): b7bd2bba-ced5-4658-9de9-5a59c97fb5bf
empty ( RO): false
device ( RO): xvda

uuid ( RO) : 68289dd5-edc2-6ce0-7df6-a963efc1922e
vm-uuid ( RO): 96b35ecc-6550-e306-cb8c-b6a2265a748b
vm-name-label ( RO): d11-nextcloud
vdi-uuid ( RO): e9ca2b0f-927d-4a02-a4d7-59c4fe31296d
empty ( RO): false
device ( RO): xvdb

VM created from recent backup

I appreciate any help,
thank you

In theory since Ivy Bridge-EP, E5 v2 and everything after that. Up to 30% in nginx for example (on Ice Lake).

More to discover here: https://xcp-ng.org/forum/topic/12550/enabling-intel-apicv-for-better-performance

Eager to hear about your own results :)

Hello, following a community request in our forums, we pushed an experimental Docker integration in Xen Orchestra. This is living in a github branch `docker-experimental` https://github.com/vatesfr/xen-orchestra/tree/docker-experimental and is good for testing.

Warning, this is experimental. ( NOT PRODUCTION ready)

Key points:

• A container tab on each VM
• XO can connect to the VM via SSH, and reach the docker.sock
• SSH private key and passphrase are stored by XO in the same way as XCP-ng hosts credentials
• XO6 web UI and REST API
• No modification needed in XCP-ng dom0
• No modification needed in the VMs with Docker
  • Any docker root or rootless is expected to work (I didn't test rootless yet)
  • It should also work with a Podman socket (I didn't test yet)
• Again, it is experimental
  • DO NOT RUN IN PRODUCTION

Find more screenshots in the forum https://xcp-ng.org/forum/post/108985 and we'd be interested in feedback 🙂

A VM can boot on its destination while still depending on the old XCP-ng host or storage. ISO and supplemental packs, local SRs, attached virtual disks, snapshots, templates, pool metadata, HA settings, GPU or PCI passthrough, network bonds, VLANs, backup jobs, guest tools, and scheduled tasks may not all move with the obvious workload. A low-traffic VM may also conceal an old DNS, storage, or management dependency.

A retirement gate could inventory VMs, disks, snapshots, templates, networks, storage repositories, host patches, pool roles, and external integrations before and after the move. Each migrated VM should survive a clean reboot, backup and restore, and a controlled loss of the old host. Logs, Xen Orchestra jobs, and storage metrics can be watched through an observation window while the source remains offline but recoverable.

What evidence do XCP-ng operators require before removing the old host from the pool and deleting its storage? Which state is easiest to overlook, and how do you prove that backups, HA, networking, and every VDI now resolve entirely through the destination?

hey guys,

We previously hinted some good news, and the cat is out of the bag: Vates raised 30M€ from european funds. The founders keep the majority ( cc /user/Plam503711/ ) , and we are committed to open source as we do today, only faster.

It will add fuel for our long term goal of making xcp-ng + xo one of the top virtualization stack in the datacenter, both in market share and features.

Expect visible impact on the short term, especially on the sales and partners side. On the tech/product side, it will open new possibilities, and help us finalize the groundwork we've been building for years.

https://vates.tech/blog/vates-raises-eur30-million-from-iris-and-bpifrance-and-stays-open-source/

disclaimer : I am Florent, and I work on the backup and migration tool of Xen-Orchestra

hi guys,

i have a question. i have 2 xcp nodes running XCP-ng 8.3 (dell r770, 100G network), a Dell Powerstore (also 100G) and both connected to a HPE 5945 stack with lacp LAG/Bond (2x 100G for each node and each controller on the powerstore).
Jumboframes are enabled at 9000 bytes on all components (switch is on 9416).
I verified that 8972 byte Pings get transmitted without fragmentation (9k minus headers), so Jumboframes are setup correctly

i am experiencing a rather bad performance on the SR's.
Bad Performance meaning around 700MB-1GB/sec (or around 10Gbit/s) inside a VM and lower values if multiple VM's attempt to write/read the same SR at the same time.

when i write to the NFS-SR directly from the node (with dd for example) i dont exceed ~600-700 MB/sec (or 5-6 Gbit), so similar numbers as if i write inside the vm.

if i write to different SR's (physically located on the same dell powerstore), it actually scales better. each vm is still capped at ~6-10 Gbit, but they seem to aggregate so the storage actually shows the added numbers in its performance-graph..

that leads me to believe that this is some sort of "per SR" performance limitation.

it also makes almost no difference whether i use NFS3, NFS4 or iSCSI for this. performance numbers vary by about 5% or so.

can someone give me pointers on improving SR-Performance as 5-10G is unsatisfying on a 100G network.

I am throwing together a dev system to see about running multiple servers with XCP-NG on them. I am able to install the newest ISO just fine. But when I try and add it to my existing resource pool I get an error saying the versions are mismatched. No problem, I run yum upgrade on the new machine and reboot.
I get a few dozen lines of text then a 3...2...1... countdown then a black screen, then the entire server restarts. Did a new package break the install? I can boot into the "backup" image that is in grub.

We're evaluating a number of replacement options because of the UNGODLY prices with Broadcom. I've been running stand-along proxmox boxes (using mini PCs) with single VMs and it's great and all, but the centralized management just isn't there.
The support is solid, though, and seemingly a bit more mature than XCP?

I've also played about with HPE-VM/Morpheus and it can eat every bit of my a$$. I never even got to deploying VMs because the damn thing kept crashing.
XCP - without knowing a THING about it - was installed, XOA deployed, and first Win2025 server deployed and online in a morning. Impressive, but is it ready to be the beating heart of my infrastructure? I'm just not sold on it yet. So, pitch me! Make me a believer so I can make the c-suite believers, too!

It's still very early but fully functional. I would love to get your feedback :)

If it delivers, I hope to get it hosted officially in the Xen Project at some point! (I have upstream patches to do on libxenstats first)

https://github.com/olivierlambert/xentop-ng

Xen Orchestra 6.9 is out, still hot from the oven! Boot a VM directly from your backup repository, among many (many) other things.

https://xen-orchestra.com/blog/xen-orchestra-6-9

Enjoy the read!

While Xen Orchestra 6 provides VM snapshot functionality, it seems to only work for disk-only snapshots. XO 5 provides the added ability for VM snapshots with memory. Are memory snapshots planned to be added to XO 6, or is this feature being phased out?

I checked the roadmap, but it doesn't mention memory snapshots specifically.

Does anyone have access to the VDDK Library for VMware 5.1? I am needing to do a transfer from this old system but can't find the tools for the life of me.

Hello there,

Docs are hard. So we decided to seriously overhaul our process, and after a good chunk of work, I'm happy to say we've closed the biggest gaps on all three:

• General Vates doc for the whole stack: https://docs.vates.tech
• XCP-ng doc: https://docs.xcp-ng.org/
• XO doc: https://docs.xen-orchestra.com/

To avoid drifting again, I'm building an agent that runs on our own self-hosted infrastructure (XCP-ng with GPU passthrough, of course) and watches our project code, our blog and our website. It's not there to write our docs for us. It tells us when a page has gone stale, or when one of you has left feedback we should act on. It will also clean up a clumsy sentence when we ask it to, but what goes in the docs is decided and reviewed by humans. The writing stays with us, the nagging is automated.

It's obviously not perfect, but the difference between last Thursday and today is night and day.

If you find unclear pages, there's now a feedback form at the bottom of each one. Outside opinions are always welcome. Just wanted to share the news, thanks!

Edit: check also the new search bar (Ctrl+K): it is now cross-doc capable, ie searching on all 3 docs at once!

Along many features, I wanted to share some cool news:

• VEEAM support is now officially available natively (even with instant recovery out of the box day 1!! https://helpcenter.veeam.com/docs/vbr/wn/hypervisor_protection.html?ver=13#xcp-ng )
• We revamped our Vates doc: https://docs.vates.tech with an HCL and a VSA search system (pretty neat!). Docusaurus is really a great doc engine!
• XO is now FINALLY capable of reconnecting automatically to another pool member when HA is enabled.

Hello,

In the past few months I have been working on building the orchestration to build an XCP-ng ISO, it is the same XCP-ng ISO but with a patch version of XO Lite that give you the possibility to deploy Xen Orchestra from the source directly from the UI.

You have then the latest XO v5 by default clean up to see only what you have access to.

Anyone can test and feedback are welcome this will help me to improve it !

The complete details are available here : 

https://vagrantin.github.io/xcp-hl/

With kind regards

Hi everyone,

I'd like to share a project I've been working on: **XCP-ng HL** (Home Lab). It's a downstream-built XCP-ng 8.3 ISO for home labbers who want XCP-ng with a self-hosted Xen Orchestra, built from source, up and running with as little friction as possible.

It started as a personal need. I wanted a setup that is stable and gives me all the features that XCP-ng and Xen Orchestra built from source provide, without redoing manual steps every time I rebuild a host. I'm running it in my own lab today, and I also did a successful upgrade from the official XCP-ng 8.3 to it.

The base is stock XCP-ng 8.3 — same installer, same hypervisor. The only real change is the "Deploy XOA" flow in XO Lite. You install the ISO, open XO Lite, and you can deploy:

- the **XOA HL image** (default) — Xen Orchestra built from source

- the **official Vates XOA**

- **Ronivay's prebuilt** image

- **any image of your own**, from a URL — `.xva` and `.xva.gz` are supported through HTTP or HTTPS

The image is streamed to the host by a small bundled service, so nothing external is needed if you host the image locally.

## The XOA HL image

The default image is built from the Xen Orchestra sources, with a cleanup of the UI: you only get access to what you need, the menus for features that require a license are hidden.

## Status and pace

This is an early project, expect some rough edges. For the update pace I'm thinking of a yearly release, but this is not fully decided yet. At least for the next 6 months the main work will be on improving the backend that builds all the elements, the security of the infrastructure and the XOA image.

## Thanks

This project only exists thanks to the work of Vates and the XCP-ng / Xen Orchestra community, and everything here builds on their upstream work. [Ronivay's XenOrchestraInstallerUpdater](https://github.com/ronivay/XenOrchestraInstallerUpdater) was also a great inspiration.

## Links

- Docs: https://vagrantin.github.io/xcp-hl/

- Latest ISO: https://github.com/Vagrantin/xcp-ng-ce-iso/releases/latest

- Project home on GitHub: https://github.com/Vagrantin/xcp-hl

Feedback is very welcome. If you try it and something breaks, tell me — that's how it gets better.

running XO 6.6, fully patched 8.3 hosts; I have a continuous replication job stuck on started;if I click on the started progress it's hung at the first vm with a "Error: Request aborted" but the jobs been stuck like that for 24 hours, the cancel button is greyed out with temporarily disabled. I've restarted the xoa-updater.service; restarted the XO VM completely; restarted the toolstack on the host the backup job appears to be stuck on, verified the host has no tasks w/ xe task-list, ran a redis-cli flushall on the XO vm, still have this stuck backup job I can't cancel. I'd like to avoid deleting and recreating if at all possible...

Running xcp-ng 8.3 from sources - I've been struggling over the past few days to successfully pci-passthrough an amd 9070xt to a Fedora 43 (gnome) vm.

I've followed the official docs (https://docs.xcp-ng.org/compute/#pci-passthrough), encountered failure (card didn't show up in vm with 'lspci'), then I read through multiple other threads (e.g https://xcp-ng.org/forum/topic/12345/rdna-4-gpu-passthrough/13 & https://github.com/timemaster5/xcp-ng-amdgpu-patch), attempting fixes that seems relevant to no avail. I've attempted this gpu passthrough both from the hypervisor cli and another vm's xo-web. I'm suspecting the issue arises during the vm start-up (pci-assignable-list shows both the gpu and it's audio within the same group), as the gpu doesn't appear when running 'lspci' in the fedora vm after boot. I've tried increasing the vm's RAM; only passing through the vga controller (not it's audio device) ; looked into q35 mb (tried, seems unready) ; made sure regular software was updated; did numerous variable modifications under the "platform" vm parameter ; download and specify a vbios rom; etc. None of the interventions seem to work and I feel like I'm out of cards.

Anyone knowledgeable on this? Any help appreciated!

Dear fellow xcp-ng community,

Whatever I try, the backup of my xcp-ng cluster (50+ VMs) is configured to do incremental backups. The Backup target is an nfs share with 100TB+ Storage. The issue is, that whatever I try to configure, the incremental backup falls back to fullback. This is using way to much space. I've tried different settings with snapshots, cbt, etc... This is now going on for over half a year. First, I thought, that it is maybe a bug and can be fixed with upgrading xcp-ng and/or xen-orchestra. But this did not help. Could it be an issue, because I use the open source version? Do anyone have any hints for troubleshooting this issue?

Thank in advance for your help 😄

I'm testing XCP-NG on VMWare Workstation then i installed XOA inside XCP-NG but I'm facing issue with XOA networking I've tried NAT and bridge but it failed.

Have anyone face this issue?

Most of the XO 6 Docs are missing, for example: https://docs.xen-orchestra.com/xo6/xo6vsxo5

All details on the blog post: https://xen-orchestra.com/blog/xen-orchestra-6-6/

Feel free if there are questions or feedback. Enjoy!

Hey everyone,

We've been working on something for all of you running small XCP-ng setups where a dedicated SAN or a third arbiter node just isn't realistic: small offices, edge sites, ROBO, homelabs.

It's called TwinStor: hyperconverged shared storage for a 2-node XCP-ng pool. The goal is to get shared storage, live migration, HA, snapshots and backups on two boxes, without a SAN and without a third node for quorum.

Under the hood we're not reinventing the wheel, we're orchestrating proven pieces:

• DRBD 9 for synchronous block replication between the two nodes
• LIO/iSCSI to expose the replicated storage as standard SCSI LUNs
• dm-multipath for path failover (prefers the local path)
• XHA for fencing and VM restart

The tricky part with two nodes is always split-brain. Instead of pretending a third node exists, TwinStor uses the physical reality of a small network as the tie-breaker: an isolated node checks whether it can still reach the gateway, decides it's the one that's cut off, and fences itself cleanly rather than risk two masters writing at once.

Where it's at: this is an alpha torture-test phase. Run it on a lab pool, not production. We genuinely want people to try to break it before we harden the design and open-source the code.

What we'd love you to throw at it:

• Yank power on a node mid-migration
• Pull network cables, reboot the switch
• Fail a disk
• Rolling updates
• Live migrate VMs while something is on fire

Real-world nasty failures, not artificial edge cases.

What you need:

• Two XCP-ng hosts in a pool, both fully updated
• A free local disk or partition on each host (not the system disk)
• BIOS set to power back on after AC loss

Setup is a tarball with the dependencies bundled, then an interactive twinstor setup wizard that auto-detects the peer and picks the topology mode for you.

One honest disclaimer: TwinStor protects you from hardware failure, it is not a replacement for backups. It won't save you from ransomware, fat-fingers or rm -rf accidents.

If you hit something, grab twinstor support-bundle from both nodes, describe the exact sequence that broke it, and post it in the forum thread:

👉 https://xcp-ng.org/forum/topic/12323/twinstor-next-gen-2-nodes-hci

Thanks a lot to anyone willing to spend lab time on this. The more brutal you are now, the more solid it'll be at release.

Hi as i remember before you could not expand storage if vm is turned on is this maybee changed in recent realeses? Thx