1. Home
  2. Popular
Log in to post
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    735
    1 Votes
    735 Posts
    878k Views
    L
    New packages in xcp-ng-testing for the next XCP-ng 8.3 LTS maintenance update This is a follow-up of the the previous post and addresses the issue reported by our testers. First of all, a huge thanks to all testers who allowed us to catch this backup issue early: @acebmxer, @jr-m4, @bufanda, @flakpyro, @Andrew. We decided to revert the change that improves the performance of xapi-nbd since it caused the backup issue. This change will be reworked and refined, then presented to you again in a future update, without this issue. While investigating, we also found a bug in blktap: in rare cases, the process handling a VM disk (tapdisk) could crash during a backup and leave the disk impossible to detach. The new blktap version fixes it. Versions blktap: 3.55.5-12.2.xcpng8.3 -> blktap-3.55.5-12.3.xcpng8.3 xapi: 26.1.21-1.1.xcpng8.3 -> 26.1.21-1.2.xcpng8.3 Test on XCP-ng 8.3 yum clean metadata --enablerepo=xcp-ng-testing,xcp-ng-candidates yum update --enablerepo=xcp-ng-testing,xcp-ng-candidates reboot If you reverted the previous candidates with yum history undo, update normally with the commands above. Note that downgrading is not recommended. If you disabled NBD in your backup jobs as a workaround, please enable it again after the update. The usual update rules apply: pool coordinator first, etc. What to test If you have already carried out the initial updates and performed the tests mentioned in our previous post, please confirm that the XO backups are now back to a working state. If you did not run the initial update and have not yet performed any tests, please be sure to review the "what to test" section of the the previous post. Test window before official release of the updates ~7 days
  • G

    random backups failing

    Solved Backup
    13
    0 Votes
    13 Posts
    323 Views
    G
    OK, marking this solved... It was the phantom reboots causing issues because the tools were not fully installed, only thing I can't understand is why only 2 out of 3 Windows servers would quit. Any way, got the Xen Tools updated and a couple reboots later, everything is working again. Also I can now report that a bug that was fixed maybe a year ago is confirmed to work in my system. The bug was backing up a Windows VM that had a lot of empty space in the drive (over 250GB free) and turning on compression. It would time out counting zeros because it thought the process wasn't doing work. Both of these VMs are now compressing with zstd, one of them is substantially smaller now, the other only shrunk about 20GB. Because of the way Windows uses the drive, these are all full backups. The differential never seemed to be small because Windows does a lot of changes on the drive (there is a post about this somewhere in here from Olivier).
  • B

    Missing vdi which is a base for a delta

    Unsolved Backup
    6
    0 Votes
    6 Posts
    109 Views
    B
    @acebmxer Of course, sorry. We have XO from sources, currently commit 0be90. I'm not aware of any beta updates? I'm attaching the latest log for one of the jobs. 2026-10-27T06_00_00.022Z - backup NG.json.txt
  • R

    Incremental backup fails on a 3 TB qcow2 disk: value is out of range ... <= 4294967295 in computeVhdBatAndFileSize

    Unsolved Backup
    5
    1 Votes
    5 Posts
    258 Views
    poddingueP
    Good to hear block mode did it. If I'm reading XO's troubleshooting page right, that 5-minute wait is a setting you can raise: httpInactivityTimeout under [xapiOptions] in a file like /etc/xo-server/config.httpInactivityTimeout.toml, then a restart of xo-server (https://docs.xen-orchestra.com/backups-and-dr/backup_troubleshooting#error-http-connection-has-timed-out). That path is the XOA one, and I don't know where the ronivay installer keeps its config, so check that first. The page calls it a workaround and says the slow host is the real thing to look at, which could fit your SMR-disk theory, but I haven't tried anything close to a 3 TB qcow2 delta myself. For the close() error, unless I'm misreading the code, XO closes the source after the failed start and only logs a warning before falling back to a full, so I'd guess it's noise from the timeout and not a second bug. The stuck tapdisks look more like one for @Team-Storage, and I don't know if a keep-alive during the delta computation is planned.
  • A

    Are there any downsides to using CBT when doing backups?

    Unsolved Backup
    10
    0 Votes
    10 Posts
    477 Views
    A
    @poddingue Thank you!
  • D

    XCP-ng 8.3 No Longer Compatible with Older Adaptec RAID Card?

    Unsolved Hardware
    16
    1
    0 Votes
    16 Posts
    3k Views
    D
    @Tristis-Oris said: @DustinB said: 14 year old controller it supported and has a driver. Whats wrong? I can't find that storage adapter on the HCL, were you able to? But the summary I have here is replace the old really old adapter. How reliable can't this card still be after working for so long?
  • T

    9.2.385 snapshot/backup corruption fix: which versions were affected, and does it apply to XenServer VM Tools?

    Unsolved Compute
    8
    1 Votes
    8 Posts
    398 Views
    T
    @dinhngtu Thanks for fixing the note. The IP loss did happen on 9.6.0. On the first boot after I set has-vendor-device=false, the guest still reported tools 9.6.0 build 19 (xenbus 9.1.13.23, xenvif 9.1.15.8, xennet 9.1.8.6), and both static IPs were already gone: the main NIC was on DHCP and the second NIC had a 169.254 address. XenClean and the 9.2.385 install came after that.
  • B

    Native Ceph RBD SM driver for XCP-ng

    Development
    34
    3 Votes
    34 Posts
    9k Views
    dicode-nlD
    @nick.lloyd if there is anything that isn't working just let me know. I do advise the SMAPIv3 solution at that implementation offers the full feature set!
  • D

    OKD on XCP-ng

    Moved Infrastructure as Code xcp-ng okd openshift rocky fedora
    10
    0 Votes
    10 Posts
    609 Views
    D
    For anyone else who steps through this, I've also installed the latest xen-guest-agent with the below process. Repeat for each host in the environment, 1 at a time from your Helper VM. ### ssh into your helper ### oc debug node/fedora-cmp-1/2/3 chroot /host cd /var/tmp curl -LO https://gitlab.com/xen-project/xen-guest-agent/-/jobs/6041686376/artifacts/raw/RPMS/x86_64/xen-guest-agent-0.4.0-0.fc37.x86_64.rpm sudo rpm-ostree install /var/tmp/xen-guest-agent-0.4.0-0.fc37.x86_64.rpm mkdir /var/tmp/xga && cd /var/tmp/xga rpm2cpio ../xen-guest-agent-0.4.0-0.fc37.x86_64.rpm | cpio -idmv ### From your helper... DRAIN YOUR WORKERS ### oc adm drain fedora-cmp-1/2/3 --ignore-daemonsets --delete-emptydir-data ### log back into fedora-cmp-1/2/3... ### sudo systemctl reboot ### from helper ### oc adm uncordon fedora-cmp-1/2/3 ### login to fedora-cmp-1/2/3 ### chroot /host sudo systemctl enable --now xen-guest-agent And then from XO this is what your VMs will look like. [image: image.jpeg]
  • I

    Slow SR Creation

    Unsolved Management
    8
    1
    0 Votes
    8 Posts
    723 Views
    tjkreidlT
    @irtaza9 Is this on a single host or a pool? Are all hosts properly time-synchronized? It it related to just one specific storage device or on any, e.g., is the behavior the same on a locally-created SR? Are there any hung tasks causing unnecessary I/O on that storage device?
  • TeddyAstieT

    Enabling Intel APICv for better performance

    Development
    2
    3 Votes
    2 Posts
    346 Views
    T
    Sharing some results. I enabled this on my homelab server, a Dell R630 with Intel Xeon E5-2630 v4 (Broadwell). No adverse impact noticed. The CDM results on Windows is higher than previous runs however, I do not go in depth with I/O benchmarking. (I am using the latest win-pv-drivers on Windows and the rust-based guest tools on Linux) Controller is in HBA mode. VM SR is using SMAPIv3 (ZFS, RAID-0, noop scheduler) [image: R630_XCP-ng_APICv.png] CDM results. Windows Server 2019 4 vCPU/8GB RAM/single VHD: [image: 2610_WIN2019_ZFS.png] I installed ScyllaDB on Alma Linux 10.2 (4 vCPU/8GB RAM & two VHDs, ScyllaDB uses a dedicated drive for data) with io_uring enabled and noop scheduler set on VM. Here are the IOTune results from the ScyllaDB installation: Measuring sequential write bandwidth: 826 MiB/s (deviation 13%) Measuring sequential read bandwidth: 1061 MiB/s (deviation 6%) Measuring random write IOPS: 50791 IOPS (deviation 11%) Measuring random read IOPS: 62977 IOPS (deviation 16%)
  • M

    Support for newer Emulex LPe37xxx amd LPe36xxx Fiber channel adapters on XCP-ng 8.3 - your testing is needed

    Hardware
    5
    2 Votes
    5 Posts
    491 Views
    J
    @MrQ said: @jr-m4 thank you so much for testing this updated driver. Just to make sure, I understand now that you confirm the driver is working as expected and the issues you had were not related to it? Or are there any problems still with this new driver? Many thanks again for spending the time to test and report. Hi Yes. I believe I was chasing a red herring of my own doing. I have not found anything actually problematic with this driver at all.
  • D

    Node.js October 21, 2026 Security Releases

    Xen Orchestra
    2
    0 Votes
    2 Posts
    731 Views
    poddingueP
    Thanks for the heads-up. If you built XO from sources, the docs say to keep Node on the latest LTS (https://docs.xen-orchestra.com/getting-started/install-from-sources#nodejs), so it's worth moving to the patched release on whichever line you run. For XOA, I don't know how fast the appliance picks up a new Node release, but I know something's cooking.
  • C

    Booting Homeassistant (HAOS) Image breaks VM

    Unsolved Compute
    2
    0 Votes
    2 Posts
    111 Views
    poddingueP
    Hello Christof, Swapping the disks between the two VMs shows the problem follows whatever runs inside, not the VM itself. Next I would run xe vm-param-list uuid=<vm-uuid> on the host once with HAOS booted and once with Debian booted, and diff the two outputs. Fields like os-version, PV-drivers-version and networks are reported back by the running OS, so they change with the guest. My guess, and it's only a guess, is that one of them comes back in a shape Commvault's parser doesn't expect: "input string has the wrong format" is what .NET says when it fails to read a number. If you find the field that differs, Commvault support would have something concrete to work with.
  • E

    filters in API requests

    REST API
    2
    0 Votes
    2 Posts
    87 Views
    P
    Hi, This was fixed in Latest. But if you need to stay on Stable, you can open a ticket to have a patch.
  • W

    VDI not showing in XO 5 from Source.

    Unsolved Management
    58
    2
    0 Votes
    58 Posts
    21k Views
    L
    It's a been a while since this thread has been updated, so I figure I should share what I've learned. First: here's a script which reproduces the bug reliably and includes steps to revert: https://gist.github.com/dmeiselman/ecb35ffcb675c38e6eeb14292948c2e3 Don't run this on your production cluster. Here's my understanding of this bug and it's current state: Some operation sets the snapshot_of metadata field of a valid snapshot to NULL (We can do this intentionally by making a VM, taking a snapshot of it, then deleting the parent disk.) If you perform a revert of this invalid snapshot, revert's "Updating the snapshot_of fields" step looks for VDIs whose snapshot_of matches the snapshot's source disk, so it can relink them to the new disk. If the source is NULL, the search becomes "every VDI with NULL", which matches ISOs, base images, ordinary VM disks. Congrats, every real disk and ISO in every SR now looks like a snapshot. Now these disks have a value set for snapshot_of which means XOA hides the VDI in the web UI. The fix is to delete or clone the super-parent, and all of its snapshots. sr_scan will correct the metadata for all the VMs and ISOs and you're back where you started. This happens in line 401 of https://github.com/xapi-project/xen-api/blob/v26.1.19/ocaml/xapi/xapi_vm_snapshot.ml#L389-L408 PR 7290 https://github.com/xapi-project/xen-api/pull/7290 has a fix, which looks like it's coming in xapi v26.1.21. (It's worth reading the Pull Request, as it has a more graceful description of the issue, it really helped me wrap my head around it.)
  • H

    Future Architecture?

    News
    11
    1 Votes
    11 Posts
    730 Views
    G
    The UEFI and possibly SecureBoot requirements on a lot of stuff and going to turn a lot of old systems into garbage. Also going to be an issue when more current stuff gets upgrade from 8.3 in BIOS mode to requiring UEFI for version 9. That's the boat I'm in for production. Alma and openSuse may be a few of the last holdouts allowing v2 and BIOS boot.
  • olivierlambertO

    🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    307
    7 Votes
    307 Posts
    185k Views
    C
    Found another issue testing, or maybe it's known behavior? This is in both v6 and v5 webUI -- if I create a new Linux VM from an Ubuntu 24 Template I created, and I installed xe-guest-utilities (v.7.20.2-0ubuntu1) in the Template, the web UI does not display the IP under the Network tab in v5, nor when clicking the 'eye' in the Networking tab in v6. But, if I install the guest utilities via the guest-iso via the cdrom (v.7.30.0-19_amd64.deb) in XOS, the IP then shows. Is there a different utilties pkg to install in Ubuntu, or just go the cdrom route? The Windows guest agent downloaded from github, after install, shows IP in Network tab for Win VMs. Thanks!