Subcategories

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

    378 Topics
    3k Posts
    olivierlambertO
    Hi, Do you have any error message? What's happening? Anything visible or not?
  • ACLs, Self-service, Cloud-init, Load balancing...

    93 Topics
    783 Posts
    MK.ultraM
    @tmk said in Cloudbase-init on Windows: @jkatz I ran into the same issue when trying to configure a network adapter with cloudbase-init. The documentation says that the MAC address value is optional but in reality it is required. In my case I want Xen Orchestra to choose a unique MAC during deployment, and I since I am deploying from a template, the NIC name is a known value. The fix that ended up working for me was to modify the networkconfig.py file in cloudbase-init so that the NIC name is required and the MAC address is optional. I ended up making some additional changes to allow for the network-config v2 format along with the existing v1 support and some additional logic to aid in setting the dns search domains (I can't recall if this was originally supported or not but I had issues getting it to work with the original networkconfig.py file) This file needs to replace the existing one that is installed in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Lib\site-packages\cloudbaseinit\plugins\common\ directory. To replace it you should make sure that the cloudbase-init service is stopped, then replace the file. Once this file is replaced, delete the pycache folder in the same parent folder as networkconfig.py - this will ensure that python recompiles this file on service start. Start the cloudbase-init service and confirm that you see a new pycache get created. I'm not a python programmer by trade so others may be able to point out areas for improvement but this ended up working for me and I wanted to share in case it could help others needing to deploy new servers without manually specifying a new MAC address. Below is an example network-config v2 format that works with the updated file. version: 2 ethernets: Ethernet 2: dhcp4: false addresses: - 10.20.30.10/24 nameservers: addresses: - 10.20.5.12 - 10.20.5.13 - 10.20.5.14 search: - intranet.domain.org - domain.org - public-domain.org routes: - to: default via: 10.20.30.1 Updated networkconfig.py file: networkconfig.py.txt Thank you for posting! I followed your directions verbatim and I'm still having trouble getting the network config to take. Does it work with Windows Server 2025?
  • All XO backup features: full and incremental, replication, mirrors...

    389 Topics
    4k Posts
    olivierlambertO
    @florent so it's like https://github.com/vatesfr/xen-orchestra/commit/a459015ca91c159123bb682f16237b4371a312a6 might introduced a regression? 0 fbeauchamp committed to vatesfr/xen-orchestra Fix(replication): VDI_NOT_MANAGED error (#8935) from ticket #40151
  • Everything related to Xen Orchestra's REST API

    68 Topics
    529 Posts
    olivierlambertO
    @lsouai-vates we should try to reproduce and if we can, to fix it ASAP. Thanks!
  • Terraform, Packer or any tool to do IaC

    35 Topics
    350 Posts
    J
    @manilx I have proposed to the IaC team of Vates, a MCP Server for Vates VMS. Which can be used by GitHub Copilot or similar, if used when doing IaC etc.
  • [Guide] Recovering from CR with error - no space for coalesce

    4
    7
    0 Votes
    4 Posts
    618 Views
    olivierlambertO
    Hopefully, we'll make things more obvious in terms of "danger zone" in XO 6 UI
  • XO Backup - question on file level restore

    backup file-level lvm
    12
    1
    0 Votes
    12 Posts
    2k Views
    S
    I have opened a ticket to support because file level restore doesn't work anymore after latest update. Best regards Walter
  • Change Email Address for XO Report

    2
    0 Votes
    2 Posts
    401 Views
    DanpD
    Look under the configuration for the backup-reports plugin, which can be found under Settings > Plugins.
  • Existing AD Users Cannot Login to XOCE but New Users Can

    18
    0 Votes
    18 Posts
    2k Views
    K
    @julien-f Hmm, that's a bit disappointing that there isn't much you guys can do to help. No worries, I'll keep testing. My AD environment works fine, since the accounts in question are not locked and are being used daily. The only place they're failing is in XOCE or XOA. It's gotta be something with how the library is handling characters in either the username or the password. I'll keep testing until I can find a repeatable pattern. Thanks to both you and @olivierlambert for the help thus far.
  • how configure aws s3 bucket for xen orchestra remote s3 beta

    9
    0 Votes
    9 Posts
    1k Views
    ontzuevanhussenO
    @kamal8641 AWS S3 remote on xen orchestra works fine in my tests.
  • Can't copy or move VM from host with xen 6.5 to host xcp-ng 8.2

    13
    0 Votes
    13 Posts
    1k Views
    L
    thanks for all advices just moved all services to new vm, that makes topic is closed. for last try i updated xen 6.5 to 7.4 but problem remains
  • How to grant permission to User/ACL to download snapshots of VMs

    3
    0 Votes
    3 Posts
    372 Views
    L
    @olivierlambert Hahaha you got it! Thank you
  • Ubuntu 22 Cloud Init/Config Network & Partition Assistance

    11
    0 Votes
    11 Posts
    10k 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
    1k 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
    357 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
    2k 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
    393 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
    254 Views
    olivierlambertO
    Question for you @florent
  • Constant refreshing of interface

    15
    1
    0 Votes
    15 Posts
    1k 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
    24k 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
    1k 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
    256 Views
    DanpD
    Not that I am aware of.
  • 0 Votes
    5 Posts
    977 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
    1k 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
    6k Views
    florentF
    @sumansaha that is a good news yes, the replication go through the XO VM, the faster the link the better the performances