Subcategories

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

    376 Topics
    3k Posts
    olivierlambertO
    Yes! That's a good guide for what you want to achieve
  • ACLs, Self-service, Cloud-init, Load balancing...

    93 Topics
    782 Posts
    T
    @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
  • All XO backup features: full and incremental, replication, mirrors...

    389 Topics
    4k Posts
    olivierlambertO
    That's a feedback for @lsouai-vates
  • 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.
  • XO Contentious Replication no longer working (commit 3d3b6)

    4
    0 Votes
    4 Posts
    288 Views
    A
    Fixed on master (commit d8721). Thanks @florent !
  • VM, missing disk

    26
    4
    0 Votes
    26 Posts
    6k Views
    M
    @Danp Thanks, yes of course. I got excited about fixing my problems and reported too early Well, the VM has been working fine since the export / import. I can see both drives. Although the VM running fine, since the last post I had to address two related VDIs that had been connected to the Control Domain. One being million_D and the other million_D (with a camera icon). These probably ended up here because of a aborted / faulty snapshot or backup. I disconnected them .. checked a few things ... and then forgot them. Everything is running fine now. For future googlers: During the problem solving, I found out some pretty helpful info using tail -f /var/log/SMlog. To me, this issue is solved. Thank you all for the feedback.
  • S3 backup not retrying after error

    22
    0 Votes
    22 Posts
    2k Views
    A
    @florent No, I did not see that in the logs. I did see this problem is bigger than I thought. It happens more often than just causing a VM backup failure. It happens during the merge or other checks which causes the backup process to destroy (remove) parts of other VM backups. Clean VM directory parent VHD is missing parent VHD is missing parent VHD is missing some VHDs linked to the backup are missing some VHDs linked to the backup are missing some VHDs linked to the backup are missing some VHDs linked to the backup are missing and Clean VM directory VHD check error some VHDs linked to the backup are missing
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    4 Views
    No one has replied
  • Great new feature: Restore file from S3 delta backup!

    Locked
    24
    2 Votes
    24 Posts
    5k Views
    olivierlambertO
    If I felt that way and we never had issues in the past, it's maybe for a reason. I'm a very patient person (as you can read since years here). So you shouldn't be saddened but more trying to understand something you provoked (it's still not clear that you understand it). I think it's important to know when not to push too far, and you were clearly too far Next time you are frustrated on an open source software you use for free (likely in production otherwise you wouldn't have been that frustrated), remember that being kind will be more productive in the end. This will be better for everyone. Also I hope it's more clear for you that using things on master was never meant to be under our internal QA since it's not a controlled environment (but it's documented with big warnings. Maybe I'll make it even more clear in the doc, I don't know, I'm surprised you didn't get it since you are using it since a while. Maybe this misunderstanding explained part of your frustration).
  • Coalesce not showing anymore

    Solved
    13
    2
    0 Votes
    13 Posts
    1k Views
    olivierlambertO
    Yay! Thanks both @Gheppy for the report and @errellion for the feedback
  • XCP-ng Authentication to AD (2019)

    6
    0 Votes
    6 Posts
    2k Views
    M
    @olivierlambert Thanks for the link , seems i will go the XOA route as suggested by @Darkbeldin
  • Networking disparity between guest OS and XO

    5
    4
    0 Votes
    5 Posts
    712 Views
    fohdeeshaF
    @jcdick1 I run opnsense on xcp-ng personally as well and use their packaged tools without issue, the only time I've gotten this behavior is when I hot-added interfaces and it changed the order of interfaces. If that's not it, I'm really not sure what would be causing this One last thing you can try in case it's a weird cash issue is (inside XOA) go to settings > servers, click the green connected button next to your xcp-ng server to disconnect it from xoa - then wait a couple seconds and click it again to reconnect it
  • Backup to shared storage

    7
    0 Votes
    7 Posts
    682 Views
    T
    @Darkbeldin In my network NFS and Samba shares would be a VM also on the same host so I would be in the same boat as before
  • Can't make new VM

    13
    0 Votes
    13 Posts
    2k Views
    olivierlambertO
    Same message than the other thread: https://xen-orchestra.com/docs/community.html Read this carefully.
  • Cannot import .ova Xen Orch from sources

    3
    0 Votes
    3 Posts
    300 Views
    olivierlambertO
    You should always start to read this before creating a new thread: https://xen-orchestra.com/docs/community.html
  • IP Address Configuration (does this exist in XOA?)

    2
    1
    0 Votes
    2 Posts
    3k Views
    M
    It is in the same place in XO. Network tab of the host. Change the Mode from None to Static (or DHCP). This should get you a pop up to enter the address, netmask, etc.
  • Very slow Backup speed when using "Continuous Replication" to NFS target

    Solved
    5
    0 Votes
    5 Posts
    979 Views
    0nelight0
    @Andrew Thanks! How to close this issue?
  • NUT Client in XOA

    2
    0 Votes
    2 Posts
    513 Views
    olivierlambertO
    You can call the feature from the API or the CLI
  • Cannot Delete a VM Template through CLI or XE

    Solved
    3
    0 Votes
    3 Posts
    1k Views
    DCTD
    This result worked!!! Thank you very much!!
  • S3 backup broken

    31
    0 Votes
    31 Posts
    7k Views
    A
    @florent Limiting concurrency did not fix my S3 backup problem, but it's working again after updating the build. So I guess it's resolved.
  • 0 Votes
    8 Posts
    1k Views
    R
    You should probably be able to fix this issue by installing the ntfs-3g package. As you mentioned you're running it on a Synology, you can do that in DSM by opening Docker -> Container -> Select your container -> Details -> Terminal and enter the below in the console. apk update apk add ntfs-3g Let us know if it helped.
  • invalid parameter when manually triggering a backup

    Solved
    10
    0 Votes
    10 Posts
    919 Views
    A
    @olivierlambert Yes, thank you so much for the big help.
  • XML-RPC Error and DNS lookup failed when adding new Server

    5
    0 Votes
    5 Posts
    1k Views
    DanpD
    @bradk Sorry for the confusion about the version number.
  • Xen Orchestrta as systemd service

    5
    0 Votes
    5 Posts
    694 Views
    A
    @olivierlambert it is pretty outdated And this is only proposition to add such option to docs.