Categories

  • All news regarding Xen and XCP-ng ecosystem

    136 Topics
    4k Posts
    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
  • Everything related to the virtualization platform

    1k Topics
    13k Posts
    olivierlambertO
    As I said, you were lucky: it's a question of "not crashing" consumer grade hardware between a driver version and a firmware version (even on server-grade hardware it could happen, but it's simply less likely. That's why I would advise to update first all the firmware first. The next step is to play with a alternative kernel driver for the NIC (if there's one), you could even start there if you like. At least, you know how to trigger it (maybe a simple iperf would be enough) so you can test various drivers and/or firmware versions.
  • 3k Topics
    24k Posts
    M
    @dinhngtu Thank you so much. If you want me I'll be at the pub.
  • Our hyperconverged storage solution

    30 Topics
    653 Posts
    H
    @olivierlambert No, For once, i followed the installation step carefully ^^'
  • 30 Topics
    85 Posts
    GlitchG
    @Davidj-0 Merci pour le retour, j'utilisais aussi une Debian pour mon test ^^