1. Home
  2. Xen Orchestra

Subcategories

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

    481 Topics
    4k Posts
    olivierlambertO
    No problem, this is always good to have feedback and cases showing an error and the explanation

  • ACLs, Self-service, Cloud-init, Load balancing...

    106 Topics
    867 Posts
    olivierlambertO
    Question for @Team-XO-Backend

  • All XO backup features: full and incremental, replication, mirrors...

    525 Topics
    6k Posts
    acebmxerA
    @msupport - Looks like veeam is still working with your on your issues. While veeam has pushed me off to vates / xen. @poddingue - Any updates from Vates about these issues? Is it possible the least patches just pushed might help with either mine or @msupport's issue? Update - Just got a reply back from veeam ... As per internal testing, I’m escalation this to the next tier Regards

  • Everything related to Xen Orchestra's REST API

    87 Topics
    650 Posts
    A
    @poddingue Borrow away - "smoke alarm" is a better name for it than anything we had, so we might borrow it right back. Since you mentioned reading the matrix - here is the classification you would be reading, straight from the file: grep access: dadl/xen-orchestra.dadl | sort | uniq -c 49 access: admin 21 access: dangerous 122 access: read 75 access: write 122 of the 267 tools are plain read - that is the entire surface a review-capped agent gets. The other 145 exist in the same file, but for that agent they might as well not. The whole security taxonomy is greppable plaintext - which is rather the point of a declarative format. And if anything in the matrix looks wrong or missing, this thread is exactly the right place - real-world corrections are how it improves.

  • Terraform, Packer or any tool to do IaC

    51 Topics
    472 Posts
    JeremyLARDENOISJ
    New releases! Terraform Provider Xen Orchestra v0.40.0 This new release allows users to import VMs directly from Xen Orchestra into Terraform without recreating it or modifying manually the Terraform state. There is still some drift when importing it, but nothing that changes the real state of VM and we are currently on it! https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.40.0 Golang SDK for Xen Orchestra v1.17.0 v2 The network service is now available from the v2 client! You can now create, get and delete your network directly from it! v1 & v2 The template value in VM struct params has been fixed, We can now get the template id directly from it. https://github.com/vatesfr/xenorchestra-go-sdk/releases/tag/v1.17.0
Log in to post
Load new posts
  • E

    how do i migrate VM storage to a different SR

    3
    0 Votes
    3 Posts
    3k Views
    E
    @olivierlambert thanks
  • GheppyG

    tasks not sowing in XOCE

    8
    0 Votes
    8 Posts
    2k Views
    rajaa-bR
    Hello, we will take a look into that and keep you posted.
  • Z

    Backup a VM with all its snapshots?

    14
    0 Votes
    14 Posts
    6k Views
    G
    @Zevgeny For a few snapshots it's fine - the issue comes when you have large numbers. Most of my first-hand experience with this specific issue comes from Hyper-V but the logic applies here. This is from VMware but the concept is the same and has some good reading on snapshots in general. Running a virtual machine on a snapshot for extended periods of time can cause instability and data loss. https://kb.vmware.com/s/article/1015180 The underlying issue stems from the nature of snapshots. With none you have a single VHD containing all of the data for the VM, once you take a snapshot a new delta VHD is created with all new data written going forward from the time of the snapshot. So, in order to have a complete VM you have the original VHD + the delta VHD. This is fine in smaller numbers, but once you start having 10, 15, 20+ snapshots, every one of those represents an additional VHD in the chain. This results in performance degradation because you're reading from multiple potential files as only new data is written to the deltas. This is actually from XO's blog: https://xen-orchestra.com/blog/xenserver-coalesce-detection-in-xen-orchestra/
  • J

    Xen Orchestra Community Edition - Registration

    xenorchestra
    14
    0 Votes
    14 Posts
    13k Views
    G
    Happy to do baby steps If / when you guys add some kind of "register" option to get a count on things I'd add my instance(s), as long as it doesn't break the existing install / upgrade scripts at least! Generally I have no issues with just clicking it away since I'm the only one that sees it. If it were a viable option sometime in the future, those would be my ideal "features". I've really enjoyed using XO coming from ESXi / vCenter at work and formerly running my home lab. Your vision of support is similar to Nutanix's which is partially why we went their route for our server overhaul and I think it's excellent. I'm hoping by the time we're due for a refresh the hyper-converged offering is fleshed out and production ready. Though I would miss my integrated firmware upgrades.
  • J

    Backup with USB passthru workaround?

    feature in backlog
    8
    0 Votes
    8 Posts
    4k Views
    J
    @olivierlambert Yes this is really great. I have a windows box where I experiment with bluetooth a bit and having backup on this machine at least once a week or so feels very good I think I think it also makes sense that a machine that needs to be taken down in order to make backup also probably will need another backup schedule.
  • D

    Best way to schedule backups hourly, daily, weekly, monthly without overlap?

    Solved
    3
    1
    0 Votes
    3 Posts
    1k Views
    D
    @ronivay very good point thank you! I guess hourly is excessive when snapshots are available. Will just schedule hourly snapshots instead as the main point is to be able to revert in the event of a breaking change.
  • A

    Strange backup error. false !== true

    11
    0 Votes
    11 Posts
    2k Views
    A
    @julien-f Restore showed that there were backups even when it said it failed.... I did not test one, sorry. I deleted the snapshots and old backup data which forced a full backup to S3 and XO was happy. A delta backup after that was also successful.
  • K

    Host Patch Installation Failure | "global name 'commmand' is not defined"

    Solved
    6
    0 Votes
    6 Posts
    2k Views
    K
    @olivierlambert Aaah, thanks Olivier. Still learning. Great product by the way. Hoping I can get comfortable with it enough to make a recommendation to my company.
  • MilitaryNerdM

    At a loss on network config chicken/egg

    3
    0 Votes
    3 Posts
    1k Views
    fohdeeshaF
    @MilitaryNerd Have you restarted the host since removing this bond? It's reporting that bond0 is still attached to an OVS bridge, so it may need a reboot. You can also ensure the bond is really gone by running xe bond-list, it should return nothing. You could also still have the bond PIF existing or other networks using the old bond, check that you don't have any PIFs with device ( RO): bond0 listed when running xe pif-list
  • Tristis OrisT

    unhealthy VDI chain

    21
    0 Votes
    21 Posts
    6k Views
    olivierlambertO
    Good news then
  • A

    New and exciting backup errors

    7
    0 Votes
    7 Posts
    2k Views
    A
    @andrewreid Not that this helps with your error, but my nightly S3 delta backups to Wasabi have been working just fine. I'm using XO source and keep mostly up to date with master. S3 and NFS are different backup formats so NFS working does not mean S3 will work. Sometimes Wasabi causes failures but not recently and not that last more than a few VMs in one night. The next backup run (manual restart or next nightly) seems to work correctly. I force a full backup every 3 months just to make sure I have a good checkpoint in case undetected corruption creeps into the delta data. Plus I have replication and other backups. I did have a problem once (not exactly yours) with a VM and just deleted the S3 backup data which forced a full backup again. Sucks because you don't have the weeks of deltas anymore. Error #3 (date-time) is strange. May be a backblaze issue. You could create a new S3 remote to backblaze (new bucket or directory) and test one failing VM backup to the new remote and see if it works (and works again for delta). You could set the retention low to test merge too. I have a setup like this with a local MinIO server for S3 testing and local backups.
  • mauzillaM

    Backups not starting after failed NFS mount

    4
    0 Votes
    4 Posts
    811 Views
    olivierlambertO
    haha that's exactly the purpose of the remote test button No grand mastery, just experience
  • K

    Moving backups to another remote?

    3
    0 Votes
    3 Posts
    1k Views
    K
    @olivierlambert I want to move them on NFS in order to be able to backup later from NFS to S3 in more granular way Generally, we are talking about XO - NFS. S3 would be out of XO.
  • S

    Register instance of XO Running on Hyper-V

    4
    0 Votes
    4 Posts
    1k Views
    julien-fJ
    @someone2b Just install this work-around xenstore-read with the following commands and hopefully it will work. sudo -s cd /usr/local/bin curl -O https://gist.githubusercontent.com/julien-f/a6f98de3bd5a775f3f04b2fa14a9a102/raw/xenstore-read chmod +x xenstore-read
  • K

    Second Pool Host Network 0 doesn't work for VMs

    1
    0 Votes
    1 Posts
    509 Views
    No one has replied
  • L

    XOA not reachable after reboot

    2
    0 Votes
    2 Posts
    503 Views
    olivierlambertO
    Hi, This is documented. https://xen-orchestra.com/docs/xoa.html#first-console-connection
  • K

    XCP-ng logs in XOA - where to find

    3
    0 Votes
    3 Posts
    2k Views
    K
    Just if somebody else is searching for the same thing, although it is not directly related to XOA: If you want to get these alerts by mail and you are not using XCP-ng-Center, you can activate them with: xe pool-param-set uuid=pool-uuid other-config:mail-destination=mail@example.com xe pool-param-set uuid=pool-uuid other-config:ssmtp-mailhub=mailserverip:port KPS
  • G

    Create VM Error SR_BACKEND_FAILURE_1200, No such Tapdisk.

    16
    0 Votes
    16 Posts
    6k Views
    ronan-aR
    @geoffbland No problem. It's the first time I see this error with tapdisk (and it's it's even more surprising to have it on this type of SR...). It had all been working fine and I had not changed anything on the share - it just stopped working In this case, maybe there was a problem with the XAPI, a lock on the device or something else. Not easy to find the cause without remote access. Don't hesitate to ping us if this problem comes back.
  • mauzillaM

    Migrating large disk - any risks?

    6
    0 Votes
    6 Posts
    2k Views
    olivierlambertO
    It's more a less that. In short, the new disk is created on both sides, and blocks mirrored on both sides. First, the read only "parent" VDI with frozen blocks is copied, when it's done, the VM is briefly paused, the memory migrated to the destination and then unpaused on destination. Consequently, only the blocks written during 11 hours will use space for new blocks on the source SR (and destination, since it's mirrored).
  • S

    All imports fail with error

    6
    0 Votes
    6 Posts
    2k Views
    julien-fJ
    @sbz71 The stable channel should not have the issue, not sure when we'll release a fix for latest. If you have an XO subscription, you can open a support ticket and a support tunnel and we'll be able to patch your install My bad, I misunderstood the question