• 0 Votes
    8 Posts
    125 Views
    P
    @Andrew @fagnermoraes Hi, A fix is ongoing here: https://github.com/vatesfr/xen-orchestra/pull/9925 @fagnermoraes can you provide your logs please? pierrebrunet289 opened this pull request in vatesfr/xen-orchestra open fix: move try/catch inside initializations #9925
  • 1 Votes
    4 Posts
    186 Views
    laszlobortelL
    @florent Thanks for your reply! We have started to migrate thousands of VMs, so disk transfer speed is important for us.. We will also do our detailed tests soon with different threads setting and publish it here. I think threads=1 is a good and logical default, but not efficient. Others might complain if you set it to a higher value. Configuration option would be a real good solution.
  • 0 Votes
    9 Posts
    69 Views
    Bastien NolletB
    Hi @Pilow, Can you send the full log of one of your backups that don't display any size? We recently had some changes on backup logs, so we need to make sure it's not just a UI issue. (please send the logs of a regular backup, a delta backup or a replication, and not the log of a metadata backup)
  • 0 Votes
    15 Posts
    550 Views
    K
    Another confirmed data point, with package delta and the specific malformed field. Host: XCP-ng 8.3.0, xapi 26.1 (build 26.1.4), Xen 4.17.6-9. Setup: XO from sources (community). All VDIs vanished from the per-VM Disks tab (XO 5 and XO 6); xe and the SR Disks tab show them fine; VMs run normally. Trigger was the 8.3 host update + reboot this morning — XO build unchanged since May 28, disks visible yesterday. Host update delta (today): all 26.1.3-1.10 → 26.1.4-3.1 (xapi-core, xenopsd, sm-cli, sm-fairlock, xapi-storage-script, vhd-tool, message-switch, etc.), plus sm 3.2.12-17.8 → 17.9 as an independent bump. The malformed field. An affected live OS disk (VM running): is-a-snapshot: false snapshot-of: <populated, points to another VDI> snapshot-time: <populated> A normal base VDI should have an empty snapshot-of. After the update, snapshot-of/snapshot-time are populated on real, non-snapshot base VDIs, and XO filters anything with a non-empty snapshot-of out of the per-VM Disks view — which is the disappearance. The VDI that snapshot-of points to is a legitimate base image in my environment (a heavily-reused Win2022 build template with a large genuine snapshot/clone lineage), so I can't tell from the host side whether the parentage links themselves changed or only the snapshot-of on live VDI labeling did. Either way, the consumer-visible effect is the same. REST confirms: /rest/v0/vms/<uuid>/vdis → []; /rest/v0/vdis/<uuid> → "no such VDI" for the VBD's referenced UUID, while xe vdi-list shows it. Caution for others: since live disks now carry snapshot-like metadata, be careful with Health-dashboard "orphan" cleanup and snapshot deletion on affected VMs until this is understood. Workaround that restored the per-VM Disks view: snapshot → revert → delete-snapshot (tested on a powered-off VM, immediate). Happy to provide more diagnostics. Quick Follow-up: Additional symptom, same root cause: ISO-SR VDIs are also affected. Pre-existing ISOs disappeared from the XO ISO picker (only ISOs uploaded after the patch still show). An affected ISO's vdi-param-list shows: is-a-snapshot: false snapshot-of: 937c3945-... (same anchor UUID as an affected VM disk on a different SR) snapshot-time: 19700101T00:00:00Z (Unix epoch — clearly synthetic) Notably the spurious snapshot-of on both an ISO VDI and an unrelated VM OS disk points to the same anchor UUID, with an epoch timestamp — so this looks like the update is stamping pre-existing VDIs with a bogus snapshot-of rather than any real lineage. VHD chains/GC are clean (GC reports no work).
  • 2 Votes
    15 Posts
    694 Views
    poddingueP
    Honestly, the confusion makes total sense; GitHub does a great job of hiding this stuff. Here's what's going on: those markdown files only exist right now as a proposed change sitting on a branch. That's the whole reason you can only get to them through the pull link, and nowhere else. They become a real, permanent part of the repo the moment you merge them in. And since it's your repo, that merge is yours to do, no special GitHub-fu required. Open the PR page (https://github.com/tobiaskreidl/Citrix-Tobias-Kreidl-Collection/pull/1), scroll down a bit, and click the green Merge pull request button. That's the "commit" step you were asking about. There's one wrinkle worth knowing about, and it's the real reason none of this shows up on your main repo page. Your repository has a couple of branches. Your existing PDFs and the Word doc live on a branch called XenServer-Articles, so I pointed my PR at that same branch to drop the markdown right next to them. But the page GitHub shows when someone visits your repo is a different branch called main, which at the moment only holds a README. So even after you merge, the articles will sit on XenServer-Articles, not on that front page. That's actually been true of your PDFs all along; it's nothing my PR changed. If you'd like the articles to show up on the landing page too, there are two easy ways, and I'm happy to do either one for you. We can change the repo's default branch to XenServer-Articles in Settings > Branches, so that one becomes the front page. Or I open a second small PR copying everything over to main. Just tell me which you'd rather have. So the short version: merge the PR to make the markdown real, then we can decide whether you also want the front page pointing at the articles. No rush at all on that second part. gounthar opened this pull request in tobiaskreidl/Citrix-Tobias-Kreidl-Collection open Add Markdown versions of the three articles (render inline on GitHub) #1
  • 0 Votes
    3 Posts
    64 Views
    psafontP
    @mdm Similar to the name-description parameter, the CLI ignores this parameter. The expected way to use would be to set the field value after the SR has been created. I'll make a work item to change the CLI and warn of ignored parameters so confusion like this doesn't happen
  • XO-Lite back to 0.19

    Solved XO Lite
    11
    1
    0 Votes
    11 Posts
    156 Views
    acebmxerA
    @pdonias confirmed... [image: 1780065202934-screenshot-2026-05-29-103255.png]
  • 0 Votes
    8 Posts
    188 Views
    LucienLassalleL
    @semarie I'll try to investigate to help you. Is it possible to run: stat /etc/xensource/xapi-pool-tls.pem openssl x509 -in /etc/xensource/xapi-pool-tls.pem -noout -text stat /etc/xensource/xapi-ssl.pem openssl x509 -in /etc/xensource/xapi-ssl.pem -noout -text (This file must exist; if not, I'd like the output of cat /etc/stunnel/xapi.conf.) And I'd like the same output for /etc/xensource/xapi-ssl.pem. If the certificate for /etc/xensource/xapi-pool.tls.pem has expired or it's empty, you can run: xe host-refresh-server-certificate host=$(hostname) If the certificate for /etc/xensource/xapi-ssl.pem has expired or it's empty, you can run: xe host-emergency-reset-server-certificate After running one of the two commands above, I recommend to do: xe-toolstack-restart (This should indeed restart the stunnel@xapi.service) I hope this helps.
  • API authentication token permissions

    Solved REST API
    6
    0 Votes
    6 Posts
    439 Views
    MathieuRAM
    Hi @halvor, FYI, ACL V2 / RBAC is now available in the REST API. You can create a privilege that only give you read privilege on your host. You can see the RBAC doc. A dedicated thread is available on the forum thread, please feel free to share your feedback. Thank you.
  • Alternative to XCP-NG Plugin for Veeam Backup & Replication Public BETA

    Unsolved Backup
    7
    0 Votes
    7 Posts
    461 Views
    Z
    I'm waiting for veeam 13.1 release as well. Will move a few things over and test out the native backup in the meantime.
  • 🛰️ XO 6: dedicated thread for all your feedback!

    Pinned Xen Orchestra
    227
    7 Votes
    227 Posts
    43k Views
    N
    Afternoon, my session timed out and I do get the normal login page, but when I login I get this UiAlert Message: [image: 1779994906012-screenshot-from-2026-05-28-12-51-11.png] import{B as e,C as t,St as n,U as r,X as i,_ as a,g as o,h as s,m as c,t as l,x as u,xt as d}from"./_plugin-vue_export-helper-DqPMJZfB.js";import{n as f,t as p}from"./VtsIcon-BoVekVkM.js";import{t as m}from"./use-mapper-M_HHKN3j.js";import{t as h}from"./UiButtonIcon-Df9Z1TJo.js";var g={class:`content`},_={class:`alert typo-body-regular-small`},v={key:0},y=l(t({__name:`UiAlert`,props:{accent:{},close:{type:Boolean}},emits:[`close`],setup(t,{emit:l}){let y=l,b=i(),x=m(()=>t.accent,{info:`status:info-circle`,success:`status:success-circle`,warning:`status:warning-circle`,danger:`status:danger-circle`},`info`);return(i,l)=>(e(),a(`div`,{class:n([d(f)({accent:t.accent}),`ui-alert`])},[c(`div`,g,[u(p,{class:`information-icon`,name:d(x),size:`current`},null,8,[`name`]),c(`div`,_,[c(`div`,null,[r(i.$slots,`default`,{},void 0,!0)]),b.description?(e(),a(`div`,v,[r(i.$slots,`description`,{},void 0,!0)])):o(``,!0)]),t.close?(e(),s(h,{key:0,class:`close-button`,icon:`fa:xmark`,accent:`brand`,size:`small`,onClick:l[0]||=e=>y(`close`)})):o(``,!0)])],2))}}),[[`__scopeId`,`data-v-5b9f5cdd`]]);export{y as t}; ... and after back-paging, I was able to login normally.
  • Disaster Recovery Backup - how to restore?

    Xen Orchestra
    16
    0 Votes
    16 Posts
    5k Views
    olivierlambertO
    It hurts (4y ) but I'm glad we finally managed to get what you needed!! Thanks for posting a comment in here after all this time [image: 1779991585587-21cd8648-f61e-46d9-a52f-4ec55a7b7c8b-image.jpeg]
  • Test results for Dell Poweredge R770 with NVMe drives

    Hardware
    31
    7
    0 Votes
    31 Posts
    5k Views
    Y
    @yllar I'm not sure honestly (I will have to ask the rest of the team), but anyway, even if it were fixed by latest xen package, we still didn't publish a new installer ISO with the fix. Target is still around June for the new ISO. Regards, Yann
  • Backups Fail with ENOENT: no such file or directory

    Backup
    11
    0 Votes
    11 Posts
    537 Views
    J
    @pierrebrunet I inadvertently found more information yesterday. I installed an old e492b commit on a new machine, configured identically to the original, and got a different error but the same effect. The new error is: xcp xo backup Error: read ETIMEDOUT That lead me to this page: https://xcp-ng.org/forum/topic/10799/backup-timeout-error I moved the XO machine onto the same subnet as XCP, leaving the storage behind in a different network. This fixed the issue, at least on commit e492b ... I have not yet tried it on the new release... however I am pretty confident it will be successful. If I'm honest, I think this is a tuning issue between XO and XCP. XO is now mounting an NFS share across this subnet boundary and that mount is not having any sort of performance issue, but for some reason XO times out transferring the same data from dom0? That seems off to me. It's not a probem moving XO to the other subnet, so I've done that, but maybe this deserves a look in the future.
  • VIF via REST API?

    Solved REST API
    9
    0 Votes
    9 Posts
    950 Views
    MathieuRAM
    Hi @jedimarcus, FYI, VIF creation is possible via the REST API POST /rest/v0/vifs
  • Ubuntu 24.04 VMs not reporting IP addresses to XCP-NG 8.2.1

    XCP-ng
    13
    5
    0 Votes
    13 Posts
    4k Views
    olivierlambertO
    Because it works already better than the GO tool from Citrix… There's no urgent fix to do, I personally use it in my production since it's available. It's just less a priority for extra features because it's already ultra stable. Right now, we choose to work in priority on XCP-ng 9.0 than the Rust tools, we can't do everything at once yet.
  • Some dashboard loading issues with v6

    Solved Xen Orchestra
    27
    5
    0 Votes
    27 Posts
    1k Views
    acebmxerA
    @simonp said: @acebmxer Hi, Thanks to your help we were able to identify an issue with Redis that we think is the source of the v6 dashboard loading issue. Could you try and checkout the fix_redis_encryption_issue branch, rebuild xo and restart ? This should solve the 401 issues. Switched back to Master branch and made some changes to my install script. add diagnostics for missing XO 6 web UI build artifacts Plain bash [[ -f ]] fails silently on unreadable paths owned by SERVICE_USER, causing false-positive missing-artifact warnings. Switch all file/dir tests and grep calls to use sudo. SUCCESS] Xen Orchestra built successfully [INFO] Build verification passed: dist — all JS chunks present. [INFO] Build verification passed: dist — all JS chunks present. [INFO] Creating systemd service... [SUCCESS] Systemd service created and enabled [INFO] Configuring sudo for xo-service (mount/umount/findmnt)... [SUCCESS] Sudo configured for xo-service (mount, umount, findmnt) [INFO] Applying security hardening... [INFO] Starting xo-server service... [INFO] Waiting for Xen Orchestra to become ready (up to 60s)... [INFO] Not ready yet (attempt 1/10), retrying in 6s... [SUCCESS] Xen Orchestra is ready (HTTPS on port 443) [SUCCESS] Update completed successfully! [INFO] New commit: 0f29421627c7 v6 Dashboard still loading correctly. Thank you for the fix.
  • XCP-ng Windows PV tools announcements

    Moved News
    88
    0 Votes
    88 Posts
    17k Views
    D
    @abudef An overhaul of the guest agent is coming. We're considering adding some kind of update notifications as part of that overhaul, but it'll take some time to suss out the details. Autoupdating the Xen drivers is potentially disruptive and I'd prefer avoiding outages arising from an update coming at a bad time.
  • 2 Votes
    12 Posts
    840 Views
    Y
    @maximsachs Thanks for getting back to me on this. I think (and hope) that in the mean time we will have released an official new ISO that fixes the issue you are having. So, you will be better off testing the new official ISO rather than this unofficial one I'll try to ping here when the new official ISO is out. Thanks! Regards, Yann
  • 0 Votes
    5 Posts
    353 Views
    MathieuRAM
    Hi, @14wkinnersley We merged the PATCH /vms/:id endpoint onto the master branch