Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    marcoiM
    went well with test systems. going to do prod soon.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    I checked this on an 8.3 host here, and your sshd_config.d observation is exactly right: the shipped /etc/ssh/sshd_config has no Include line at all, so anything you drop in that directory is never read. The directory exists and is empty, which is what makes it look like it should work. It is not an OpenSSH version limit either, since the package is openssh-server-9.8p1-1.2.4.xcpng8.3 and 9.8 supports Include fine. On @tjkreidl's route, two things check out on my side: the packaged unit really is ExecStart=/usr/sbin/sshd -D $OPTIONS, so his blank ExecStart= plus a replacement line is the correct shape, and RH-Firewall-1-INPUT does exist as a chain, so his iptables step targets the right place. I have not actually moved a port with it, so treat that as "the pieces line up" rather than "I tested it end to end", and keep a second session open when you try. Might be worth a mention to @Team-OS-Platform-Release, since whether there is a supported way to pin a port is a packaging question more than a config one.
  • 3k Topics
    29k Posts
    acebmxerA
    @poddingue After going back to Veeams website and review the information they do state allot of features are not ready in the web interface use to interact with the Appliance vs the Windows client and suggest to use the windows client. I guess its a debate on which way to deploy it. The application seems to focus more on security by forcing secure passwords and setting up MFA. While the installing B&R on windows. Well its Windows.... Using the Windows client to interact with either install options function identically. Just an obvious note - Dont backup vms with Veeam and Xen Orchestra. Veeam will break the backup chain on Xen Orchestra forcing next Xen Orchestra backup to do a Full backup. I didnt push further and do another Veeam backup. Have not tested Restore functionality as of yet. [image: 1785616452622-screenshot_20260801_162929.png]
  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!
  • 37 Topics
    128 Posts
    poddingueP
    Merci pour les précisions, elles écartent ma piste. Si vous reproduisez en BIOS comme en UEFI, le ticket #151 ne colle pas, d'autant qu'il parle de l'installeur Windows et pas d'Anaconda : je l'avais résumé un peu vite. La différence intéressante est peut-être RHEL 9 contre RHEL 10, puisque @AtaxyaNetwork a un build qui fonctionne en 10 avec cd_files et sans DHCP, et son test en 9 ce week-end devrait trancher. Sur cd_label = "OEMDRV", je n'ai trouvé ni issue ni PR dans le dépôt du plugin, donc ça n'existe visiblement pas encore : si ça vous va, ça ferait une demande propre à ouvrir sur https://github.com/vatesfr/packer-plugin-xenserver, en reprenant l'argument air-gapped que vous détaillez plus haut, qui est plus convaincant que ce que j'écrirais moi. Je ne connais pas assez le plugin pour dire si c'est simple à ajouter, donc je préfère ne rien promettre. Merci en tout cas de documenter tout précisément, ça servira sans doute bien au-delà de votre POC.