Subcategories

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

    450 Topics
    3k Posts
    W
    @florent And here I was trying to give you the benefit of the doubt ... lol
  • ACLs, Self-service, Cloud-init, Load balancing...

    99 Topics
    828 Posts
    simonpS
    @MajorP93 Hi, In the demo dashboard it is intended yes but these percentages are obtained by dividing the free memory by total memory so changing the dashboard to show GB/GiB should be quite straight forward. I've forgot to add to the initial post that there is a advanced dot md file that describes all the available metrics located in "xen-orchestra/docs/docs". Thanks.
  • All XO backup features: full and incremental, replication, mirrors...

    460 Topics
    5k Posts
    P
    @MajorP93 this was found in the troubleshooting section of the documentation when i tried to optimise my xoa/xoproxies deployments https://docs.xen-orchestra.com/troubleshooting#memory
  • Everything related to Xen Orchestra's REST API

    76 Topics
    578 Posts
    R
    @Pilow tags can work and the path to them is much more succinct. Thanks!
  • Terraform, Packer or any tool to do IaC

    49 Topics
    450 Posts
    nathanael-hN
    @ThasianXi Nice, thanks For now no other question related to the CCM. But I would be very interesting if you have some feedback about the CSI Driver. We'll work on this in the coming weeks. https://github.com/vatesfr/xenorchestra-csi-driver
  • XOCE limit ?

    27
    2
    0 Votes
    27 Posts
    7k Views
    florentF
    @Gheppy I am not an expert on the network part but I can help on the NBD part We added some info in this PR https://github.com/vatesfr/xen-orchestra/pull/6596, it should be merged in this form or another in master in a few days. It will give the user more info on the NBD usage and the cause (misconfiguration, or network error) Then if XO ( or the proxy) can't connect to the host through the NBD (for example with a network filtering/ routing), it will fall back to the reliable (but non parallelizable) api call Finally , the backup done with NBD or the legacy api call will produce exactly the same data so they are compatibles, but using the same target (as in the same directory , same remote and same VMs) for multiple job can lead to complex support tickets with interesting race conditions. I would advise to only use the same remote/directory only if the backups jobs does not concern the same VMs fbeauchamp opened this pull request in vatesfr/xen-orchestra closed feat(@xen-orchestra/backups): more information on nbd backups #6596
  • S3 Remote with encryption: VHDFile implementation is not compatible

    11
    0 Votes
    11 Posts
    2k Views
    florentF
    @cdbessig that's strange Since S3 remote are only able to store blocks, the option is enforced on save ( without any uI) I tested locally and the options seems to be there. Can you show me a screenshot of the backup job configuration ?
  • Base Copy (No active VDI)

    vdi base copy remove
    4
    1
    0 Votes
    4 Posts
    3k Views
    olivierlambertO
    Remember that the point of pro support (to help and guide you to run this setup confidently in production).
  • VM won't start with internal error

    7
    0 Votes
    7 Posts
    1k Views
    DanpD
    What is your process for provisioning a VM? What template are you using?
  • XO reports wrong number of backups

    Solved
    11
    0 Votes
    11 Posts
    2k Views
    codesmakerC
    @julien-f Thanks a lot for the fast answer. I'll update to the latest version and test.
  • Importing OVA - “Device Already Exists”

    24
    0 Votes
    24 Posts
    9k Views
    planedropP
    @trent234 Interesting, good to know. I do know that XCP-ng only officially supports 7 network interfaces, so not really surprised by that. It supports more VHDs though so feel like I shouldn't be seeing this error.
  • XOCE - Config path

    10
    0 Votes
    10 Posts
    2k Views
    K
    @Gheppy I found my issue... The changes, I wanted to test have not been committed to "master-branch". After changing the branch, everything is clear... Thank you for your help!
  • 0 Votes
    7 Posts
    1k Views
    olivierlambertO
    +1, that's the way to go
  • error -104

    21
    0 Votes
    21 Posts
    9k Views
    P
    @tuxen No GPUs were removed. only 2 were added. The only PCIE item removed was a NIC but I didn't remove it from dom0 or assign it to any VMs, it was just in the system.
  • [XO-CE] job.Sequence error - invalid parameters

    xoce jobs
    3
    7
    0 Votes
    3 Posts
    878 Views
    julien-fJ
    I believe this is a known issue (https://github.com/vatesfr/xen-orchestra/issues/5973) that is unlikely to be fixed in XO5. We'll need to wait for @pdonias to be back from holidays to have more info on this. just-333 created this issue in vatesfr/xen-orchestra closed Error on vm.set from Jobs tab in XO web GUI #5973
  • Deleting snapshots and base copies

    18
    1
    0 Votes
    18 Posts
    6k Views
    S
    @sumansaha In summary , I've deleted Orphan VDIs from Dashboard->health . But in deletion, I've maintained the sequence of their age.It has taken 6 hours, though that depends on the VM size.
  • Show me your backup performance

    11
    0 Votes
    11 Posts
    970 Views
    olivierlambertO
    If you do a full every time, it's fine (use no retention or full every time)
  • How to delete unmanaged disks in local storage

    7
    0 Votes
    7 Posts
    5k Views
    olivierlambertO
    You can't delete a base copy. You need to understand how it works before doing dangerous operations. A base copy exists if there's a snapshot. If you have 0 snap and still base copy, it could be either: because the coalesce isn't finished because the coalesce doesn't work In both case, you have to take a look at your SMlog. If you have no idea about it, you should either get pro support or start to read the doc in more details You can start here: https://xcp-ng.org/docs/storage.html#coalesce
  • FYI - Applying 11/3/2022 and 11/4/2022 Commits in XO from Sources

    22
    0 Votes
    22 Posts
    9k Views
    E
    Thanks for sharing
  • Delta Backup broken with commit 45dcb914...

    3
    0 Votes
    3 Posts
    423 Views
    A
    @julien-f The new update seems to be working correctly now. Thanks for the quick update fix. The backup cache fixes/cleanup made a huge difference (improvement). I was trying to figure out what was going on with my backups as they were running but were missing from the restore list. After the cache cleanup, it showed 3-4 times the number of restore points! All the missing stuff and more. It took some time to clean up all the extra stuff, but backups seem to be back on track again.
  • EIO: i/o error, close when making backup over 10 GbE nic.

    2
    0 Votes
    2 Posts
    429 Views
    tjkreidlT
    @anturk What errors do you see in /var/log./SMlog related to this? Have you run ifconfig or netstat to look for network transmission errors? Is this a new setup and if so, are you sure the cables are of good quality? Is this a dedicated NIC or is it part of a VLAN?
  • Backup jobs started to fail after last XOA update

    13
    2
    0 Votes
    13 Posts
    2k Views
    julien-fJ
    @Forza No, it's not possible to add multiple hosts of the same pool to XO.
  • Windows VM - No ram reported?

    Solved
    3
    0 Votes
    3 Posts
    507 Views
    N
    @olivierlambert I blew away the docker container and did a fresh build of XO from source on a *buntu box. Issue resolved itself with that. Must be a bad build in the docker.
  • "an error has occurred" in home -> storage

    xenorchestra
    6
    3
    0 Votes
    6 Posts
    938 Views
    olivierlambertO
    You can't login to our servers with your source version (from Git), you must download the virtual appliance. If you can't access https://xen-orchestra.com internally, then, indeed, you won't be able to register it in the end. But if you managed to clone it from Github, you have some access to outside
  • Monitor Backups - Last backup for VM

    14
    0 Votes
    14 Posts
    3k Views
    julien-fJ
    @KPS You can use xo-cli --list-objects type=VM. Also you should only get the backup logs once and join with the VM list, because backupNg.getLogs is heavy.