XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      769
      1 Votes
      769 Posts
      925k Views
      acebmxerA
      @mpiton Correct. Sorry yes did have to press rolling pool update after the Finalize. The first host was not connecting to the pool after 2-3 min from reboot. I disabled and renabled the pool got host 1 connected again. waiting for host2 to start it didnt so i then put into maintenance mode and applied the updates and rebooted. [image: Screenshot 2026-11-04 134138.png] rpu-64466023-8ef0-f5de-54ed-57e30eca644b-20261104T163948197Z.ndjson.txt rpu-finalize-64466023-8ef0-f5de-54ed-57e30eca644b-20261104T163942579Z.ndjson.txt https://drive.google.com/drive/folders/1wIBRm-8P5lqSOZmhX1ACWdSFLt3wbAQ9?usp=drive_link - to the other logs.
    • olivierlambertO

      XOSTOR hyperconvergence preview

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      468
      1
      6 Votes
      468 Posts
      1m Views
      dthenotD
      @Maelstrom96 Hello, There is indeed an identified bug with addHost that we are investigating at the moment.
    • M

      Bulk "Disconnect from all hosts" action does not work for selected Storage Repositories

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      3
      0 Votes
      3 Posts
      85 Views
      M
      @poddingue Thanks for looking into this! I checked the bulk "Reconnect to all hosts" action as well, and you're right — it doesn't work either. It only works if I select a single SR, open its page, and use the "Reconnect to all hosts" action from there.
    • B

      Missing vdi which is a base for a delta

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      8
      0 Votes
      8 Posts
      367 Views
      B
      FWIW it seems to be the same VMs and same VDIs each day. I'm doing some additional experimentation and testing.
    • ludalm13L

      Audit plugin: forward audit records to syslog in real time (PR #10460)

      Watching Ignoring Scheduled Pinned Locked Moved Advanced features
      5
      0 Votes
      5 Posts
      446 Views
      ludalm13L
      To add some context on our own use case: our standard xo-server logs already go to syslog through [logs.transport.syslog] and on to our central log server, and that works fine. The problem is that a lot of the useful information only exists in the audit log: who did what, which API calls were made, from which IP. Right now that data stays inside XO and we can't correlate it with the rest of our infrastructure. For us it is also a compliance issue. We are subject to PCI-DSS, and Requirement 10 expects administrative actions to be logged, promptly sent to a central log server and reviewed, ideally with automated tools. XO is where our virtualization admin actions happen, so its audit log is exactly the data an auditor wants to see in the SIEM. Having the audit records go through the existing pipeline, as this PR does, would make life much easier: no polling script, no long-lived admin token, and everything ends up in our SIEM in real time. @Team-XO-Backend, a review would be much appreciated.
    • Z

      Veeam and XO backup CBT. How to avoid conflict?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      7
      0 Votes
      7 Posts
      266 Views
      poddingueP
      @zorro So with purge off, Veeam stayed clean for a few nights, which fits what I saw in the lab test. If I read the docs right, the cost is that XO's reference snapshot keeps its data on the SR again, which you'd notice more on thick-provisioned storage: https://docs.xen-orchestra.com/backups-and-dr/backup-types/incremental_backups#purge-snapshot-data-cbt. Storage hasn't said yet whether purge breaking another tool's chain is expected, so I'd still call this a workaround rather than the answer. If a CBT warning comes back when you add the other VMs, the Veeam task id and the time would probably help them. And keeping both makes sense to me, since Veeam doesn't do the cross-site replication you need XO for.
    • O

      Intel GPU passthrough on windows server 2025

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Hardware
      3
      0 Votes
      3 Posts
      100 Views
      O
      @yannsionneau I don't use Ubuntu, but I have a few linux vm's ranging from Debian 13-14 to RHEL 10 and in all of them the passthrough works fine.