Subcategories

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

    457 Topics
    3k Posts
    C
    Tested this and it worked; [09:33 xcp-ng-01 ~]# ls /dev/ipmi* /dev/ipmi0 [09:33 xcp-ng-01 ~]# ipmitool sensor CPU Temp | 49.000 | degrees C | ok | na | 5.000 | na | na | 100.000 | na Inlet Temp | 24.000 | degrees C | ok | na | 5.000 | na | na | 50.000 | na System Temp | 27.000 | degrees C | ok | na | 5.000 | na | na | 85.000 | na Peripheral Temp | 35.000 | degrees C | ok | na | 5.000 | na | na | 85.000 | na CPU_VRM0 Temp | 41.000 | degrees C | ok | na | 5.000 | na | na | 100.000 | na CPU_VRM1 Temp | 32.000 | degrees C | ok | na | 5.000 | na | na | 100.000 | na SOC_VRM Temp | 38.000 | degrees C | ok | na | 5.000 | na | na | 100.000 | na VDDIO_VRM Temp | 31.000 | degrees C | ok | na | 5.000 | na | na | 100.000 | na DIMMA~F Temp | 37.000 | degrees C | ok | na | 5.000 | na | na | 85.000 | na DIMMG~L Temp | 38.000 | degrees C | ok | na | 5.000 | na | na | 85.000 | na MB 12V | 11.999 | Volts | ok | 10.151 | 10.319 | na | na | 13.259 | 13.427 MB 5VCC | 5.112 | Volts | ok | 4.482 | 4.482 | na | na | 5.490 | 5.490 MB 3.3VCC | 3.229 | Volts | ok | 2.952 | 2.952 | na
  • ACLs, Self-service, Cloud-init, Load balancing...

    101 Topics
    840 Posts
    olivierlambertO
    That's a very good question, let me ask internally. Ping @pdonias he might know the answer
  • All XO backup features: full and incremental, replication, mirrors...

    479 Topics
    5k Posts
    A
    @florent I updated XO to master 60ba5, and still having the issue. I don't see any errors in the backup log. It just says "isFull": true for the ones stuck on full backups. The XO log just reports: Mar 24 16:26:47 xo1 xo-server[21199]: 2026-03-24T20:26:47.315Z xo:backups:worker INFO starting backup Mar 24 16:26:52 xo1 xo-server[21199]: 2026-03-24T20:26:52.359Z xo:xapi:xapi-disks INFO export through vhd Mar 24 16:26:54 xo1 xo-server[21199]: 2026-03-24T20:26:54.410Z xo:xapi:xapi-disks INFO export through vhd Mar 24 16:29:22 xo1 xo-server[21199]: 2026-03-24T20:29:22.250Z xo:backups:worker INFO backup has ended Note, it reports two export through vhd and does two full backups and one delta.
  • Everything related to Xen Orchestra's REST API

    83 Topics
    624 Posts
    K
    @gduperrey Worked swell, thanks
  • Terraform, Packer or any tool to do IaC

    49 Topics
    463 Posts
    dalemD
    Version 1.4.0 is released: https://codeberg.org/NiXOA/system/releases/tag/v1.4.0 It includes significant changes and improvements, including: dedicated getting started section, migration to valkey, only needing to clone system, and helper scripts. the xen-orchestra-ce nixpkg now references the libvhdi nixpkg, and the core flake now references and pulls from the xen-orchestra-ce repo as an overlay. System (the user input flake) now uses the Core repo as an overlay, reducing the need to clone both locally AND allowing system to pull new updates and releases from core. XO, and libvhdi as needed. The next goal is: Make an xsconsole-like TUI Automate package updates for libvhdi and xen-orchestra-ce using CI/CD pipelines Submit libvhdi and xen-orchestra-ce as official nixpkgs
  • Ubuntu 22 Cloud Init/Config Network & Partition Assistance

    11
    0 Votes
    11 Posts
    13k Views
    L
    Hi there Gsrfan Apologies for the delayed response, I had to shelf this passion project to focus on other work So far managed to get the host, static IP, packages, users & their keys/password etc sorted with the init I was working last on lvm partitions, to grow them and that ended up a bit of a mess I might return to this at a later stage but I found your help and advice invaluable to getting the config to where it is now Thank you so much
  • file restore on large backups ends in print_req_error: I/O error's

    8
    0 Votes
    8 Posts
    2k Views
    T
    @olivierlambert said in file restore on large backups ends in print_req_error: I/O error's: Yes, that sounds the next step to do Something is wrong during the mount phase. Also check you have enough RAM in your XOA. Ok, filesystem checks out - as far as I can see having: Done full restore of VM from the same Delta image. Booted VM, logged in and done 'tar cvf /dev/null *' of the filesystem I'm trying to restore from - which ran to completion without error. I upped the RAM for XOA from default 2GiB to 16GiB and re-tried - and same result. I can try yet more RAM if needs be but would hope 16GiB is more than enough? The console error on XOA is more detailed than my install- so don't know if this helps: blk_update_request: I/O error, dev loop0, sector 8912912 op 0x00:(READ) flags 0x80700 phys_seg 1 prio class 0 Looks to be the same issue, just reported differently. You also (on both systems) get kernel chatter about "tasked blocked" (understandable, as it is).
  • Can't restore VM's from 'read-only' remote?

    3
    0 Votes
    3 Posts
    546 Views
    T
    @olivierlambert said in Can't restore VM's from 'read-only' remote?: A remote (now Backup repository) is meant to write backups into it. If you aren't able to write, then, sure, you can restore but you won't be able to backup anything. Yes, understand that - I'll have to re-test here, but I'm sure when it was 'read-only' - I couldn't restore anything from it, as nothing showed up in XO's "Backup / Restore' list of backups... The remote was mounted on two systems - hence why made R/O for one of them (this was just for testing restores).
  • Shutting down "Protect from accidental shutdown" VMs from command line

    2
    0 Votes
    2 Posts
    3k Views
    B
    @Zevgeny Did you succeed to remove the protection with "xe vm-param-clear"? It didn't worked perfectly for me. Before I use xe vm-param-clear, I have the following: [18:28 xcpng02 ~]# xe vm-param-list uuid=37b7a201-eb45-b7de-5ce4-da25b1c7b547 | grep block blocked-operations (MRW): pause: true; hard_shutdown: true; (unknown operation): true; hard_reboot: true; clean_shutdown: true; suspend: true; clean_reboot: true [18:28 xcpng02 ~]# Now I try to clean: [18:28 xcpng02 ~]# xe vm-param-clear uuid=37b7a201-eb45-b7de-5ce4-da25b1c7b547 param-name=blocked-operations The value given is invalid field: blocked_operation value: (unknown operation) [18:28 xcpng02 ~]# After, "blocked-operations" looks like this: [18:28 xcpng02 ~]# xe vm-param-list uuid=37b7a201-eb45-b7de-5ce4-da25b1c7b547 | grep block blocked-operations (MRW): (unknown operation): true; hard_reboot: true; clean_shutdown: true; suspend: true; clean_reboot: true [18:30 xcpng02 ~]# In the GUI of XOA, the "Protect from accidental shutdown" is removed but not on the command line.
  • 0 Votes
    4 Posts
    639 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
    318 Views
    olivierlambertO
    Question for you @florent
  • Constant refreshing of interface

    15
    1
    0 Votes
    15 Posts
    2k 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
    33k 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
    479 Views
    DanpD
    Not that I am aware of.
  • 0 Votes
    5 Posts
    1k 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
    8k 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
    645 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
    11k 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
    175 Views
    No one has replied
  • SR_SOURCE_SPACE_INSUFFICIENT

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

    3
    0 Votes
    3 Posts
    423 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?