1. Home
  2. Xen Orchestra

Subcategories

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

    482 Topics
    4k Posts
    I
    @poddingue Yes multipath is enabled and we have two target ips. When I scan the target it calls the sr.probeIscsiIqns method and return the iqns in the dropdown as *(ip,ip) and on the select of *(ip,ip) it calls sr.probeIscsiLuns method. Both method take time to return the response. 90+ LUNs will be listed in the Lun dropdown after 4-5 minutes. Then On selection of LUN with respect to the id it calls sr.probeIscsiExists to validate the LUN, this method also take 1-3 minutes. After all this on create button click if then calls a method sr.createIscsi . This takes too much time too. I have a pool of 3 hosts and all servers have verified connectives to the SAN Storage. If you need any information regarding this, I will be happy to share.

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

    106 Topics
    869 Posts
    T
    @mpiton Thanks for looking into this, I guess it wasn't apparent that I needed to click the Save Configuration button for that plugin. I did that and confirmed that the secret now survives an xo-server restart. Thanks again!

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

    526 Topics
    6k Posts
    poddingueP
    That's great news, thanks, @christopher-petzel !

  • 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
  • J

    Is it possible to do this with VM list filters?

    Solved
    6
    0 Votes
    6 Posts
    1k Views
    J
    @Danp You're right, I missed the question mark on it when I tried it before. With the question mark, it works. Thank you for your help.
  • X

    Logs Partition Full

    59
    0 Votes
    59 Posts
    45k Views
    X
    How can I determine which VM is causing this problem? Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830066:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830198:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830311:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830458:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830605:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830712:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830797:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.830885:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831006:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831094:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831185:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831260:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831333:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831407:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831478:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.831551:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884264:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884519:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884615:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.884721:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.923891:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924054:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924207:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924319:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924505:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924675:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924803:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.924913:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927026:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927185:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927303:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927436:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927657:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927772:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927903:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.927993:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928136:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928255:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928396:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail2 Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.928479:xen_platform_log xen platform: XENBUS|CacheCreateObject: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932786:xen_platform_log xen platform: XENVIF|__AllocatePages: fail1 (c0000017) Nov 1 13:05:00 df-c01-node04 qemu-dm-25[29890]: 29890@1730462700.932906:xen_platform_log xen platform: XENVIF|ReceiverPacketCtor: fail1 (c0000017)
  • P

    Bug?? Tree view XO v6

    Solved
    3
    1
    0 Votes
    3 Posts
    619 Views
    P
    @Danp Yes of course You are correct I moved it to local storage a few weeks ago My bad
  • K

    Filtering multiple hosts by name

    Solved
    5
    0 Votes
    5 Posts
    1k Views
    olivierlambertO
    That's the right way, yes Enjoy!
  • S

    Building Xen Orchestra 6 from scratch

    2
    0 Votes
    2 Posts
    629 Views
    olivierlambertO
    Hi, From the XO root folder, just do a yarn run turbo run build --filter @xen-orchestra/web and then access the XO URL with /v6 in the end.
  • L

    [SOLVED] Missing Plugins

    2
    0 Votes
    2 Posts
    598 Views
    L
    @llabtaem This issue has been resolved. I just needed to rebuild Xen Orchestra after adding the symbolic links. Then the plugins registered and I can now see them in the console.
  • humitoH

    Error restore backup

    7
    0 Votes
    7 Posts
    1k Views
    humitoH
    @olivierlambert said in Error restore backup: No I mean the file level restore feature from XO. If it all worked, I'm curious to understand why you had this issue in the first place. Did you restore the entire chain? We had to restore the entire VM as a new instance from Xen Orchestra using the delta backup. However, the same error occurred with each restore point. So, we manually copied the backup files from XOA and imported them.
  • D

    This topic is deleted!

    1
    0 Votes
    1 Posts
    5 Views
    No one has replied
  • I

    Forgot password for the webgui

    11
    0 Votes
    11 Posts
    4k Views
    J
    @peder Thanks, it works
  • A

    Free Xen Orchestra?

    15
    0 Votes
    15 Posts
    24k Views
    olivierlambertO
    Thanks for your feedback, we'll improve the doc.
  • B

    XOA says not up to date after 8.3 upgrade

    4
    0 Votes
    4 Posts
    974 Views
    olivierlambertO
    Check your NTP is correctly configured. For the rest, it works then
  • M

    XCP-ng Tools Storage contains VDIs I’m unable to Destroy

    Solved
    9
    0 Votes
    9 Posts
    2k Views
    M
    @gduperrey said in XCP-ng Tools Storage contains VDIs I’m unable to Destroy: It seems that it is possible to clean old isos manually, via the command line, as explained in this forum post: https://xcp-ng.org/forum/post/15703 Wau!!! That actually works like charm! Thank you sooooo much!
  • S

    Project Pyrgos

    12
    0 Votes
    12 Posts
    5k Views
    olivierlambertO
    We had to reorg a bit the team, with the creation of an internal devops team. We hope to get some cool news in the following months
  • mauzillaM

    Benchmarks between XCP & TrueNAS

    20
    1
    0 Votes
    20 Posts
    9k Views
    mauzillaM
    @andrewperry yes, we replicate TrueNAS to a "standby" TrueNAS using zpool / truenas replication. Our current policy is hourly. We then (plan) to do Incremental replication of all VM's to a standby TrueNAS over weekends giving a 3 possible methods for recovery. Currently we're running into a major drawback with VM's on TrueNAS over NFS (specifically VM's that rely on fast storage such as databases and recordings). We did not anticipate such a huge drop in performance having VHD files over NFS. We're reaching out to XCP to ask them to give us some advice as it could likely be in part due to customization we can make.
  • W

    Add multiple pool/host to XOA

    2
    1
    0 Votes
    2 Posts
    726 Views
    A
    @wildones It's good that the XCP hosts can reach each other, but that's not enough. XOA needs to reach all the hosts too. You may want to use an XO proxy to manage remote locations. Please read the XO proxy guide.
  • mauzillaM

    Urgent: how to stop a backup task

    10
    0 Votes
    10 Posts
    6k Views
    olivierlambertO
    The latest release blog post, in the Backup section: https://xen-orchestra.com/blog/xen-orchestra-5-99/
  • P

    LDAP Plugin - Syncing Groups from Windows AD (Server 2016) HELP

    7
    1
    0 Votes
    7 Posts
    2k Views
    olivierlambertO
    No problem, happy to see people providing solutions in here! Kudos for that. Would you be interested to contribute to our doc to help even more people at once?
  • P

    XOA / NFS ISO - Unable to create on IPv6 NAS

    5
    0 Votes
    5 Posts
    960 Views
    P
    @BenjiReis I tried to fill in the IP address with brackets, but then the discovery of the NFS shares fails. With regular SRs, it works fine without using brackets.
  • ForzaF

    Local mirror for XOA and XCP-ng updates

    3
    0 Votes
    3 Posts
    647 Views
    ForzaF
    @olivierlambert thanks. I'll read through the documentation and maybe contact support about this.
  • mauzillaM

    Incremental Replication Health Testing?

    4
    0 Votes
    4 Posts
    878 Views
    olivierlambertO
    In fact it's already possible In your replication job: Edit the schedule, check "Health check" box. Target the same SR than your VM are replicated too And voila!