Subcategories

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

    431 Topics
    3k Posts
    itservicesI
    Hi @McHenry . You should obfuscate the IP address in your first screenshot. Also check your profile and private chat Hope everyone had a joyful Christmas and I wish everyone the best for 2026. Regards, Marc
  • ACLs, Self-service, Cloud-init, Load balancing...

    97 Topics
    818 Posts
    olivierlambertO
    October release fixed it
  • All XO backup features: full and incremental, replication, mirrors...

    444 Topics
    4k Posts
    A
    I have opened a support ticket and tunnel is open - Ticket#7749796 here is a section of the error log. I have rebooted XOA and rebooted the Proxy but yet the job still remains hung. Maybe i didn't reboot them in the correct order? As stated support ticket and tunnel are open. { "id": "1766901730734", "message": "snapshot", "start": 1766901730734, "status": "success", "end": 1766901734483, "result": "a995b25e-ab77-a217-fccd-7e8a1d06df57" }, { "data": { "id": "3022703c-5029-4ac3-bda1-3a76c6634a39", "isFull": true, "type": "remote" }, "id": "1766901734494", "message": "export", "start": 1766901734494, "status": "interrupted", "tasks": [ { "id": "1766901737246", "message": "transfer", "start": 1766901737246, "status": "interrupted" } ] } ], "infos": [ { "message": "Transfer data using NBD" } ] } ], "end": 1766901871318, "result": { "url": "https://10.120.20.119/api/v1", "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out\n at ClientRequest.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:61:25)\n at ClientRequest.emit (node:events:518:28)\n at ClientRequest.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at TLSSocket.emitRequestTimeout (node:_http_client:849:9)\n at Object.onceWrapper (node:events:632:28)\n at TLSSocket.emit (node:events:530:35)\n at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17)\n at TLSSocket.Socket._onTimeout (node:net:595:8)\n at listOnTimeout (node:internal/timers:581:17)\n at processTimers (node:internal/timers:519:7)" schedule.runSequence { "schedules": [ "3a677031-4eb9-427a-99fc-22afa411b745", "cadef7b9-2541-4850-9bfd-871d9602c6bb", "599d9321-7081-4840-9617-d31762d4764c", "828b5e60-4302-455c-94f1-479a8001f955" ] } { "url": "https://10.120.20.119/api/v1", "message": "HTTP connection has timed out", "name": "Error", "stack": "Error: HTTP connection has timed out at ClientRequest.<anonymous> (/usr/local/lib/node_modules/xo-server/node_modules/http-request-plus/index.js:61:25) at ClientRequest.emit (node:events:518:28) at ClientRequest.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17) at TLSSocket.emitRequestTimeout (node:_http_client:849:9) at Object.onceWrapper (node:events:632:28) at TLSSocket.emit (node:events:530:35) at TLSSocket.patchedEmit [as emit] (/usr/local/lib/node_modules/xo-server/node_modules/@xen-orchestra/log/configure.js:52:17) at TLSSocket.Socket._onTimeout (node:net:595:8) at listOnTimeout (node:internal/timers:581:17) at processTimers (node:internal/timers:519:7)" backupNg.runJob { "id": "bb0adfc7-93b9-45c9-a90f-7aa327f95a05", "schedule": "3a677031-4eb9-427a-99fc-22afa411b745", "vms": [ "4c2fb974-f2d5-b0fb-7385-1683e0275ef2", "025f71ff-ecb2-9d0c-7692-f7005d22c659", "78aecc3d-4817-a11c-04b4-9d0f49f8736e", "9f36a8c5-c988-8546-b0f9-30ac9d0a5015", "db89c6f0-3330-7180-b5e4-7f2f36a241e6", "e5c656bb-8bb2-461e-a801-402ae150d022" ] } { "code": -32000, "data": { "jobId": "bb0adfc7-93b9-45c9-a90f-7aa327f95a05", "stack": "Error: job is already running at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:96:25 at file:///usr/local/lib/node_modules/@xen-orchestra/proxy/app/mixins/backups.mjs:114:20 at processTicksAndRejections (node:internal/process/task_queues:95:5)" },
  • Everything related to Xen Orchestra's REST API

    75 Topics
    571 Posts
    F
    @MathieuRA Thank you, perfect Br,
  • Terraform, Packer or any tool to do IaC

    45 Topics
    427 Posts
    CyrilleC
    Terraform provider release v0.37.0 Enables the secure boot parameter for the VM resource Terraform provider release: https://github.com/vatesfr/terraform-provider-xenorchestra/releases/tag/v0.37.0
  • XO Load Balancer

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    Every HA or load balancing setup is too take it seriously. Consequences might be high, so use it only if we really know what you are doing.
  • xo-cli deploy VM using ssh-key parameter

    Solved
    4
    0 Votes
    4 Posts
    830 Views
    kirovtomeK
    @julien-f @olivierlambert Thanks guys! You can close this one.
  • Snapshot with memory - orphaned suspend_image

    1
    0 Votes
    1 Posts
    422 Views
    No one has replied
  • VM get Halted Everytime I start them

    4
    3
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    You need to enable hardware assisted virtualization in your hardware (in the BIOS).
  • Latest XCP-ng 8.2: Cannot import XVA, even with latest XOA

    19
    0 Votes
    19 Posts
    4k Views
    B
    @olivierlambert Hah, indeed it was! CIFS is totally unstable, but I was able to get NFS working with these configs: mount -o vers=3,soft,mountproto=tcp [IP]:/share /mnt/nfs_share/backup.xva
  • Feature request - Configurable columns in list views

    3
    0 Votes
    3 Posts
    643 Views
    pdoniasP
    @d1rtym0nk3y Thanks for the feedback! This is actually something that we had in mind. It will probably have to wait for the next major version of XO, though.
  • Monitoring disk usage of thin provisioned disks

    15
    1 Votes
    15 Posts
    5k Views
    olivierlambertO
    It's because it's a fake, edited to show how we would like to have it If you need that, please open an issue in XO bugtracker, only after checking there isn't an existing same request
  • Cannot see virtual Machine consoles...

    Solved
    9
    1
    0 Votes
    9 Posts
    4k Views
    NickyMN
    @dreday said in Cannot see virtual Machine consoles...: @FPIT I would say to further troubleshoot the limited connectivity issues first... A few things that jump to mind right away Does the host have a network gateway address set for the management interface? Are there any firewalls or switch port ACLs blocking traffic? This one is the least likely culprit 3) Is you host management configured to use DHCP?(based on the blank console, though it would not explain the connectivity issues unless DHCP is not providing all necessary information for the network) Option number 3 worked for me. I had initially configured my management console (with public IP) to use DHCP and the other port (with local IP) to use static. When I did reset all connections to use DHCP the consoles came up. Thank you thank you thank you! @DreDay and of course thanks @FPIT for raising the issue. #one
  • Multiple NIC in XOA / XO CE

    Solved
    3
    0 Votes
    3 Posts
    787 Views
    H
    @olivierlambert Thank you again for the answer! I was not using the right search criteria to find this part myself Changed the 'config.toml' file after searching my system (not an XOA but XO CE, so it was in another location then mentioned in the documentation) Restarted and just as expected the GUI was only available on the specified IP
  • Ansible dynamic inventory

    2
    0 Votes
    2 Posts
    588 Views
    olivierlambertO
    We sponsored someone to work on Terraform and Packer. But every contribution is welcome, on Ansible too
  • Help with Xen Orchestra

    6
    0 Votes
    6 Posts
    1k Views
    olivierlambertO
    Sure, you can create a GH issue on XO repository
  • Xen Orchestra proxies - Test Feedback

    31
    0 Votes
    31 Posts
    15k Views
    olivierlambertO
    We are focusing first on getting something correctly integrated from XOA, it doesn't mean it will be exclusive to XOA. It's just we are first focusing on a completely "known" environment (XOA), but I think at some point we'll be able to provide manual setup for people who want to do it from the sources
  • Delta backup - can't restore

    4
    0 Votes
    4 Posts
    942 Views
    tonyp90T
    @julien-f Backup files check found no problems, so I tried to restore again and it works. No changes or updates in XO, no changes on vhd or json files (same dates and sizes). Only think I did was detach and attach backup repository (settings - remotes) which I tried before with no luck.
  • Python3 support?

    12
    0 Votes
    12 Posts
    3k Views
    DanpD
    @julien-f
  • Min static memory fixed?

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    In theory, static min is bundled in the template and you shouldn't use less than that. If you still want to do it, consider it as "advanced", and do it with xe
  • Disable network_usage alarm

    3
    1
    0 Votes
    3 Posts
    667 Views
    olivierlambertO
    pinging @nhanlon
  • VM space used in local storage and base copies

    8
    6
    0 Votes
    8 Posts
    2k Views
    N
    @olivierlambert Dont know why the screenshots were not loading, posting that again With no snapshots and coalesce completed, very very little space used. [image: 1606962162989-captura-de-pantalla-233.png]
  • Feature Request: Allow changing proxy from WebUI in XOA

    6
    0 Votes
    6 Posts
    5k Views
    ForzaF
    @julien-f That explains it. Thanks!
  • XO HUB Templates and Recipes Free vs Premium

    Solved
    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    @maxcerny You shouldn't have any diff, no.
  • Terraform

    4
    0 Votes
    4 Posts
    1k Views
    D
    @ruskofd is right. You should be able to use the cloud_network_config attribute to achieve this. The following code is untested but should launch a vm with a static IP. Please see the xenorchestra_vm resource docs and the cloud-init networking v1 docs for more details. resource "xenorchestra_vm" "static_ip_vm" { .... cloud_network_config = <<EOF network: version: 1 config: - type: physical name: eth0 subnets: - type: static address: STATIC_IP/24 gateway: GATEWAY_IP dns_nameservers: - 8.8.8.8 EOF } Let me know if you have any questions or issues using cloud_network_config, As for the blog post, the VM would have been assigned an ip address via dhcp (assuming the guest OS had cloud-init installed which was true for the VM template in the blog post).