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.
  • Delta Backup Fails for a Single VM - ENOTDIR (.vhd/chunk-filters.json)

    4
    0 Votes
    4 Posts
    368 Views
    olivierlambertO
    That's why a XOA will be helpful, so a simple support tunnel will do the trick
  • Restoring Full Backup Error: Stream_vdi.Invalid_checksum

    10
    0 Votes
    10 Posts
    1k Views
    florentF
    @lawrencesystems We added the healthcheck for full backup (here : https://github.com/vatesfr/xen-orchestra/pull/6401 ) Also we removed our js smb implementation ( https://github.com/vatesfr/xen-orchestra/commit/b50e95802c6a876d4e6ffd0c62c209a187b1bfb2 ) to try to circumvent the strange samba comportment fbeauchamp opened this pull request in vatesfr/xen-orchestra closed fix(backups): add healthcheck to full backup #6401 0 julien-f committed to vatesfr/xen-orchestra feat(fs): remove JS based SMB handler It's not well tested nor maintained.
  • Why does df -h produce a different disk size than in XO / XOA?

    4
    0 Votes
    4 Posts
    621 Views
    olivierlambertO
    There's no black magic As @ronivay said, you need to tell the filesystem inside your VM that the disk grew. On Cloudinit-enabled VM, there's an auto-grow parameter that is checking at each boot if the disk was extended, and will automatically do it for you. But again, that's inside the VM. Keep in mind: it's not the job of the virtualization system to deal with what's inside the VM
  • how to see which user created a vm snapshot?

    2
    0 Votes
    2 Posts
    322 Views
    ronivayR
    Settings -> audit. Assuming you have it enabled. If not, nowhere afaik.
  • 0 Votes
    3 Posts
    1k Views
    A
    @Darkbeldin I totally missed that.... I know I have used it before. It must be a long week already. Thanks.
  • Netdata plugin

    12
    0 Votes
    12 Posts
    1k Views
    olivierlambertO
    That would be nice if you open a support ticket with a support tunnel so we can take a look remotely
  • No Hosts Available When Creating New VM

    5
    0 Votes
    5 Posts
    5k Views
    K
    @olivierlambert Thanks for that information, will use it next time I run into the issue. Before I read your above reply, I was poking around and noticed that the only SR I had added was disconnected, somehow. So I researched into it and discovered that this was my own doing. Without going into too much detail, I had converted my Active Directory environment from a Zentyal server to a Windows Server and I was hosting the SMB share on the old domain controller. So I had made a DNS error which was causing the SR to not be reachable from the XCP-ng host. So I deleted the SR and recreated it and viola I was able to create the VM. Honestly, I'm not sure how the two are connected since I'm not storing any disks on this SR; I only use it for ISOs which I mount into the newly created VM to install an OS and then I eject it. Long story short, my problem is solved but I'm still confused as to how it happened.
  • Pool Metadata Backup in XO throwing a Redis Configuration Error

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    olivierlambertO
    As stated in the big warning yellow box here in the official doc: https://xen-orchestra.com/docs/community.html#report-a-bug Closing then
  • Rolling Snapshot not work on xo-server 5.103 and xo-web 5.104

    Solved
    3
    3
    0 Votes
    3 Posts
    245 Views
    L
    @olivierlambert I'm rebuild to xo-server 5.103.1, It's working now ,thanks [image: 1665913661236-9e807578-8296-4fc9-aa81-8afaf1e4f52b-image-resized.png]
  • Editing a Remote always fails

    7
    0 Votes
    7 Posts
    694 Views
    florentF
    @mjtbrady compression is used ( brotli, fastest mode by default) There is a problem on the size reported especially with encryption. I will add a task to the backlog to fix it (there is padding with encryption, that complexify the maths)
  • Storage not connecting, VMs stuck in state and unable to get back.

    14
    2
    0 Votes
    14 Posts
    4k Views
    olivierlambertO
    Indeed, if your other hosts are somehow dead/unresponsive from XAPI perspective, ejecting them from the pool is an option to get your master booting those VMs
  • Restore File - Long filenames not displayed correctly

    8
    1
    0 Votes
    8 Posts
    793 Views
    M
    @pdonias I am puzzled. What do you see? To be clear there are two problems. The selected directory truncates the directory name at around 46 characters ("/var/lib/docker/containers" in my original screen shot isn't truncated because it isn't that long). "Long" file/directory names in the "Select a file" drop down do not display correctly. Once a file has been selected, the "Selected files/folders" does show it in a scrollable "widget" that can then be used to see the full file name. My screen shots are from Chrome on Fedora. I normally use Fedora/Firefox which has the same issues. I set up the following as a test. Filename lengths are 10-80 characters long. root@debian42:~/testdir# pwd /root/testdir root@debian42:~/testdir# ls -l total 0 -rw-r--r-- 1 root root 0 Oct 7 09:50 1234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 12345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 1234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:50 12345678901234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:51 123456789012345678901234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:51 1234567890123456789012345678901234567890123456789012345678901234567890 -rw-r--r-- 1 root root 0 Oct 7 09:51 12345678901234567890123456789012345678901234567890123456789012345678901234567890 Filename lengths 10-50 display. Filename lengths 60-80 do not. [image: 1665091374720-screenshot-from-2022-10-07-10-22-26.png]
  • Exports OVA Timeout...

    37
    0 Votes
    37 Posts
    10k Views
    S
    @olivierlambert i did update xoa again but no dice, i was wanting to export a couple VM's and do a head to head iscsi I/O test between vmware and xcp on identical hardware but not having much luck trying to get my VM's out of xcp. Guess I'll have to wait for this to work possibly.
  • Email Notification Alerts

    8
    0 Votes
    8 Posts
    1k Views
    olivierlambertO
    You can open an issue on XCP-ng repo here: https://github.com/xcp-ng/xcp/issues Just check before if you can already have the temps from the dom0
  • Error: couldn't instantiate any remote

    33
    0 Votes
    33 Posts
    7k Views
    olivierlambertO
    Oh wow, you were lucky indeed! Happy to know you are safe
  • Restore fails with import_error

    9
    0 Votes
    9 Posts
    808 Views
    H
    @olivierlambert Thank you Olivier, posting it here can maybe help somebody else who does the same mistake
  • XO Backup Failing - Possibly to due Local Disks and loopback issues?

    7
    0 Votes
    7 Posts
    827 Views
    DanpD
    @MichaelCropper said in XO Backup Failing - Possibly to due Local Disks and loopback issues?: Job canceled to protect the VDI chain This usually indicates that there are VDIs that haven't coalesced. Check the "unhealthy VDIs" section of Dashboard > Health.
  • XO Remote mount.nfs: access denied by server while mounting

    26
    0 Votes
    26 Posts
    8k Views
    P
    @daninmanchester Thanks so much - this is the exact same problem I had, which was further complicated by running XO in Docker running on the OMV host exporting the NFS shares. So basically you just built a small XO VM instead of running it in Docker? I had originally been thinking of making a small VM to run XO in a container there - just because Docker containers are super easy to keep updated and I could run some other orchestration-y stuff there too, like Rancher - but if you're saying that's a non-starter I'll just bite the bullet and build a tiny VM dedicated to XO and be very grateful to you for having saved me a lot of frustration.
  • Wrong paths at pool's storage

    1
    1
    0 Votes
    1 Posts
    114 Views
    No one has replied
  • Remove xocloudconfig disk with xo-cli

    6
    0 Votes
    6 Posts
    758 Views
    olivierlambertO
    @slax we might get this upstream in few weeks