Subcategories

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

    431 Topics
    3k Posts
    M
    @itservices Thanks 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
  • No "new" Tab

    15
    2
    0 Votes
    15 Posts
    2k Views
    I
    @tony I removed the 2nd XOA... I think that's the reason I'm lagging but now everything is smooth...
  • Detached backups and snapshots with commit '2aed2fd53'

    5
    2
    0 Votes
    5 Posts
    804 Views
    J
    Makes sense now that you mention it... Perhaps I should have realized that because obviously the backups only run on my primary XO instance. Thanks!
  • xo-cli vm.create from bash fails

    2
    0 Votes
    2 Posts
    542 Views
    L
    Solved: you need to use the template id, not the uuid.
  • xo-cli data limit ??

    3
    0 Votes
    3 Posts
    539 Views
    L
    I'm just guessing here, but maybe something like this? xo-cli --list-objects type=VM power_state=Halted | jq -r ".[].name_label"
  • Creating schedules to run on specific days.

    12
    0 Votes
    12 Posts
    2k Views
    badrAZB
    Yes, backup jobs require attached schedules to be executed properly.
  • This topic is deleted!

    1
    0 Votes
    1 Posts
    7 Views
    No one has replied
  • Continuous vm replication or VM copy through XOA fails on WAN

    1
    0 Votes
    1 Posts
    328 Views
    No one has replied
  • NFS Storage added through Center

    6
    0 Votes
    6 Posts
    4k Views
    M
    Hi @tony yes I understand that, actually I made a post a while back spanning different aspects of the XOA and where I feel Center is more intuitive but as suggestion for XOA improvement if anyone cares to consider it. Regarding the adding of SR's to pools, I leave my suggestion here, have a selector for pool instead of host, it'd be more intuitive imho. Cheers all.
  • Changed Block Tracking

    9
    0 Votes
    9 Posts
    2k Views
    akurzawaA
    Becouse xoa backup is painfully slow... it's good for CR but for full vm backup, let's say it's unsuitable... on my 1Gb lan, full vm backup (DR or Copy) from xcp1 to xcp2 I have about 10-15Mb/s. This is the topic I've asked many times on this forum. And guys from vProtect brag that the speed im much better on their soft due to CBT not vhd delta - which I'll check in a while.
  • Question: USB filters on XCP VM's?

    xenserver ethernet xenorchestra usb vms
    2
    0 Votes
    2 Posts
    935 Views
    T
    AFAIK, you have to do manual passthrough for USB so if you want to attach ethernet dongle to a VM, you plug it in the host and turn off the VM, passthrough the USB to the VM, start the VM, never do snapshot of this VM as it will fail.
  • Orphan VDIs after every backup

    7
    1
    0 Votes
    7 Posts
    1k Views
    J
    @badrAZ I've rebuilt XO and confirm that the suspended VDI snapshots are no longer listed as orphans, thanks!
  • vm.set not working for int

    4
    0 Votes
    4 Posts
    598 Views
    julien-fJ
    Hi, sorry for the delay! Please read xo-cli's documentation, you need to use JSON when you want to pass non-string values: xo-cli vm.set id=89517372-b45b-ca36-4c51-dd17c0e760c0 CPUs=json:3
  • Specify a username and password for XOA backups

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    You can map root to a local user you created on the syno (so it's all on NFS server side configuration)
  • XOCE misidentifing Orphaned Snapshots with XCP-ng 8.1

    Solved
    18
    1
    0 Votes
    18 Posts
    3k Views
    badrAZB
    @olivierlambert I've created the dedicated Github issue
  • Backup reports on Microsoft Teams

    Solved
    9
    0 Votes
    9 Posts
    2k Views
    olivierlambertO
    @gskger said in Backup reports on Microsoft Teams: @olivierlambert Thanks - that is what I like about this forum and XCP-ng: learn and share Exactly, but I'm really happy to see this becoming more and more common here. That's a good sign for this community
  • Vm.create unable to create vm using xo-cli

    13
    0 Votes
    13 Posts
    2k Views
    B
    xo-cli vm.set id=89517372-b45b-ca36-4c51-dd17c0e760c0 CPUs=3 Ă— invalid parameters property @.CPUs: must be integer, but is string
  • TLS failure during VxLAN creation

    9
    0 Votes
    9 Posts
    2k Views
    BenjiReisB
    Glad to hear it! There were probably an issue when updating the SDN controller's TLS certificate. The reload had solved it. Regards!
  • XOA High CPU / Single Core

    7
    1
    0 Votes
    7 Posts
    2k Views
    olivierlambertO
    No problem Proxy code will help a lot when merged in your main XO!
  • VM Backup failure

    Solved
    9
    1
    0 Votes
    9 Posts
    1k Views
    olivierlambertO
    Don't worry: if there's stuff to correct in the PR, the review process is made for that
  • VM migration stuck at 100%

    3
    0 Votes
    3 Posts
    3k Views
    J
    I ended up restarting the toolstack, which caused all of the migrating VMs to be in an error state, as they were halted but the system thought they should be running. I couldn't perform any actions on them. VM_BAD_POWER_STATE(OpaqueRef:f1f14751-cbc8-4a86-b98f-9e980b2b0d00, Running, Halted) After restarting the toolstack on all the hosts in the pool, they finally showed up as powered off and I was able to get them back up and could migrate them. Is there anywhere I can look to see why the migration got right to the doorstep and stopped?