• Slow SR Creation

    Unsolved
    15
    1
    0 Votes
    15 Posts
    1k Views
    I
    @tjkreidl everything looks normal. I also shared SOS report with @goulven I hope I'll get a feedback on slowness.
  • xoa kernel update crash the VM ! linux-image-6.1.0-55

    Unsolved
    4
    2 Votes
    4 Posts
    129 Views
    poddingueP
    Thanks for the heads-up, @Pilow. In case someone finds this later, Debian tracks it as bug #1154101, an ext4 regression in kernel 6.1.192-1, which installs as -55. They marked it fixed in 6.1.192-2 on 16 November. That one installs as linux-image-6.1.0-56-amd64, so it's the -56 in your proxy screenshot. The XOA in my test lab never picked up -55, and apt-cache policy there already offers 6.1.192-2 as the next kernel. I think unattended-upgrades will jump straight to the fixed one, but I haven't watched it do that. If you put the hold in place, you'll want sudo apt-mark unhold linux-image-amd64 once you're on -56. Otherwise, if I understand holds correctly, the box stops getting kernel updates, including the security ones. It might be worth a mention to @Team-XO-Backend too, since XOA installs these kernels on its own.
  • New Tools 9.2.445 update failure

    Unsolved
    5
    1
    0 Votes
    5 Posts
    226 Views
    F
    @dinhngtu I will mention that the package was deployed via windows SCCM deployment tools so that may have also played a part in leaving the old product code behind. After running the above script we were able to deploy 9.2.445 via SCCM without issue and no old product codes were left behind.
  • New 9.2.445 XCP Windows tools Roll Back

    3
    0 Votes
    3 Posts
    239 Views
    B
    Looks like the tools installation had an issue with Windows Update packages, the windows event log started throwing error relating to the cryptsvc service and C:\Windows\System32\catroot2 at the time I ran XenClean before trying to install 9.2445. Rebuilding Catroot resolved the issue and tools installed fine. net stop cryptsvc ren C:\Windows\System32\catroot2 catroot2.old net start cryptsvc Reboot Appears to be isolated to this single VM
  • Disk import not happens

    Unsolved
    5
    0 Votes
    5 Posts
    283 Views
    Tristis OrisT
    error via reverse proxy. Uncaught Error: Body is not a JSON, original message is : <html> <title>500 Internal Server Error</title> <style>html{color-scheme:light dark;}</style> </head> <body> <center><h1>500 Internal Server Error</h1></center> <hr><center>Angie</center> </body> </html> pr index.js:2564 me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 be index.js:4029 be index.js:4029 dr index.js:2531 importDisks index.js:2575 Lodash 2 importDisks index.js:2574 e index.js:113 P index.js:22 i index.js:22 R index.js:22 R index.js:22 import index.js:121 t factory.js:307 o factory.js:331 e action-button.js:93 m action-button.js:10 i action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 v action-button.js:140 componentDidMount action-button.js:147 React 14 componentWillUnmount factory.js:125 f factory.js:31 _dispatch factory.js:158 t factory.js:322 promise callback*t factory.js:313 o factory.js:331 value index.js:206 promise callback*value index.js:174 React 5
  • XO RBAC Granularity?

    Unsolved
    10
    0 Votes
    10 Posts
    420 Views
    julienXOvatesJ
    Thanks @ataxyanetwork I was about to answer the same...! (but was too busy this morning )
  • Auth LDAP Plugin "Could Not Authenticate User"

    Unsolved
    3
    1 Votes
    3 Posts
    177 Views
    coolsport00C
    Hi @poddingue ..yes, I have quite a few 'requests' I need to post in there...I just have yet to do so Thanks!
  • 0 Votes
    4 Posts
    330 Views
    poddingueP
    @mdm thanks for checking Reconnect. If I'm reading the code right, both actions have the same mistake, so one fix should cover both. You already wrote the steps out in your first post, so if you're up for it, an issue on https://github.com/vatesfr/xen-orchestra/issues would put it where the frontend team tracks their work. Their bug form asks for the XO version (or commit if you're on sources) plus your Node and XCP-ng versions, which I don't know for your setup.
  • Unable to update Windows PV driver

    Unsolved
    6
    4
    0 Votes
    6 Posts
    410 Views
    D
    @fred974 Hello, Could you please provide the logs produced by XenClean after its execution? If your VM couldn't boot after XenClean, XenBootFix executed from a recovery environment should get your VM working again. Instructions are available here: https://docs.xcp-ng.org/troubleshooting/windows-pv-tools/#windows-fails-to-boot-hangs-inaccessible_boot_device
  • VDI not showing in XO 5 from Source.

    Unsolved
    59
    2
    0 Votes
    59 Posts
    24k Views
    C
    For some reason, we have the same issue (missing disks / snapshot-of) on our environment. (XO from source commit a5077) This is a major issue for us. We use Terraform to manage our VMs, and the missing VDIs are causing Terraform to fail. As a result, we are currently unable to manage our VMs using Terraform. ➜ dacsvm-db02 git:(main) tofu plan -var-file="dacsvm-db02.tfvars" module.vm.xenorchestra_vm.vm: Refreshing state... [id=e36fcd8a-b88c-42f7-6d61-2aa639f63b4a] Planning failed. OpenTofu encountered an error while generating this plan. ╷ │ Error: Could not find client.VDI with query: {VDIId:cad7d739-35c2-4585-9991-4c2f3fc6531c SrId: NameLabel: NameDescription: Size:0 VBDs:[] Parent: PoolId: Tags:[]} │ │ with module.vm.xenorchestra_vm.vm, │ on ../modules/vm/main.tf line 16, in resource "xenorchestra_vm" "vm": │ 16: resource "xenorchestra_vm" "vm" { │ ╵
  • Change Pool Master does not update connection string in XOA

    Unsolved
    8
    2
    0 Votes
    8 Posts
    2k Views
    poddingueP
    @john.c I've put this on the feedback portal as a feature request, so it doesn't get buried in a thread that started out about pool masters: https://feedback.vates.tech/posts/121/publish-build-date-and-package-manifest-sbom-with-the-xoa-xva-download . As far as I know votes there help the team prioritise, so if you and @Forza want it, that's the place to say so. There's an open PR adding SBOM generation (https://github.com/vatesfr/xen-orchestra/pull/10368), but going by the files it touches it covers XO's own JavaScript dependencies, not the Debian packages in the appliance. I've only looked at the file list, not the code, so happy to be corrected. How often the downloadable XVA gets rebuilt, I still don't know: @Danp said back in 2024 that it isn't rebuilt for every XOA release (https://xcp-ng.org/forum/post/81220), which would fit the 2025.12 tag, but I'd rather not guess beyond that.
  • Internet connectivity - Check XOA failed.

    Solved
    8
    1 Votes
    8 Posts
    693 Views
    Z
    @poddingue said: Thanks for posting the fix. The same thing came up in an older thread, https://xcp-ng.org/forum/topic/9957, where disabling IPv6 also made xoa check go green. @HamiltonWDS explained a likely reason in https://xcp-ng.org/forum/post/87831: Node tries the addresses with a short timeout and can end up on the IPv6 one. Your curl -6 test helps a lot here, because it shows IPv6 doesn't connect at all on that network, so it's more than a slow path. Turning it off in XOA seems reasonable if you don't use IPv6 there; if you do, I'd guess the router side is where it really needs fixing, though I could be wrong (still haven't migrated to IPv6 myself ). Curious whether it sorts out the Cloud Backup too. XOA is using our management network where ipv6 is not needed and not enabled. Looks like our cloud backup finally ran for the first time in while too.[image: cloudbackup.jpg]
  • XO Tasks - backups just pilling up

    Unsolved
    5
    1
    0 Votes
    5 Posts
    514 Views
    poddingueP
    I didn't know, so I went and looked at the code. XO prunes that list in a cleanup step: backup runs are kept for 31 days, and other tasks are kept by count, the newest 1000 (https://github.com/vatesfr/xen-orchestra/blob/b59c8f3d20954aa1d72e92c1e8f2db635d74fcba/@xen-orchestra/mixins/Tasks.mjs#L119-L127). You can change both with tasks.gc.keep and tasks.gc.backupKeepDuration in the xo-server config. As far as I can tell the cleanup runs when xo-server starts, not on a timer, so a long-running XO can collect quite a few before the next restart. My guess for the Cloud Backup entries @acebmxer still sees after 30 days is that they're kept by count rather than by age.
  • Unclear errors

    Unsolved
    4
    1
    0 Votes
    4 Posts
    482 Views
    poddingueP
    I tried it on a lab host (XCP-ng 8.3, xapi 26.1.16): calling VM.pool_migrate on a halted VM gives me your error, VM_BAD_POWER_STATE with running, halted, so the two values are the state XAPI wanted and the one it found. On the XO side, a migration inside the same pool with no SR or network mapping goes straight to VM.pool_migrate without checking the power state first: https://github.com/vatesfr/xen-orchestra/blob/b59c8f3d20954aa1d72e92c1e8f2db635d74fcba/packages/xo-server/src/xapi/index.mjs#L942-L981. So a stopped VM in that batch would give this, which fits what you remember. I haven't tried the batch migrate from the UI itself though, so I don't know if the UI is supposed to filter halted VMs out before that. It's a good concrete example for the feedback post anyway, XO could just say "this VM is halted" instead of passing XAPI's raw code through.
  • HA causes reboot of xcp-ng nodes

    Unsolved
    32
    0 Votes
    32 Posts
    4k Views
    tjkreidlT
    @john.c Indeed, John, and I almost forgot that the backup network on each host was actually on a separate, isolated NIC, and not at all on the VLAN.
  • 0 Votes
    19 Posts
    3k Views
    johnnezeroJ
    @fohdeesha Hi all, I apologize that it's taken a while to get all the issues sorted, fixed and properly verified. I have pushed the corrected version up to my GitHub, and everything seems to be working much better (thanks to the efforts of everyone here)! A big shout out to all of you, as this is exactly how open source is supposed to work! Let me know if there are any other issues that arrise - and Happy Day to one and All!
  • GPU Passthrough

    29
    3
    0 Votes
    29 Posts
    12k Views
    tjkreidlT
    @coolsport00 Sorry about the VMW need for the Cisco product. Sounds like you have a number of constraints, finances being I'm sure one of them! At least you have time on your hands and the means to experiment. You may, als, end up with a number of different platforms to meet your needs. We ran both Sun Microsystems and Red Hat Linux and Microsoft Windows servers, each taking on specific duties. It's far from ideal and probably not very cost-effective, but you do what you have to to get stuff to work.
  • 1 Votes
    5 Posts
    780 Views
    johnnezeroJ
    @poddingue Hey, it's just fun building stuff, even if it ends up in the bit-bucket (as unfotunately that's the destiny of all things anyway). Happy Day
  • update failed - NOT_SUPPORTED_DURING_UPGRADE()

    Unsolved
    2
    0 Votes
    2 Posts
    308 Views
    DanpD
    If you are running XOA, not XO from sources, then we could take a look remotely using the support tunnel. Otherwise, make sure that you have patched and rebooted each pool member.
  • 0 Votes
    6 Posts
    819 Views
    F
    Hi, Thanks for your answers For the second problem, after deletion, it is impossible to have the connection to the xo-server despite the refresh of the XOCE page. In a new firefox tab = same problem I closed and then opened Firefox and xo-server connection = OK Best regards