Subcategories

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

    365 Topics
    3k Posts
    B
    @Danp THANKS! That did the trick. I was able to clean up after doing that. Thanks so much!
  • ACLs, Self-service, Cloud-init, Load balancing...

    90 Topics
    766 Posts
    D
    @Danp said in Advanced VM settings Logs: Hi Dustin, Yes... these types of actions are recorded in the Audit log (Settings > Audit) if you have access to this feature and have enabled it. Dan Perfect, thanks!
  • All XO backup features: full and incremental, replication, mirrors...

    374 Topics
    4k Posts
    burbilogB
    I have a delta backup job with Full backup interval set to 7. If i look at the backup job results I get this: xoce (legion) Snapshot Start: 2025-07-25 03:02 End: 2025-07-25 03:02 Fiend NFS transfer Start: 2025-07-25 03:02 End: 2025-07-25 03:08 Duration: 6 minutes Size: 23.78 GiB Speed: 73.01 MiB/s Clean VM directory cleanVm: incorrect backup size in metadata Start: 2025-07-25 03:08 End: 2025-07-25 03:08 Start: 2025-07-25 03:02 End: 2025-07-25 03:08 Duration: 6 minutes Start: 2025-07-25 03:02 End: 2025-07-25 03:08 Duration: 6 minutes Type: full It says "full". If i go to backup -> restore, search for this vm, i see "full 2 delta 2" in "Available Backups" column. Yet if i press "restore" arrow i see that two full backups are of 2022 year and it looks dangerous. Documentation says about that setting "For example, with a value of 2, the first two backups will be a key and a delta, and the third will start a new chain with a full backup.". Yet, I see only VERY old full backups... Xen Orchestra, commit 19412 Master, commit 6277a, but it seems that this happens for a long time (i recently updated it to this state and the problem seems to persist ever since I began to use Xen Orchestra in 2022). Do I miss something? Do I really have fresh full backups and these a just labeled "incremental" or what? [image: 1753444452743-xoce.png]
  • Everything related to Xen Orchestra's REST API

    66 Topics
    502 Posts
    lsouai-vatesL
    @StephenAOINS This endpoint is not currently present in our REST API swagger, but we do plan to add it to the list of endpoints. We are currently finalizing the migration of existing endpoints, the next step will be adding new ones. We will keep you informed when it is available. Feel free to come back to us if you want to learn more and follow our blog posts. have a good day
  • Terraform, Packer or any tool to do IaC

    34 Topics
    319 Posts
    olivierlambertO
    No, it's fine, as long the issue contains all the relevant details it's fine
  • Rolling Snapshot not work on xo-server 5.103 and xo-web 5.104

    Solved
    3
    3
    0 Votes
    3 Posts
    232 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
    532 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
    578 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
    8k 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
    979 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
    5k Views
    olivierlambertO
    Oh wow, you were lucky indeed! Happy to know you are safe
  • Restore fails with import_error

    9
    0 Votes
    9 Posts
    625 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
    615 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
    6k 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
    113 Views
    No one has replied
  • Remove xocloudconfig disk with xo-cli

    6
    0 Votes
    6 Posts
    618 Views
    olivierlambertO
    @slax we might get this upstream in few weeks
  • XO Contentious Replication no longer working (commit 3d3b6)

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

    26
    4
    0 Votes
    26 Posts
    5k 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
    4k 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
    580 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