1. Home
  2. Xen Orchestra

Subcategories

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

    459 Topics
    4k Posts
    P
    @wgomes yup thanks for bumping this topic, still having the problem too

  • ACLs, Self-service, Cloud-init, Load balancing...

    102 Topics
    852 Posts
    P
    @dlgroep Thank you, we will take thin/thick token into account and use 'claims' part for other properties.

  • All XO backup features: full and incremental, replication, mirrors...

    489 Topics
    5k Posts
    P
    Re: FILE RESTORE / overlapping loop device exists we still had this annoying probleme where we couldn't FLR our backup, source VM could be Windows or linux, with or without LVM... (see error logs in previous thread, overlapping loop...) latest XOA is installed. on a secondaray XO CE, I mounted the same remote, and NO PROBLEMS AT ALL... soooo I thought my main XOA is probably beaten up somewhere... but that was not it. all remotes on main XOA are attached to a XO PROXY (official, not CE) ! on the XO CE that is in another datacenter, I mounted the S3 remotes directly WITHOUT the proxy use, and it worked. On main XOA, we offload all backup tasks to proxies, so all remotes are attached to a proxy... I duplicated a remote, same conf, but without proxy, so that XOA would do the restore job, not the proxy, and voila, all is working as intended, FLR is okay on main datacenter. TLDR : FLR is not working with proxy attached remotes, if you duplicate the remote without the XO PROXY, all good @florent @bastien-nollet I think there is something to look into. probably a race condition, the XOA and the XO PROXY both try to mount the loop device ?

  • Everything related to Xen Orchestra's REST API

    84 Topics
    629 Posts
    K
    @olivierlambert & @mathieura thanks for the speedy response. Duly noted, very much appreciated.

  • 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
Log in to post
Load new posts
  • D

    SR not working: stale NFS handle

    2
    0 Votes
    2 Posts
    513 Views
    I
    @djingo Have you made any config changes to unraid? That will often make nfs go stale.
  • R

    Template usage doc

    2
    0 Votes
    2 Posts
    190 Views
    olivierlambertO
    Hi, In XO Hub, you already have a Debian 11 which is Cloudinit ready This is more a Cloudinit question BTW, you should ask their community. Frankly, Cloudinit doc isn't great and many things changed a lot
  • ForzaF

    VM console borks with "Alt Gr" key

    8
    0 Votes
    8 Posts
    3k Views
    K
    @olivierlambert I can confirm: This issue is solved in XO Lite, but still present in XOA.
  • K

    What are these 34+ tasks - going 5+ hours

    4
    1
    0 Votes
    4 Posts
    513 Views
    K
    Restarting the toolstack on AHP101 (which was the pool master) cleared the tasks. Hopefully no long term side effects
  • mauzillaM

    Changing the backup name

    6
    0 Votes
    6 Posts
    1k Views
    julien-fJ
    @mauzilla There is no easy way to achieve that, it requires updating a number of other_config entries manually. If you have a paid subscription, open a support ticket and I'll take care of it for you
  • M

    Delta backups: Restore issue

    Solved
    4
    0 Votes
    4 Posts
    788 Views
    A
    @MrNaz It merges the past delta backup into the past full backup. Then it does a delta backup..... then you repeat.... Since you only keep one copy it just keeps merging the delta into the full backup. The delta backup depends on the old full backup existing and being correct. When it does a "full backup", it does a full backup of the data not just a delta (the changes). That way it does not merge the new full backup into the old full backup (or depend upon any old backups). Doing a full backup is a good checkpoint in case the old data (full or deltas) is corrupted. So having the retention set to 1 basically means you only have the most current backup saved. With backups every 12 hours you might want to set the retention to 20 so you have about 10 days of backups and every 5 days (10 backups) it will do a full backup. Or set it higher if you have more backup space.
  • T

    xo-web build from source, FATAL ERROR: Ineffective mark-compacts near heap limit Allocation failed

    Solved
    7
    1
    0 Votes
    7 Posts
    642 Views
    T
    @Danp Thanks RAM was problem. There was only 1.5GB, which was default value with XCP-ng center. Now it compiled successfully with 4GB. [image: 1684340422417-28e1c460-9d67-44b4-b018-96d1b9531bc7-obraz.png]
  • SchmalzTechS

    Remove/Reset TOTP 2FA

    mfa 2fa totp
    5
    0 Votes
    5 Posts
    1k Views
    DanpD
    Another option is to add a new admin user using xo-cli. Then login to XO as the new user and clear the OTP for the existing user.
  • K

    Advanced Live Telemetry - Cluster-Wide

    2
    0 Votes
    2 Posts
    399 Views
    olivierlambertO
    Hi, No easily, no (at XCP-ng level at least). Maybe in the future with Open metrics everywhere. You can already track a VM metrics whatever they move to by having VM metrics from within the VM itself (eg VM is sending its metrics via netdata to a central netdata that will store them in Prometheus for example).
  • K

    Boot after restore - excluded swap

    6
    0 Votes
    6 Posts
    610 Views
    olivierlambertO
    XO doesn't have access to the VM content so it's not possible at the moment.
  • sMteXS

    Cannot use cloudConfig while creating VM with RPC call

    Solved
    23
    0 Votes
    23 Posts
    8k Views
    TheiLLeniumStudiosT
    @julien-f The problem seems to be fixed now! Thank you for the fix
  • M

    Xen-Orchestra broken after rollback

    8
    0 Votes
    8 Posts
    2k Views
    M
    So I'm very very sorry for digging this up; I had this XO installation halted for a while wanted to come back to it. In the meanwhile the resolution for the error presented on the initial post: 2022-09-22T10:50:18.823Z xo:xo-server ERROR unhandled error event { error: Error: connect ECONNREFUSED ::1:6379 at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1161:16) at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) { errno: -111, code: 'ECONNREFUSED', syscall: 'connect', address: '::1', port: 6379 } } Solution: Edit /etc/redis.conf; Comment the bind directive; Save, restart redis, done.
  • brodiecyberB

    Unable to convert VM to Template in Xen Orchestra ( VBD_IS_EMPTY )

    Solved
    11
    0 Votes
    11 Posts
    2k Views
    julien-fJ
    @josh383451 The bug was fixed 3 days ago: https://github.com/vatesfr/xen-orchestra/commit/73d88cc5f1a5458c68e6935a9d5a9240616007b1 0 julien-f committed to vatesfr/xen-orchestra fix(xo-server/vm.convertToTemplate): handle VBD_IS_EMPTY (#6808) Fixes https://xcp-ng.org/forum/post/61653
  • bullerwinsB

    Continuous Replication health check fails

    Solved
    7
    2
    0 Votes
    7 Posts
    1k Views
    bullerwinsB
    Just updated to lastest commit https://github.com/vatesfr/xen-orchestra/commit/4bd5b38aeb9d063e9666e3a174944cbbfcb92721 It's fixed now. Working wonderfully. Thanks! [image: 1683882828176-603fbea0-1c07-45b8-a005-54c100a74663-image.png] 0 fbeauchamp committed to vatesfr/xen-orchestra fix(backups): fix health check task during CR (#6830) Fixes https://xcp-ng.org/forum/post/62073 `healthCheck` is launched after `cleanVm`, therefore it should be closing the parent task, not `cleanVm`.
  • S

    Cannot export OVAs

    Solved
    64
    0 Votes
    64 Posts
    22k Views
    olivierlambertO
    Thanks for your feedback lads!
  • escape222E

    Option to Create Host only Private Network

    4
    1
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    Then it's a bug Pinging @pdonias or @julien-f
  • dumarjoD

    Import from vmware esxi 6.0 or 6.5

    13
    0 Votes
    13 Posts
    2k Views
    M
    @florent Tunnel ID sent via chat. Thank you for your help.
  • bullerwinsB

    XOA Proxy Error when updating

    5
    1
    0 Votes
    5 Posts
    2k Views
    bullerwinsB
    @julien-f said in XOA Proxy Error when updating: @bullerwins XO Proxy Appliance deployment is not supported in XO built from sources. my bad, it used to work a few months back I believe @olivierlambert said in XOA Proxy Error when updating: I missed that in the original message, indeed FYI @bullerwins there's no such thing as XOA built from sources, you have either: XOA is Xen Orchestra virtual Appliance, that's the VM we distribute with pro support and QA/stable channel, updater and such XO from the sources is from Github, without pro support but community support, no QA no stable version, no udpater and such Thanks, I got confused with the naming, I'm using the second option. As a workaround I used a VPN to manage the remote XCP-ng host, thanks!
  • F

    Kubernetes cluster recipes not seeing nodes

    43
    0 Votes
    43 Posts
    27k Views
    F
    @Raymondello you right, the issue is from the storage and I am looking into that. Thank you for sharing the UAT Testing, I didn't know about it
  • N

    Fail2Ban for failed Xo-Web-Logins

    Solved
    16
    0 Votes
    16 Posts
    3k Views
    konsultanerK
    Found the issue. I used the service from the repo like this: But I had to replace @BINDIR@ to /usr/bin. [Unit] Description=Fail2Ban Service Documentation=man:fail2ban(1) After=network.target iptables.service firewalld.service ip6tables.service ipset.service nftables.service PartOf=iptables.service firewalld.service ip6tables.service ipset.service nftables.service [Service] Type=simple Environment="PYTHONNOUSERSITE=1" ExecStartPre=/bin/mkdir -p /run/fail2ban ExecStart=/usr/bin/fail2ban-server -xf start # if should be logged in systemd journal, use following line or set logtarget to sysout in fail2ban.local # ExecStart=/usr/bin/fail2ban-server -xf --logtarget=sysout start ExecStop=/usr/bin/fail2ban-client stop ExecReload=/usr/bin/fail2ban-client reload PIDFile=/run/fail2ban/fail2ban.pid Restart=on-failure RestartPreventExitStatus=0 255 [Install] WantedBy=multi-user.target