Subcategories

  • VMs, hosts, pools, networks and all other usual management tasks.

    473 Topics
    4k Posts
    olivierlambertO
    Hi, IP conflict?
  • ACLs, Self-service, Cloud-init, Load balancing...

    104 Topics
    863 Posts
    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.
  • All XO backup features: full and incremental, replication, mirrors...

    511 Topics
    5k Posts
    P
    @itservices Hi, xen-bugtools is in xcp-ng hosts. You can directly get the logs from the hosts if you don't have the command.
  • Everything related to Xen Orchestra's REST API

    86 Topics
    645 Posts
    J
    Hello I'm pulling stats for all VMs to understand CPU usage. We're a bit behind the curve in terms of XO versions, but these questions hopefully are still relevant. If using a granularity of days, the interval is set to 86400 (understandably) but the endTimestamp varies. Running this on June 9th @ ~1740 we get timestamps for both Mon Jun 8 01:00:00 AM BST 2026 and Tues Jun 9 01:00:00 AM BST 2026. Does this average across the day? Why is the timestamp 0100? Why would there be different timestamps between VMs (all are running) and does that mean that the figures are misaligned in the results? These are retrieved via curl and a bash script, a bit hacky, but for clarity the request is: ++ curl -X GET -s -H accept:application/json -b authenticationToken=[[REDACTED]] -o [[REDACTED]] 'https://[[REDACTED]]/rest/v0/vms/[[REDACTED]]/stats?granularity=days' Really keen to know if we can control the start and endtime, as well as provide a manual interval, as well as the aggregation strategy (min, max, average). Are any of these possible? Lastly, is cpuUsage the percentage as per the dashboard, but averaged over all CPUs? Thanks so much in advance. James
  • Terraform, Packer or any tool to do IaC

    51 Topics
    471 Posts
    poddingueP
    The Kubernetes CSI driver for Xen Orchestra just hit v0.4.0, and we want it on more real clusters before it reaches a stable release candidate. If you run Kubernetes on XCP-ng VMs, this is a good time to give it a proper workout. What's new in v0.4.0: Local-storage support Automatic pool-discovery fallback Kubernetes metadata now lives in Xen Orchestra VDI tags instead of the deprecated other_config. That change also drops the old requirement for Xen Orchestra 6.4 or newer, so the driver runs on more deployments now. ️ Read this before you upgrade. v0.4.0 is a breaking change. The Kubernetes metadata moved from other_config to VDI tags, so you must migrate before upgrading from v0.3.0. Do not upgrade in place: follow the v0.3.0 to v0.4.0 migration guide in the release notes, then move to v0.4.0. What helps us most is hearing how it behaves on your own setup: what works, what breaks, which storage backend you use, and which flavour of Kubernetes you run (k3s, full k8s, or something else). Edge cases on real clusters are the ones we don't see in our own testing. Where to report: start right here in this thread. It keeps everything visible to the community and lets others on the same setup jump in. If something turns out to be a reproducible bug, we'll move it to a GitHub issue on the repo so the team can track it to a fix. Release notes and migration guide: https://github.com/vatesfr/xenorchestra-csi-driver/releases/tag/v0.4.0
  • 0 Votes
    4 Posts
    775 Views
    B
    I think this is important. When the issue appears the replicated VM that auto-starts has the [IMPORTING] prefix as in the image below. [image: 1689001402269-130e1c45-ad28-4b6c-a4d7-202b552ab723-image.png]
  • XOCE Warning on build

    2
    0 Votes
    2 Posts
    360 Views
    olivierlambertO
    Question for you @florent
  • Constant refreshing of interface

    15
    1
    0 Votes
    15 Posts
    3k Views
    A
    @pdonias Hi, On Master, as of yesterday, I see this only when I am logged in using an IP address on the URL instead of the hostname. Either way it is SSL with trusted certificate. There are no console errors Browser is Microsoft Edge on Windows No difference in behaviour between incognito mode and normal. Yes I see all the VMs There is an improvement - now if I am creating a new VM only the selected network is reverting back to default when it refreshes, the other things like number of cores and ram is remaining when I set it, whereas previously these also were wiped back to default every 20 seconds or so. Thanks Alex
  • VDI_IO_ERROR(Device I/O errors) when you run scheduled backup

    66
    0 Votes
    66 Posts
    36k Views
    R
    @rauly94 Hello everyone. Anyone can help me on this issue. Now it started happening on 2 vm's instead of 1 vm. It is happening on the backup replication. Error: VDI_IO_ERROR(Device I/O errors)This is a XenServer/XCP-ng error Start: Jul 5, 2023, 09:03:18 AM End: Jul 5, 2023, 09:44:46 AM Duration: 41 minutes Error: VDI_IO_ERROR(Device I/O errors)This is a XenServer/XCP-ng error Start: Jul 5, 2023, 09:03:09 AM End: Jul 5, 2023, 09:45:12 AM Duration: 42 minutes Error: VDI_IO_ERROR(Device I/O errors)This is a XenServer/XCP-ng error Type: delta
  • Deleting all existing Backups

    4
    0 Votes
    4 Posts
    2k Views
    planedropP
    Yeah for doing a fresh start it's easiest to just nuke the backup directory you were using and start over, have done it before and it's quick and easy vs trying to manually remove them all within XOA.
  • Deleting orphaned backups

    4
    0 Votes
    4 Posts
    575 Views
    DanpD
    Not that I am aware of.
  • 0 Votes
    5 Posts
    2k Views
    A
    @ronivay, I resolved my problem with orchestra which did not want to make backup with NFS. Orchestra wrote errors like: Command failed with exit code 1: mount -o -t nfs 192.168.11.53:/backups/xo /run/xo-server/mounts/0e5e9511-8912-48d4-96ad-532979533332 mount: only root can use "--options" option In general, orchestra tried to use mount option "--options" but mount command rejected this option. When I mount my NFS-shares manually everything was ok - mount works, read-write too, umount also. I did simplest process. I removed at all "--options" from mount command. (As far as I understand, *BSD mount will not work without this option but my Ubuntu works). Background: xcp-ng server (centos 8.2) as NFS server ubuntu server 16.04 where orchestra is going to be placed Orchestra installed 10 days ago from sources according to https://xen-orchestra.com/docs/installation.html#from-the-sources I complete followed document before chapter "Installing dependencies". I made yarn Then, before "yarn build", I manually edited file: /opt/xen-orchestra/@xen-orchestra/fs/src/_mount.js at string 68 I replaced await this.#execa('mount', ['-o', options, '-t', type, device, realPath], { with await this.#execa('mount', ['-t', type, device, realPath], { I then proceeded to follow the instructions: yarn build a so on... Now "patched" orchestra fine makes any kind of backup with NFS. At least, I solved this problem. Yet another question appeared as backup works What kind of Backup should I use to make full copy which enough for restoring (Heaven forbid)? I tried simply "Backup". It SUCCESSFULLY (!) created several files with 56 kbytes (no giga, no mega but kilo). I suppose it abnormal. My VM has got 20 Gb of disk space and about one half is already used (ubuntu server, postgres etc). As far as I understand (https://xcp-ng.org/forum/topic/7034/backup-with-local-usb-hdd-attached-sr_operation_not_supported/5?_=1688120707451) my version of xcp-ng (8.2.1) does not support "Snapshots" with local disks. Now I copy imagine of my VM with cron as temporary option but may be there is some more correct backup option?
  • Snapshot failure

    12
    0 Votes
    12 Posts
    2k Views
    S
    @sumansaha Hello Team, The issue has resolved after applying xe-toolstack-restart. Thanks.
  • increase 24 hour timeout-limit on backup/copy

    Solved
    24
    0 Votes
    24 Posts
    9k Views
    florentF
    @sumansaha that is a good news yes, the replication go through the XO VM, the faster the link the better the performances
  • if ACL is not free?

    3
    0 Votes
    3 Posts
    771 Views
    K
    @AtaxyaNetwork Thanks
  • Debian 12 (Bookworm) default template

    3
    0 Votes
    3 Posts
    1k Views
    escape222E
    @olivierlambert Thanks
  • Hosts have disappeared from XO Web UI

    30
    0 Votes
    30 Posts
    13k Views
    D
    @julien-f @julien-f All I have done is let ronivay's script do the builds daily on schedule if there is a new commit on the master branch. His script has not changed. There have been no new patches to the hosts. I don't have an explanation.
  • clone linode to local

    1
    0 Votes
    1 Posts
    231 Views
    No one has replied
  • SR_SOURCE_SPACE_INSUFFICIENT

    Solved
    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    XO saved the day
  • Check User creation Date/time

    3
    0 Votes
    3 Posts
    664 Views
    N
    @Danp Yes but unfortunately before of this incident audit is disabled
  • Move VMs between SRs

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    No problem! Did you manage to do what you need?
  • XOA does not reliably autostart

    Solved
    4
    0 Votes
    4 Posts
    1k Views
    B
    Toggling it back and forth seems to have worked, thanks.
  • OIDC not redirecting back to XO

    22
    0 Votes
    22 Posts
    5k Views
    julien-fJ
    The fix is now merged on master and will be part of the next release.
  • DR - Failback Scenario

    5
    0 Votes
    5 Posts
    880 Views
    H
    That's great, we'll be watching the space.
  • How to restore vm and xo metadata from backups?

    2
    0 Votes
    2 Posts
    2k Views
    GheppyG
    I don't have experience with something like this, but I can do a mini lab with something like this, to test the steps below . What would I do. 0. Do you have metadata backup for XCP-ng? If YES 1.1. I would reinstall the server from scratch, before make a backup with Clonezilla with the boot disk of XCP-ng ; 1.2. I would reconnect iSCSI, without formatting it - reinitialize, only reconnecting (to not delete the data on it); 1.3. I would restore the metadata; 1.4. The result should be all the info about the VM that was on XPC-ng, and hopefully it also attaches the iSCSI disks. If NO 2.2. I would reinstall the server from scratch, before make a backup with Clonezilla with the boot disk of XCP-ng; 2.2. I would reconnect iSCSI, without formatting it - reinitialize, only reconnecting (to not delete the data on it); 2.3. I would redone the VMs from scratch and start attaching the disks to identify which and to which VMs they were attached before; 2.4. The result should be functional VMs In principle, if you have the disks intact, the data is there, you just have to restore the VMs (RAM, CPU, attached the correct disks, etc.) This is the menu for XCP-ng metadata backup, Backup/New. [image: 1686467766517-cf7e9ec4-0d85-4ab6-9a1a-1061cd40a685-image.png] [image: 1686467824225-129ea089-e38b-4cf6-aa04-f7b3020b23a3-image-resized.png]