Subcategories

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

    378 Topics
    3k Posts
    olivierlambertO
    Hi, Do you have any error message? What's happening? Anything visible or not?
  • ACLs, Self-service, Cloud-init, Load balancing...

    93 Topics
    783 Posts
    MK.ultraM
    @tmk said in Cloudbase-init on Windows: @jkatz I ran into the same issue when trying to configure a network adapter with cloudbase-init. The documentation says that the MAC address value is optional but in reality it is required. In my case I want Xen Orchestra to choose a unique MAC during deployment, and I since I am deploying from a template, the NIC name is a known value. The fix that ended up working for me was to modify the networkconfig.py file in cloudbase-init so that the NIC name is required and the MAC address is optional. I ended up making some additional changes to allow for the network-config v2 format along with the existing v1 support and some additional logic to aid in setting the dns search domains (I can't recall if this was originally supported or not but I had issues getting it to work with the original networkconfig.py file) This file needs to replace the existing one that is installed in the C:\Program Files\Cloudbase Solutions\Cloudbase-Init\Python\Lib\site-packages\cloudbaseinit\plugins\common\ directory. To replace it you should make sure that the cloudbase-init service is stopped, then replace the file. Once this file is replaced, delete the pycache folder in the same parent folder as networkconfig.py - this will ensure that python recompiles this file on service start. Start the cloudbase-init service and confirm that you see a new pycache get created. I'm not a python programmer by trade so others may be able to point out areas for improvement but this ended up working for me and I wanted to share in case it could help others needing to deploy new servers without manually specifying a new MAC address. Below is an example network-config v2 format that works with the updated file. version: 2 ethernets: Ethernet 2: dhcp4: false addresses: - 10.20.30.10/24 nameservers: addresses: - 10.20.5.12 - 10.20.5.13 - 10.20.5.14 search: - intranet.domain.org - domain.org - public-domain.org routes: - to: default via: 10.20.30.1 Updated networkconfig.py file: networkconfig.py.txt Thank you for posting! I followed your directions verbatim and I'm still having trouble getting the network config to take. Does it work with Windows Server 2025?
  • All XO backup features: full and incremental, replication, mirrors...

    389 Topics
    4k Posts
    olivierlambertO
    @florent so it's like https://github.com/vatesfr/xen-orchestra/commit/a459015ca91c159123bb682f16237b4371a312a6 might introduced a regression? 0 fbeauchamp committed to vatesfr/xen-orchestra Fix(replication): VDI_NOT_MANAGED error (#8935) from ticket #40151
  • Everything related to Xen Orchestra's REST API

    68 Topics
    529 Posts
    olivierlambertO
    @lsouai-vates we should try to reproduce and if we can, to fix it ASAP. Thanks!
  • Terraform, Packer or any tool to do IaC

    35 Topics
    350 Posts
    J
    @manilx I have proposed to the IaC team of Vates, a MCP Server for Vates VMS. Which can be used by GitHub Copilot or similar, if used when doing IaC etc.
  • Import from vmware esxi 6.0 or 6.5

    13
    0 Votes
    13 Posts
    1k Views
    M
    @florent Tunnel ID sent via chat. Thank you for your help.
  • XOA Proxy Error when updating

    5
    1
    0 Votes
    5 Posts
    1k 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!
  • Kubernetes cluster recipes not seeing nodes

    43
    0 Votes
    43 Posts
    22k 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
  • Fail2Ban for failed Xo-Web-Logins

    Solved
    16
    0 Votes
    16 Posts
    2k 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
  • Unable to create NFS SR with truenas after rebuilding truenas

    Solved
    5
    1
    0 Votes
    5 Posts
    1k Views
    E
    @iLix That worked! I guess i forgot to enable NFSv4 after rebuilding it.
  • Samba Timeout - How to configure timeout limit / possible issues ?

    4
    0 Votes
    4 Posts
    4k Views
    olivierlambertO
    I can't follow what's done in 3rd party scripts, and it might be not trivial to find problems with them (if it's a problem due to the script or not). But before pointing any finger (I don't like that ) I would prefer to check with a fully up to date XOA on latest release channel and see if you have the same issue. At least, we'll be able to compare the behavior
  • 0 Votes
    2 Posts
    267 Views
    olivierlambertO
    Hi, I'm not aware of such feature on our side, you should ask AWS on how to import a XenServer/XCP-ng VM into EC2.
  • Non Fatal Error Starting XOA

    8
    0 Votes
    8 Posts
    692 Views
    olivierlambertO
    Quick note: XOA is for our Xen Orchestra virtual Appliance. You are using XO from the sources So it's just "XO". Anyway, indeed, it seems that your forever service isn't able to kill the process therefore, keep it.
  • Question On Cloud-init and ConfigDrive

    1
    0 Votes
    1 Posts
    629 Views
    No one has replied
  • Missing VMs from Restore

    5
    1
    0 Votes
    5 Posts
    365 Views
    yarozY
    @olivierlambert said in Missing VMs from Restore: Try to see after a new backup with this version We'll see then. Thank you. I'll check it after tonight's run.
  • Memory usage is not showing up in XOA

    Solved
    12
    1
    0 Votes
    12 Posts
    1k Views
    S
    @olivierlambert That did the trick. Wanted to make sure to say thanks for your help. Thanks again! Hope you have a great day!
  • XO rebooted, remotes lost, unable to add back

    16
    0 Votes
    16 Posts
    2k Views
    olivierlambertO
    So what you need is more something like backup tiering (or secondary backup). This feature is currently a work in progress by @florent
  • Continuous Replication backup (Missing Job)

    2
    0 Votes
    2 Posts
    225 Views
    olivierlambertO
    It means one VM got a backup job that's not in your current XO. Are you sure you restored your previous XO config?
  • Smart reboot. Is that going to be implemented?

    5
    0 Votes
    5 Posts
    752 Views
    J
    @olivierlambert ok. For info: xo-server 5.113.0 / xo-web 5.116.1 Installed this version XO yesterday and tried a smart reboot with 14 vm's running. Windows and linux vm's. Of which some linux vm's have NFS shares which I use for ISO files and making backups with XO. These I normally have to disconnect before I can do a reboot of the host otherwise it will not reboot and had expected that this would not be necessary now. It took a very long time for all vm's to enter suspend mode (>2 hours) and the server did not reboot. Probably ran into not shutting down the NFS shares. I finish much faster if I manually shut down all vm's (and disconnect the NFS shares) reboot the host and restart the vm's. But maybe I am overlooking something then I would like to hear about it.
  • How to fix XOSTOR

    11
    0 Votes
    11 Posts
    2k Views
    F
    @brodiecyber I can see it exist in /opt/xensource/bin/linstor-kv-tool but no idea on how to use it
  • Can't import ISO through OVA--not a supported filetype?

    4
    0 Votes
    4 Posts
    457 Views
    MathieuRAM
    @miker Hi Thank you for your feedback. We will explore ways to enhance the current UI.
  • Xen Orchestra Update Failed - Error: ENOSPC: no space left on device

    9
    0 Votes
    9 Posts
    2k Views
    DanpD
    You may need to extend the partition first using growpart.
  • 0 Votes
    7 Posts
    830 Views
    olivierlambertO
    Okay so you are right: we did not test this scenario, so that's why the error is cryptic. I'm adding @Enishowk in the loop so he can put that in our backlog
  • Why do I see this message?

    4
    0 Votes
    4 Posts
    791 Views
    planedropP
    If I'm being honest here I don't really find the messages as annoying as you are making them out to be. Sure if I had a choice I would want them gone, but it's really not a big deal, 1-2 clicks and they are gone until the next time I login. I also kinda like the reminder on the sidebar about no support, helps me remember that A. I'm in my lab environment and B. I'm using a from the sources version so I need to manually do updates etc.....
  • Slow backups (updated XO source issue)

    17
    0 Votes
    17 Posts
    2k Views
    A
    @julien-f Thanks. I updated to 0444cf0 and CR times are normal again (as expected).