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

      DevOps Megathread: what you need and how we can help!

      Watching Ignoring Scheduled Pinned Locked Moved Infrastructure as Code
      33
      4 Votes
      33 Posts
      3k Views
      A
      Hi, I'm currently testing deployments with pulumi using packer templates. So far the basics work as expected but I'm stuck on a setting issue that seems to affect both pulumi and terraform providers. As far as I know there is no way to set the memory as static or changing memory_min when creating a VM from a template. The template was created with 1cpu and 2GB of RAM [image: 1752573420785-screenshot-2025-07-15-at-11.56.01.png] The VM created from this template using pulumi was assigned 2cpus and 4GB of RAM, however this only sets memory_max [image: 1752573490942-screenshot-2025-07-15-at-11.56.21.png] I found the following post that talks about this: https://xcp-ng.org/forum/topic/5628/xenorchestra-with-terraform and also the folllowing github issue https://github.com/vatesfr/terraform-provider-xenorchestra/issues/211 Manually setting the memory limits after VM creation defeats the purpose of automation. I suppose that implementing those settings in the relevant providers is a core feature. In most cases, VMs need static memory limits. In the meantime, is there any workaround that I should investigate or anything that I missed ? slax81 created this issue in vatesfr/terraform-provider-xenorchestra open Dynamic memory control #211
    • B

      Migrating from XCP-ng Windows guest tools to Citrix

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      20
      0 Votes
      20 Posts
      660 Views
      B
      I did it that way so as to get the old Citrix driver first, and then let it update and watch it reboot. That was my logic anyway. @dinhngtu said in Migrating from XCP-ng Windows guest tools to Citrix: @bberndt Okay, I managed to reproduce your situation. I think it's because the "driver via Windows Update" option was enabled after installing the XS drivers, which caused the drivers to lock onto the non-C000 device and prevent updates from coming in. Normally, XenClean should be able to fix the situation. But if you want to fix things manually, or if things still don't work (C000 is still not active), here's a procedure that should fix the problem: Take a snapshot/backup/etc. Keep a note of static IP addresses (if you have any; there's a chance those will be lost). You can also use our script here: https://github.com/xcp-ng/win-pv-drivers/blob/xcp-ng-9.1/XenDriverUtils/Copy-XenVifSettings.ps1 Reboot in safe mode and disable the non-C000 device. Reboot back to normal mode; it'll ask you to reboot a few more times. The C000 device should now be active and you should be able to get driver updates again. (Optional) You can now enable and manually update the non-C000 device (Browse my computer - Let me pick).
    • J

      How to create a user with read only access to all objects in xoa for monitoring purposes

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      5
      0 Votes
      5 Posts
      410 Views
      F
      Hello everyone. I tripped over this issue. If someone got another approach I would be interested. Thanks to @lsouai-vates I had a look at: https://github.com/vatesfr/xen-orchestra/blob/ab56924b1d046ccf6c09dfe7a4ab47deb5d77f4a/packages/xo-acl-resolver/index.js and https://github.com/vatesfr/xen-orchestra/blob/ab56924b1d046ccf6c09dfe7a4ab47deb5d77f4a/packages/xo-server/src/xo-mixins/acls.mjs#L150-L168 To what I understand it is not possible as a Non-Admin user to get information like pools, ... By creating a new admin user limiting the resources via ACLS with viewer right worked around this. However, granting admin rights still looks sort of strange. Just in case someone struggled as well this information might help.
    • michael.manleyM

      XCP-ng Center 25.04 Released

      Watching Ignoring Scheduled Pinned Locked Moved News
      24
      4 Votes
      24 Posts
      3k Views
      D
      @uberiain said in XCP-ng Center 25.04 Released: Hi, with this modification on MainWindow.cs in private List<TabPage> GetNewTabPages() adding this at the end: This will add the tab back in XCP-ng Center but I don't think it works in XCP-ng 8.3. I just upgraded from 8.2.1 to 8.3 when I logged into XCP-ng Center I saw the error message Active Directory authorization is not available","Server 'xcp-ng-TEST' has failed to connect to the Active Directory server. INTERNAL_ERROR: [ Xapi_systemctl.Systemctl_fail(""INTERNAL_ERROR: [ Subprocess exited with unexpected code 1; stdout = [ ]; stderr = [ Job for winbind.service failed because the control process exited with error code. See \""systemctl status winbind.service\"" and \""journalctl -xe\"" for details.\n ] ]"") ]","xcp-ng-TEST","Jul 11, 2025 3:58 PM"," # systemctl status winbind.service winbind.service - Samba Winbind Daemon Loaded: loaded (/usr/lib/systemd/system/winbind.service; disabled; vendor preset: disabled) Active: failed (Result: exit-code) since Fri 2025-07-11 16:01:28 AEST; 3min 15s ago Docs: man:winbindd(8) man:samba(7) man:smb.conf(5) Main PID: 9593 (code=exited, status=1/FAILURE) Status: "Starting process..." I haven't figured out what to do yet. None of the users can log into XCP-ng Center using their Active Directory credentials and only root can log in. EDIT: Actually winbind wasn't even used in XCP-ng 8.2.1, I'm not sure why this service started up in 8.3. XCP-ng 8.2.1# systemctl status winbind.service ā— winbind.service - Samba Winbind Daemon Loaded: loaded (/usr/lib/systemd/system/winbind.service; disabled; vendor preset: disabled) Active: inactive (dead) Docs: man:winbindd(8) man:samba(7) man:smb.conf(5) But I can see that windbind is used for XenServer 8.4 https://docs.xenserver.com/en-us/xenserver/8/users Anyone got suggestions on how to get AD authentication working with XCP-ng Center again? Or add users manaully? SOLUTION: What I found after following the steps in the in the XenServer page above is that if I disable AD Authentication then re-enable it then it will work. To Disable AD Authentication: xe pool-disable-external-auth Enable AD Authentication: xe pool-enable-external-auth auth-type=AD service-name=full-qualified-domain config:user=username config:pass=password Without the Users tab in XCP-ng Center, CLI command is needed to add or remove users. Refer to the XenServer page above. xe subject-add subject-name=entity_name