1. Home
  2. Xen Orchestra

Subcategories

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

    408 Topics
    3k Posts
    dthenotD
    @cmanos No problem, glad I could helped. As Olivier also pointed above, it's not an issue anymore when using QCOW2 which is currently in beta, so hopefully it's only a short workaround

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

    96 Topics
    811 Posts
    olivierlambertO
    Indeed, and it's clearly stated at https://docs.xen-orchestra.com/community

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

    417 Topics
    4k Posts
    A
    I had to disable Purge snapshot data when using CBT. Backups are not longer defaulting to full backups.

  • Everything related to Xen Orchestra's REST API

    71 Topics
    555 Posts
    olivierlambertO
    Yes, they are created either: on demand for users when we need in XO 6 Now, XO 6 is becoming the main driver for new endpoint as the UI is providing more and more features.

  • Terraform, Packer or any tool to do IaC

    40 Topics
    380 Posts
    C
    This approach isn’t entirely foolproof since I can’t use a wildcard, and I don’t know how many disks will be attached to the VM. For now, it will never exceed two disks, so I can explicitly include both in the ignore_changes statement. That’s an acceptable solution for us. Thanks for your support.
Log in to post
Load new posts
  • 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
    467 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
    591 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
    780 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
    224 Views
    No one has replied
  • L

    XOA not reachable after reboot

    2
    0 Votes
    2 Posts
    328 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
    4k 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
    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
  • A

    Broken backup logs

    bugs planned
    18
    0 Votes
    18 Posts
    3k 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
    471 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.
  • R

    Install new supplemental pack not work

    7
    0 Votes
    7 Posts
    1k Views
    R
    @olivierlambert last update> I try diferent browser(Firefox) and ISO localy > all working First time I try from Chrome and ISO on remote drive
  • mauzillaM

    Is it possible to migrate from hyper-v?

    2
    0 Votes
    2 Posts
    218 Views
    mauzillaM
    @mauzilla nevermind google to the rescue
  • A

    VM autostart

    4
    0 Votes
    4 Posts
    2k Views
    olivierlambertO
    Try to disable/enable autostart in Advanced section of your VM. That might do the trick.
  • G

    Kudos for the XO User Interface

    2
    1 Votes
    2 Posts
    462 Views
    olivierlambertO
    Hello @geoffbland Thanks for the feedback To be fair, we added that precisely because our community/users asked for it! I wouldn't have thought of this by myself. That's the power of community, and for that, I thank you all!
  • J

    "global name 'commmand' is not defined" while installing patches

    13
    0 Votes
    13 Posts
    2k Views
    julien-fJ
    @olivierlambert This error does not ring a bell to me.
  • B

    Can't create second virtual disk for a VM using XOA

    3
    0 Votes
    3 Posts
    712 Views
    B
    @Andrew thank you , it's NFS mount yes. i perform forget and remount and now is ok, most probably i chose older storage from another host, the menu to select storage for VM showing everything associated with the pool and sometimes this is confusing. Thanks for your comment.
  • S

    Permissions for users to be able to snapshot

    bugs done
    13
    0 Votes
    13 Posts
    3k Views
    olivierlambertO
    That's because doing a snapshot will have consequences on the SR. That's why we restricted the permissions for doing snapshot.