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

    Backup fails with "Body Timeout Error", "all targets have failed, step: writer.run()"

    Unsolved Backup
    94
    0 Votes
    94 Posts
    10k Views
    J
    @MajorP93 Ok. Thanks!
  • stormiS

    XCP-ng 8.3 updates announcements and testing

    Pinned News
    653
    1 Votes
    653 Posts
    517k Views
    A
    @gduperrey Rolling pool update worked with released production patches.
  • acebmxerA

    Veeam for Xen Orchestra has been release today 13.1

    Backup
    25
    0 Votes
    25 Posts
    1k Views
    acebmxerA
    So I ended up going with the Windows B&R as i could net setup the windows mount server when setting up the repo for the backups. It would setup the linux one but not the windows one. This was with using the veeam console from a windows client. So i ended up with the Windows one. Now after a few backups i am see this warning / error.... 8/5/2026 5:34:50 PM Warning : Failed to use CBT: [Task e75c4247-2ee1-7b51-088c-b970ace60f3d (Async.VDI.list_changed_blocks) failed: . SR_BACKEND_FAILURE_460. . Failed to calculate changed blocks for given VDIs. [opterr=Source and target VDI are unrelated] First i thought it was because i maped the new job to older backups from Beta v1. So i purged all old backups and started fresh. The full backups were successful. Now on first delta 4 out of 7 vms have that warrning. This a Veeam issue or xcp-ng?
  • J

    xcp-ng server crashed/rebooted due to issues with drbd/linstor?

    Unsolved XOSTOR
    30
    0 Votes
    30 Posts
    3k Views
    J
    All hosts are restarted with 9.2.18 loaded now. Will see what happens next. [15:56 ovbh-pprod-xen05 ~]# drbdadm --version DRBDADM_BUILDTAG=GIT-hash:\ 71c8bcff6ea77a022b272a7eba649a774251bac4\ build\ by\ @buildsystem\,\ 2025-11-03\ 10:21:36 DRBDADM_API_VERSION=2 DRBD_KERNEL_VERSION_CODE=0x090212 DRBD_KERNEL_VERSION=9.2.18 DRBDADM_VERSION_CODE=0x092100 DRBDADM_VERSION=9.33.0
  • J

    [PACKER] soucis avec cd_files

    Unsolved French (Français)
    18
    1 Votes
    18 Posts
    667 Views
    AtaxyaNetworkA
    Pour l'ISO montée deux fois : My bad, j'ai ajouter un truc en trop sur mon précédent fix. Une PR est en cours pour corriger ça. Pour le problème principal : J'ai identifié la cause, mais je n'ai pas encore de solution. Sans les drivers Xen (non initialisés avant l'installation), une VM est limitée à 4 périphériques. La séquence de boot ne peut donc pas détecter le second disque contenant le fichier Kickstart (ks). Côté Packer, on semble être bloqués par cette contrainte XCP-ng. Les seules alternatives actuelles seraient de se limiter à : 2 disques + 2 CD ou 3 disques + 1 CD + HTTP (Note : L'installation manuelle fonctionne car l'installateur démarre directement, avec le driver xen_blkfront, alors qu'avec Packer, l'injection de notre fichier interrompt le flux de démarrage classique). Je vais fouiller encore un peu, mais sans certitude d'un contournement possible. (et je regarde pour ajouter le CDlabel)
  • J

    PCIe Pass-through lanes and lane performance

    Unsolved Compute
    44
    0 Votes
    44 Posts
    5k Views
    pandusenP
    @andriy.sultanov @andriy.sultanov said: @pandusen As Teddy said above, you can't passthrough a PCI bridge, so there's no PCI devices xapi shouldn't omit here. I am not trying to pass through the bridge only the end points. The Intel arc's have 2 end points: The GPU and the Sound device. "xe pci-list" only reveals the GPU, not the sound device. (this works for nvidia and AMD) But "going the xen-cmdline way" shouldn't break anything, that's what xe pci-disable-dom0-access does behind the scenes. What issues did you see? Which steps did you follow? the sound device is available in the lspci list and can be passed through using CLI. But doing so, (using CLI for passtrough) undoes everything done using xe or the passthrough gui in XO. and results in this: https://xcp-ng.org/forum/topic/10609/xcp-ng-8.3-pci-passthrough-issue so yes, its does break something.
  • acebmxerA

    Unable to fetch latest master commit.

    Solved Xen Orchestra
    17
    1
    1 Votes
    17 Posts
    1k Views
    TS79T
    @acebmxer all good and thank you again for sharing your discovery on the forums
  • D

    CR - Cannot start copy because suspended

    Unsolved Backup
    17
    0 Votes
    17 Posts
    843 Views
    poddingueP
    Good news that it sorted itself out. Both changes went in at once and the next run came back clean on the ADDS VMs too, so I don't think there's anything left to pin down here, and I'd rather say that than invent an explanation after the fact. Your question about the snapshot modes was the useful thing to come out of this thread. I went looking, they genuinely aren't documented anywhere, and that's written up on our side now If the fall back to a full ever comes back on the ADDS VMs specifically, that would deserve its own thread with the SMlog output @tjkreidl asked for, since nobody got to look at that part.
  • D

    XCP-ng Windows PV tools announcements

    Moved News
    104
    0 Votes
    104 Posts
    32k Views
    J
    @dinhngtu When creating GPOs if you have an non-policy setting for all users in the settings area for the agent config. The policy based registry settings can go into “Software\Policies”, for the appropriate HKEY and keys. In which case the policy based registry entries supersede the non-policy ones, when considering also the HKLM vs HKU and HKCU cascade. Also a disabling of user configuration of the managed setting(s) along with display of a message like “At least some of these settings are managed by the organisation”.
  • P

    " can't compute delta" & "can't connect through NBD, fall back to stream export" after 2026-07-28

    Unsolved Backup
    14
    1
    0 Votes
    14 Posts
    501 Views
    P
    @olivierlambert Happy to hear that they are providing results to be looked at. If there is anything else I can provide, please don't hesitate to ask. And I'll do my very best to be helpfull
  • T

    XEN7 -> XCP83 VM migration

    Solved Migrate to XCP-ng
    14
    0 Votes
    14 Posts
    450 Views
    olivierlambertO
    Excellent! It's really cool to see how XO Backup and Replication can help you to migrate easily
  • msupportM

    Veeam 13.1 Rocky9 Linux Appliance: Potential Data Loss with CBT and Workers with Expired Tokens

    Unsolved Backup
    10
    2 Votes
    10 Posts
    498 Views
    acebmxerA
    @msupport - Looks like veeam is still working with your on your issues. While veeam has pushed me off to vates / xen. @poddingue - Any updates from Vates about these issues? Is it possible the least patches just pushed might help with either mine or @msupport's issue?
  • D

    Smart Reboot blocked in XO, and no Rolling Pool Update

    Unsolved XCP-ng
    9
    0 Votes
    9 Posts
    277 Views
    D
    @poddingue said: What I can't tell you is what set that particular combination on your VM in the first place. Does it ring a bell? I have no Idea. I had it on "Protect from accidental shutdown" but turned that off again, later. Doing this again (on, off) helped, as you said. Thank you so much!
  • acebmxerA

    Deploy VM via cloud-init config

    Solved Xen Orchestra
    9
    1
    0 Votes
    9 Posts
    362 Views
    MathieuRAM
    @acebmxer Thank you for your quick feedback.
  • D

    Ubuntu cloud images on XCP-ng 8.3 UEFI: ~15s per secondary vCPU at boot, caused by console=ttyS0

    Unsolved Compute uefi cloud-init slow-boot ubuntu
    8
    0 Votes
    8 Posts
    111 Views
    D
    @poddingue Thanks for running the -31 numbers — good to have it confirmed that the ttyS0 removal stays worth ~3-4s even with the clock fixed. Agreed on not rushing -proposed to production; we'll pick up -31 when it promotes and keep the cloud-init tweak permanently.
  • O

    VM autostart stopped working

    Unsolved XCP-ng
    8
    0 Votes
    8 Posts
    345 Views
    O
    @poddingue Thank you for the analysis. I'd give you a rep if I could
  • K

    Intermittent Xen blkfront I/O stalls: all guest tags busy while tapdisk reports zero outstanding requests

    Unsolved Compute
    10
    0 Votes
    10 Posts
    653 Views
    A
    Hello @mike.potapov , on n_reqs=32 and n_reqs_free=32, I think you're watching td_blktap_t structure. This structure is only used if the pvdriver are not install in the VM, so it's normal this ring is not used. You should watch struct td_xenblkif that is the ring use normally and that must contains 256 requests on max_order=3. The tapdisk will wakeup periodically, you could put a breakpoint on tapdisk_xenio_ctx_ring_event to confirm that the ring is check periodically. You can investigate td_xenblkif here. Ultimatly, you can try to send a notification from the tapdisk under gdb to the linux kernel with call (int)xenevtchn_notify(blkif->ctx->xce_handle, blkif->port); to see if it unlock something on the guest side. It it's the case it will confirm a notification was lost. If not you will get a message about spurious interrupt in the dmesg of the guest kernel.
  • M

    PCIe Passthrough of Radeon iGPU fails

    Unsolved Hardware
    13
    0 Votes
    13 Posts
    1k Views
    S
    @yannsionneau , may this link helps if you not anyway know it https://medium.com/@timemaster5/getting-amd-phoenix-igpu-passthrough-working-on-xen-xcp-ng-8856593f9c0d I will give it a try this weekend
  • F

    is Xo Proxy available in community version

    Unsolved Xen Orchestra
    13
    0 Votes
    13 Posts
    3k Views
    B
    @poddingue Fistst of all I appreciate your answer and your position. The thing is that, even though the proxy code itself is opensource, the functionality of the plugin is basicaly behind a paywall. We are not talking about support. Actual functioning of the plugin after compiling from sources depends on license availability and there is no option to select no support or something along the lines "I built it myself from sources". Without patching the code even though the proxy is otherwise functional the backups won't work because of missing license. Hopefully the powers that can will provide an acceptable albeit community supported way to use the proxy cleanly, without touching license checks. Best regards!
  • olivierlambertO

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

    Pinned Xen Orchestra
    249
    7 Votes
    249 Posts
    101k Views
    poddingueP
    Depends which one you mean, because there are two different problems tangled together in this stretch of the thread and they have opposite answers. If you mean @escape222's report at #177, where a VM cloned from XO 6 sits at the TianoCore screen for a couple of minutes, then yes, that was an XO bug and it is fixed. PR #9867, merged 26 May, shipped in XO 6.5.0 on 28 May. The boot order was being rewritten whenever no new disk needed provisioning, so an HVM VM created from a template that already had a disk got network pushed to the front whether or not anyone asked for a network install, and the VM burned the PXE timeout before falling through to the disk. It now follows the install method only. Since you are on sources, anything past 6.5.0 has it. If you mean the slow UEFI boot @MajorP93 described at #182, with the installing Xen timer and spinlock lines, that one is not an XO bug and no XO patch will touch it. It is a regression in the Linux guest kernel introduced in 6.12.5. The cost lands per secondary vCPU, so the wider the VM, the worse it looks. There is a separate thread with the per-vCPU numbers: Ubuntu cloud images on XCP-ng 8.3 UEFI. Worth noting its title blames console=ttyS0, which we now think amplifies the same bug rather than being a second one. I measured that one here this week on a single host, changing only the guest kernel between runs and leaving everything else alone. Ubuntu 7.0.0-30 came in at 50 and 59 seconds across two runs. 7.0.0-31 came in at 0.4. Wall clock reboot to sshd went from 78 seconds to 31. The awkward part is the timing. The upstream fix is f24df84cbe05, in stable 6.12.97 and later, 6.18.y, 7.1.4 and later, and 7.2, but no default channel carries it yet. I re-checked the archives this evening: Debian trixie still ships 6.12.94-1, with 6.12.100-1 sitting in proposed-updates for the next point release, and Ubuntu 26.04 still ships 7.0.0-30 in updates, published today, while 7.0.0-31 has been in proposed since 10 August. Rocky and el10 I could not confirm either way. So keep whatever workaround you are on until a named version lands for your distro. There is arguably a third one at #183, where @Greg_E had Debian 13 and Windows Server 2022 refusing to boot at all when created through XO-lite with UEFI. As far as I know nobody has retested that since. If it is the kernel one you are hitting, this says which version you are waiting for: uname -r dmesg -T | grep -iE "installing Xen timer|spinlock event"