XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • olivierlambertO

      ๐Ÿ›ฐ๏ธ XO 6: dedicated thread for all your feedback!

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      327
      7 Votes
      327 Posts
      225k Views
      poddingueP
      @coolsport00 not in XO 6 yet as far as I can tell. For now it's still done from XO 5: Home > Pools, open the pool, then "Add Hosts" at the top right, once the new host has been added as a server (docs). I believe the XO team already has it on their list for the pool dashboard. If you want to push it, there's a close Feeder request you could vote on, which also asks for a proper add-host form: https://feedback.vates.tech/posts/75/permit-to-add-host-to-pool-with-a-real-form @Greg_E thanks for the screenshot. It looks like the parent task keeps reporting 1% once the metadata backups underneath it are done. I think that one is known too, but I'll let the XO team confirm.
    • B

      New project - XenAdminQt - a cross-platform GNU/Linux, macOS, Windows native thick client

      Watching Ignoring Scheduled Pinned Locked Moved News
      53
      1
      9 Votes
      53 Posts
      18k Views
      B
      @bvitnik yes it's very easy to build on debian, you need to install the qt packages: sudo apt-get install qt6-base-dev build-essential freerdp2-dev libwinpr2-dev mesa-common-dev libglu1-mesa-dev libegl1-mesa-dev libxkbcommon-dev libegl1 libxkbcommon0 qt6-charts-dev libssl-dev zlib1g-dev # then clone the repo git clone https://github.com/benapetr/XenAdminQt cd XenAdminQt mkdir release cd release qmake6 ../src make -j $(nproc) built binary will be in xenadmin-ui dir
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      802
      1 Votes
      802 Posts
      1m Views
      R
      Thank you, @stormi , I'm happy to know that xcp-ng.repo is not touched. These three hosts haven't been rebuilt or restored recently, no hosts have been added, and I did have to make the above modification on each one of them to get them to work. I suppose it's possible I missed the step to remove "mirrors.xcp-ng.org" from xcp-ng.repo during the initial pool build about a year ago and it's just somehow been working with our outbound Internet proxy. In any event, having "mirrors.xcp-ng.org" in our xcp-ng.repo file has definitely caused us problems in the past with our proxy setup. TGIF/DMCV!
    • F

      Xen Orchestra web UI becomes unresponsive when an NFS backup remote goes offline

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Xen Orchestra
      18
      0 Votes
      18 Posts
      760 Views
      acebmxerA
      @poddingue added my info as well.
    • S

      Backup failures after VHD to QCOW2 conversion

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      8
      0 Votes
      8 Posts
      408 Views
      poddingueP
      Thanks for sharing those. I can't read SMlogs well enough to add anything useful myself, so this is really one for @Team-Storage. One thing though: if I read the link right, it expires on 23 November, so it would be good if someone grabbed the files before then.
    • P

      Full backup failure when upgrading XOce

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Backup
      7
      0 Votes
      7 Posts
      100 Views
      poddingueP
      Small correction to what I wrote above. There's an open PR for XO on Node 26 (https://github.com/vatesfr/xen-orchestra/pull/10721) whose description says several outgoing HTTP requests from xo-server fail on 26 until it's merged: web hooks, Netbox, XO Proxies, the patch list, imports from a URL. So the docs saying "latest LTS" doesn't make 26 a safe bet right now, and I shouldn't have made it sound like one. My bad. @ph7, backups to a NAS aren't in that PR's list if I'm reading it right, which would fit with yours working, but the rest might bite you. As @jr-m4 and @acebmxer pointed out, https://github.com/vatesfr/xen-orchestra/pull/10790 would pin the docs to Node 22 like XOA. I'm still asking the team which version they actually want people on, and I'll come back here once I know.
    • R

      RPU on XOSTOR pool: live migration fails while evacuating the host running the linstor controller, VM left unmanageable

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XOSTOR
      5
      0 Votes
      5 Posts
      252 Views
      poddingueP
      If I follow your excerpts, there are two different problems stacked here. One is the LinstorSR attach giving up on what looks like a one-second controller hiccup, which is the @Team-Storage side. The other is xenopsd leaving state behind on both hosts after the failed sync point 4, so that every later run trips over it. I think that half belongs to the toolstack people rather than storage, so I'm adding @Team-XAPI-Network too. I can't judge either part myself, so I'll leave it with them.
    • Tristis OrisT

      Disk import not happens

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      5
      0 Votes
      5 Posts
      230 Views
      Tristis OrisT
      error via reverse proxy. Uncaught Error: Body is not a JSON, original message is : <html> <title>500 Internal Server Error</title> <style>html{color-scheme:light dark;}</style> </head> <body> <center><h1>500 Internal Server Error</h1></center> <hr><center>Angie</center> </body> </html> pr index.js:2564 me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 promise callback*me index.js:4029 i index.js:4029 be index.js:4029 be index.js:4029 dr index.js:2531 importDisks index.js:2575 Lodash 2 importDisks index.js:2574 e index.js:113 P index.js:22 i index.js:22 R index.js:22 R index.js:22 import index.js:121 t factory.js:307 o factory.js:331 e action-button.js:93 m action-button.js:10 i action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 _execute action-button.js:10 v action-button.js:140 componentDidMount action-button.js:147 React 14 componentWillUnmount factory.js:125 f factory.js:31 _dispatch factory.js:158 t factory.js:322 promise callback*t factory.js:313 o factory.js:331 value index.js:206 promise callback*value index.js:174 React 5
    • F

      [Bug?] Load Balancer: Performance mode fails to power on hosts previously shut down by Density mode

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Xen Orchestra
      4
      1 Votes
      4 Posts
      207 Views
      Bastien NolletB
      Here's the fix, which should be merged in the following days/weeks, and should be in the next XO release: https://github.com/vatesfr/xen-orchestra/pull/10809
    • O

      Rolling pool update

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      13
      0 Votes
      13 Posts
      637 Views
      J
      @tjkreidl said: @john.c Note that a two-host pool running HA can run into the split-brain issue if one of the hosts fails; it's highly recommended to have at least three hosts in an HA pool (or look into HA-Lizard if running a pool with two hosts and HA). Right but also considering the in development Twinstor for when it goes stable and in production!
    • C

      XO RBAC Granularity?

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      10
      0 Votes
      10 Posts
      369 Views
      julienXOvatesJ
      Thanks @ataxyanetwork I was about to answer the same...! (but was too busy this morning )
    • F

      New Tools 9.2.445 update failure

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Management
      3
      1
      0 Votes
      3 Posts
      88 Views
      olivierlambertO
      Pinging @dinhngtu
    • D

      XCP-ng Windows PV tools announcements

      Watching Ignoring Scheduled Pinned Locked Moved News
      120
      0 Votes
      120 Posts
      66k Views
      F
      Running into an installation issue with this new version. I created a separate thread here about the issue: https://xcp-ng.org/forum/topic/12580/new-tools-9.2.445-update-failure
    • B

      New 9.2.445 XCP Windows tools Roll Back

      Watching Ignoring Scheduled Pinned Locked Moved Management
      3
      0 Votes
      3 Posts
      196 Views
      B
      Looks like the tools installation had an issue with Windows Update packages, the windows event log started throwing error relating to the cryptsvc service and C:\Windows\System32\catroot2 at the time I ran XenClean before trying to install 9.2445. Rebuilding Catroot resolved the issue and tools installed fine. net stop cryptsvc ren C:\Windows\System32\catroot2 catroot2.old net start cryptsvc Reboot Appears to be isolated to this single VM
    • C

      Booting Homeassistant (HAOS) Image breaks VM

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      5
      0 Votes
      5 Posts
      407 Views
      C
      @IgorGlock What do you mean by "okay"? Backing up the VM with Commvault or...?
    • julien-fJ

      [Security] VSA-2026-062: critical Xen Orchestra vulnerability fixed, please update

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      3
      4 Votes
      3 Posts
      967 Views
      J
      @vmpr Popping it behind an instance of BunkerWeb (https://www.bunkerweb.io/) or similar, with Xen Orchestra on a new IP address would help. As BunkerWeb is whatโ€™s known as a Web Application Firewall. It will help to protect your instance of Xen Orchestra, especially if you change the IP address of the appliance, and only give that friend the one that goes through BunkerWeb. As always donโ€™t expose Xen Orchestra to the Internet, but if itโ€™s absolutely necessary always use something like BunkerWeb (with BunkerNET) and only provide the BunkerWeb based IP address! Also run a check on all of your hosts and may be best to roll them a fresh (in case thereโ€™s an Advanced Persistent Threat). As well as a fresh instance of Xen Orchestra, and maybe encourage your friend while also doing yourself to start using hardware security keys, preferably ones that support biometrics and PINs. Alternatively other secure enclaves with cryptographic credentials held there. Additionally opt into the new encrypted datastore for Xen Orchestra on the new fresh Xen Orchestra and XCP-ng. Also make sure itโ€™s completely up to date! Also if the hosts support it ensure that Intel TME or similar is enabled on the fresh installs of XCP-ng. Finally rotate all passwords associated with that system, including your Vates account password, especially if itโ€™s linked to the Xen Orchestra instance hit.
    • D

      MFA for console access

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved XCP-ng
      2
      0 Votes
      2 Posts
      108 Views
      poddingueP
      I haven't tried Duo on a host myself, so this comes from reading an 8.3 dom0 rather than from experience. The first thing I'd watch is that XAPI checks the root password through PAM as well. /etc/pam.d/xapi just includes system-auth, so my guess is that a Duo module placed in system-auth would make every password login to XAPI (XO's connection to the pool, xe -pw, XO Lite) ask for a factor it can't give. The physical console is less simple than it looks too: tty1 runs xsconsole, and on my 8.3 host it checks root against the password-auth PAM service by handing over just the password, so I'd expect a module that asks a second question to make that login fail rather than prompt. Also worth knowing before an audit: software from outside the XCP-ng repos isn't supported in dom0 (https://docs.xcp-ng.org/installation/requirements), and as far as I can tell from rpm, /etc/pam.d/xapi isn't marked as a config file, so an update would put it back. Anyone who has been through this for real will know more than me.
    • A

      Increasing the disk size of vmguest without shuting down

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      12
      0 Votes
      12 Posts
      6k Views
      olivierlambertO
      Hi @odmsys It's on the roadmap and it won't wait for SMAPIv3. I truly hope we can bring something in a matter of few months, at least to have it to test
    • I

      Windows Server 2025 VM randomly freezes/hangs (loss of VNC + RDP + console) on XCP-ng โ€” reboot required

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Compute
      5
      0 Votes
      5 Posts
      548 Views
      I
      @gudge25 check these https://docs.xcp-ng.org/vms/#enabling-viridian-extensions and https://lazyadmin.nl/it/september-2026-update-break-rds-how-to-fix/
    • olivierlambertO

      XOSTOR hyperconvergence preview

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      471
      1
      6 Votes
      471 Posts
      1m Views
      Maelstrom96M
      @dthenot For anyone stuck, here is what I ended up doing: I've manually hardcoded the controller_uri in /opt/xensource/sm/linstorvolumemanager.py on the new host, restarted the toolstack using xe-toolstack-restart and ran the xe host-call-plugin host-uuid=NEW_HOST_UUID plugin=linstor-manager fn=addHost args:groupName=linstor_group/thin_device command. def _get_controller_uri() -> str: # TODO: Check that an IP address from the current pool is returned. #addresses = _get_controller_addresses() return "linstor://10.25.254.100" #return "linstor://" + addresses[0] if addresses else "" After that, you should see the addHost command return True. It should be safe to revert the change to the _get_controller_uri() function and restart to make sure everything starts properly. [10:06 van3-pprod-xen01 ~]# linstor --controllers 10.25.254.100 node l โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”Š Node โ”Š NodeType โ”Š Addresses โ”Š State โ”Š โ•žโ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•ก โ”Š van3-pprod-xen01 โ”Š COMBINED โ”Š 10.25.254.100:3366 (PLAIN) โ”Š Online โ”Š โ”Š van3-pprod-xen02 โ”Š COMBINED โ”Š 10.25.254.101:3366 (PLAIN) โ”Š Online โ”Š โ”Š van3-pprod-xen03 โ”Š COMBINED โ”Š 10.25.254.102:3366 (PLAIN) โ”Š Online โ”Š โ”Š van3-pprod-xen04 โ”Š COMBINED โ”Š 10.25.254.103:3366 (PLAIN) โ”Š Online โ”Š โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ [10:06 van3-pprod-xen01 ~]# xe host-call-plugin host-uuid=f9d94f6c-e826-452f-b9b9-638550b209cf plugin=linstor-manager fn=addHost args:groupName=linstor_group/thin_device True [10:08 van3-pprod-xen01 ~]# linstor --controllers 10.25.254.100 node l โ•ญโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฎ โ”Š Node โ”Š NodeType โ”Š Addresses โ”Š State โ”Š โ•žโ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•โ•ก โ”Š van3-pprod-xen01 โ”Š COMBINED โ”Š 10.25.254.100:3366 (PLAIN) โ”Š Online โ”Š โ”Š van3-pprod-xen02 โ”Š COMBINED โ”Š 10.25.254.101:3366 (PLAIN) โ”Š Online โ”Š โ”Š van3-pprod-xen03 โ”Š COMBINED โ”Š 10.25.254.102:3366 (PLAIN) โ”Š Online โ”Š โ”Š van3-pprod-xen04 โ”Š COMBINED โ”Š 10.25.254.103:3366 (PLAIN) โ”Š Online โ”Š โ”Š van3-pprod-xen05 โ”Š COMBINED โ”Š 10.25.254.104:3366 (PLAIN) โ”Š Online โ”Š โ•ฐโ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ”€โ•ฏ