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

    Master, commit a3139 failing backups

    Backup
    16
    0 Votes
    16 Posts
    171 Views
    A
    @simonp [info] Updating Xen Orchestra from 'cb85e44ae' to 'eed3d72f7' First log is from automatic schedule before latest update. 2026-02-17T18_00_00.012Z - backup NG.txt latest log after update. Backup completed successfully. 2026-02-17T18_22_52.199Z - backup NG.txt
  • DustyArmstrongD

    Detached VM Snapshots after Warm Migration

    Backup
    19
    1
    0 Votes
    19 Posts
    149 Views
    DustyArmstrongD
    @Pilow Time for a drink, I think.
  • olivierlambertO

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

    Pinned Xen Orchestra
    125
    5 Votes
    125 Posts
    9k Views
    J
    @pdonias said in ️ XO 6: dedicated thread for all your feedback!: @jacob.becker We're adding the maintenance icon very soon, thanks for the feedback. Regarding VM vs host in the treeview, do you mean that the icon isn't clear enough? Do you have the same issue with pools? I don't have that many pools, sorry. The icon for each host got lost in a wall of VMs if you have lets say >50 VMs per host. AFAIK the tree-view allways starts fully expanded. Since all VM belonging to any host are on the same depth of the tree you can scroll over a host easy. Another thing are VMs which do not belong to a host - they are shown on the same depth as a host. I personally would color the line for a host, but i know that this not the way most design guidlines agrees with.
  • N

    XCP-NG server crashes/reboots unexpectedly

    Solved Hardware
    27
    0 Votes
    27 Posts
    3k Views
    N
    @magicker Thanks, I was also thinking it would be a good idea to monitor CPU temps just to make sure its nothing related to that. As I have a consumer motherboard I don't have IPMI to monitor. I believe I could install some linux temperature monitoring packages in the xcp-ng host, but I didn't dare to do that yet not wanting to risk breaking anything on the host. Or would you guys say it's in principle fine to install such temp monitoring tool on the host?
  • CyrilleC

    Xen Orchestra Container Storage Interface (CSI) for Kubernetes

    Infrastructure as Code
    12
    4 Votes
    12 Posts
    1k Views
    T
    My validation of this was not successful; I used the Quick Start PoC. Pods eventually went into CrashLoopBackOff after ErrImagePull and ImagePullBackOff. I created a GitHub token with these permissions: public_repo, read:packages. I also used a token with more permissions (although that was futile) however, I figured at least it required the aforementioned ones. I have since uninstalled via the script but captured the following events from the controller and one of the node pods: kgp -nkube-system | grep csi* csi-xenorchestra-controller-748db9b45b-z26h6 1/3 CrashLoopBackOff 31 (2m31s ago) 77m csi-xenorchestra-node-4jw9z 1/3 CrashLoopBackOff 18 (42s ago) 77m csi-xenorchestra-node-7wcld 1/3 CrashLoopBackOff 18 (58s ago) 77m csi-xenorchestra-node-8jrlq 1/3 CrashLoopBackOff 18 (34s ago) 77m csi-xenorchestra-node-hqwjj 1/3 CrashLoopBackOff 18 (50s ago) 77m Pod events: csi-xenorchestra-controller-748db9b45b-z26h6 Normal BackOff 3m48s (x391 over 78m) kubelet Back-off pulling image "ghcr.io/vatesfr/xenorchestra-csi-driver:edge" csi-xenorchestra-node-4jw9z Normal BackOff 14m (x314 over 79m) kubelet Back-off pulling image "ghcr.io/vatesfr/xenorchestra-csi-driver:edge" Warning BackOff 4m21s (x309 over 78m) kubelet Back-off restarting failed container node-driver-registrar in pod csi-xenorchestra-node-4jw9z_kube-system(b533c28b-1f28-488a-a31e-862117461964) I can deploy again and capture more information if needed.