1. Home
  2. Xen Orchestra

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...

    91 Topics
    769 Posts
    olivierlambertO
    Question for @pdonias

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

    376 Topics
    4k Posts
    olivierlambertO
    Check dmesg, there's something blocking the mount listing. An old ISO SR maybe?

  • 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
    323 Posts
    D
    @Cyrille I am seeing /sys/hypervisor/uuid matching dmidecode's Serial Number matching VM ID in xen orchestra. dmidecode's UUID however is different from those three.
Log in to post
Load new posts
  • Z

    Backup a VM with all its snapshots?

    14
    0 Votes
    14 Posts
    4k 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
    10k 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
    2k 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
    703 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
    963 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
    1k 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
    691 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
    3k Views
    olivierlambertO
    Good news then
  • A

    New and exciting backup errors

    7
    0 Votes
    7 Posts
    1k 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
    340 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
    424 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
    587 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
    181 Views
    No one has replied
  • L

    XOA not reachable after reboot

    2
    0 Votes
    2 Posts
    318 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
    1k 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
    3k 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
    1k 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
    1k 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
  • A

    Broken backup logs

    bugs planned
    18
    0 Votes
    18 Posts
    2k Views
    A
    @julien-f Thanks. I'll post an update if I hit the problem again.
  • C

    Generic Error When Running S3 Backups to Minio on Latest XO Build

    2
    0 Votes
    2 Posts
    314 Views
    A
    @creoleMalady This does not help you, but my setup works with MinIO S3 (current version minio_20220607003341.0.0_amd64.deb) and current XO commit a5e9f. I'm running XO commit 379e4 (June 2nd) and it has been working correctly with Wasabi. I updated XO to commit a5e9f (current master) on a second server and backup still works for me to MinIO.... Delta Backup as a full and as a delta with and without merge.