Subcategories

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

    362 Topics
    3k Posts
    tjkreidlT
    @gb.123 You need to do both. After adding the PCI device, you might also need to specifically enable "passthrough" for that device within the VM's settings. It may do it automatically when you add it. Make sure the appropriate NVIDIA driver is also installed on the the VM.
  • ACLs, Self-service, Cloud-init, Load balancing...

    89 Topics
    762 Posts
    olivierlambertO
    Hi, It was never meant to be a 2 ways synchronization plugin. Making it 2 ways considerably raise the complexity of such plugin (because we would need to make configuration for decision on when to take it one way and the other, and each use case is different). I would say: you shouldn't have any IP that's already in Netbox from other source in the IP range that's used for your VMs.
  • All XO backup features: full and incremental, replication, mirrors...

    364 Topics
    4k Posts
    R
    @florent Great work, thanks for the fixes
  • Everything related to Xen Orchestra's REST API

    64 Topics
    492 Posts
    MathieuRAM
    This is normal, as the tasks endpoints are in the old REST API (undocumented by Swagger). We are gradually migrating to the new REST API to document all endpoints.
  • Terraform, Packer or any tool to do IaC

    33 Topics
    309 Posts
    I
    @olivierlambert @nathanael-h @Team-DevOps Please let me know if you have answers for any of the flollowing questions: Why JSON-RPC over websocket regularly returns not expected result for calls and what could be done with it? examples: method xo.getAllObjects sometimes returns empty result, but following: jsonrpc method params ------- ------ ------ 2.0 all @{type=enter; items=} On retry - everything is fine and we have all data jsonrpc result ------- ------ 2.0 @{bbdb1ed0-4c86-24ec-...=;..... method vm.copy sometimes returns only task with name_label host.get_server_certificate and no task async.vm.copy. Meanwhile copy operation is started in XEN Orchestra, so we have to separately search for the task currently running in all objects and if it is not there anymore suggest that it completed successfully. Afterwards we need to check if vm was copied and appeared in all objects. That is really frustrating as we have no info about successfully completed tasks in XEN - records just removed as nothing happen. most likely this happens due to other tasks being popped up in tasks at the same time and websocket call recives not its own responce, is it possible to workaround? What is correct syntax for JSON to run job.create method? Are there any article with supported methods for JSON-RPC calls and examples to use them? Calling for "system.getMethodsInfo" I can see "job.create": { "description": "Creates a new job from description object", "params": { "job": { "type": "object", "properties": { "userId": { "type": "string", "optional": true }, "name": { "type": "string", "optional": true }, "timeout": { "type": "number", "optional": true }, "type": { "type": "string" }, "key": { "type": "string" }, "method": { "type": "string" }, "paramsVector": { "type": "object", "properties": { "type": { "type": "string" }, "items": { "type": "array", "items": { "type": "object" } } }, "optional": true } } } }, "permission": "admin" }, But it is unclear what values should I provide to paramsVector and looking into the job created manually (in web interface) with method job.getall I can see 2 jobs [ { "type": "call", "name": "copyvm", "key": "generictask", "method": "vm.copy", "paramsvector": { "type": "crossproduct", "items": [ { "type": "set", "values": [ { "name": "nevm", "vm": "GUID", "sr": "GUID" } ] } ] }, "userid": "GUID", "id": "GUID" }, { "method": "vm.copy", "key": "vm.copy", "name": "copyvmjob", "type": "call", "userid": "GUID", "id": "GUID" } ] How can I create similar job myself if it is not possible to find out why vm.copy does not return async.vm.copy task info?
  • xo-cli - Get alarms

    Solved
    8
    1
    0 Votes
    8 Posts
    533 Views
    olivierlambertO
    You are welcome Enjoy! (great thing about xo cli is that you can get alarms of all your hosts from a single endpoint)
  • XOA migrate the XO itself

    Unsolved
    2
    0 Votes
    2 Posts
    666 Views
    olivierlambertO
    You can't, indeed, live migrate a VM from Intel to AMD (or vice-versa), for obvious reason (the VM will try to call Intel specific instructions after migrating on an AMD CPU, the result would be… a crash!) We had a similar migration ourselves (in our own prod), from Intel to AMD. And we decided to use Continuous Replication to make a first "backup" on destination (the full) while the original VMs were running (no service interruption). Then, we shut down the VMs, make another round of replication (delta, very fast) and then we booted on destination.
  • New VMs created in Xen Orchestra reboot every couple of minutes

    5
    0 Votes
    5 Posts
    563 Views
    R
    @olivierlambert That socket issue was not what was causing the problem, I went through setting by setting and if I choose 2GB of memory for a VM I get constant reboots when using XOA. I was able to repeat the issue with a number of OSs not just RHEL 8 (and variants). I havent went through and compared the differences between XOA and XenCenter yet.
  • Multiple remotes in a backup - how is retention calculated

    5
    0 Votes
    5 Posts
    509 Views
    badrAZB
    @s-pam said in Multiple remotes in a backup - how is retention calculated: OK Great. So if I set retention to 10, it would keep 10 copies on each remote? Yes. it will keep 10 copies on each remote.
  • 0 Votes
    1 Posts
    743 Views
    No one has replied
  • Error: SR_BACKEND_FAILURE_109(, The snapshot chain is too long, )

    6
    0 Votes
    6 Posts
    2k Views
    olivierlambertO
    In theory, Xen Orchestra got a protection against this issue (see https://xen-orchestra.com/docs/backup_troubleshooting.html#vdi-chain-protection ) So you have to find what's causing a long chain outside XO. You can check in XO, in the Advanced tab of the SR view, if there's VDI to coalesce. Or maybe very long chain for other reasons, there's a tool we made called xapi-explore-sr.
  • Backups/VM Migrations Slow

    4
    0 Votes
    4 Posts
    1k Views
    olivierlambertO
    Use CR instead of DR then, it will send only the diff to the other host, so it will be faster.
  • Cannot migrate VM from 7.5/7.6 to 8.2 INTERNAL_ERROR

    4
    0 Votes
    4 Posts
    339 Views
    M
    I can migrate this VM from another host (7.6) to the 8.2 host just fine: [image: 1612363337871-29412a19-7047-4feb-a82e-1b3d3ce61a94-image.png] Im not sure what the agent actually is, thats why im guessing this might be related [image: 1612363441628-eb67e1dd-0979-4b17-94a8-b3d4f72397a5-image.png] VM that fails: [image: 1612363482511-153e71d2-3779-4894-b990-3b4f6b02e032-image.png]
  • Crashed XOA. Can't boot a clean XOA and use RESTORE because of REGISTRATION

    10
    -1 Votes
    10 Posts
    901 Views
    olivierlambertO
    It's not that easy to block some screens. But that's an interesting suggestion, I'll pass that to @pdonias
  • Multiple VM exports fails with unknown error

    7
    0 Votes
    7 Posts
    1k Views
    DanpD
    @nodesocket Depends on your setup. For mine, I use sudo systemctl restart xo-server.service. You could also just restart the VM.
  • ova problems

    Solved community
    20
    0 Votes
    20 Posts
    2k Views
    olivierlambertO
    @s-pam said in ova problems: @crazytoo Best way to be sure it to boot the VM using a live-cd, for example systemrescue-cd or ubuntu live-dvd. Then you can use tools like gparted to inspect your disk image from inside the booted vm. That's exactly what I advised to do earlier, but it seems it was missed the first time I think that's the best approach to understand what's going on in the VM disk.
  • xoa update "your appliance is too old, please deploy a new one"

    2
    0 Votes
    2 Posts
    547 Views
    olivierlambertO
    Mainly a more recent version of Debian.
  • Duplicate entries in backup restore?

    3
    1
    0 Votes
    3 Posts
    178 Views
    ForzaF
    @jedimarcus No. But I think the problem could be an issue where I merged two remote backup trees.
  • Deleted Backup Jobs

    Solved
    7
    7
    0 Votes
    7 Posts
    592 Views
    A
    Complete solution is delete delete all jobs with type "call" then delete this job ids from job_ids table. After this delete all schedule's with this job ids. And then delete this schedule ids from schedule_ids table.
  • when i use the eve-ng it crashs

    2
    0 Votes
    2 Posts
    1k Views
    olivierlambertO
    Hi, I think the issue was already reported on EVE-ng forums. It's a problem with their image and Xen, if I remember correctly.
  • Roadmap vote

    2
    1
    0 Votes
    2 Posts
    301 Views
    olivierlambertO
    Hi, We never had the time to formalize that. But we do something "close": feature requests via paid support ticket are given a top priority. For the community feedback, it's pretty easy to see what's the most required via github repo or here.
  • Unable to start newly created VM

    Solved
    4
    0 Votes
    4 Posts
    480 Views
    olivierlambertO
    Thanks for the feedback. If you couldn't find this in our troubleshooting section of our doc, feel free to contribute, that will be helpful to others too
  • New install of XCP-ng, can't complete Quick Deploy

    Solved
    12
    0 Votes
    12 Posts
    6k Views
    DanpD
    @mstollenwerk Took care of that for you
  • Complete uninstall of XOSANv1?

    2
    0 Votes
    2 Posts
    216 Views
    olivierlambertO
    Hi, Please open a support ticket so we can take a look remotely. In theory, just removing the SR should be enough.
  • XOA backups missing after changing IP on the remote

    3
    0 Votes
    3 Posts
    219 Views
    ForzaF
    @danp said in XOA backups missing after changing IP on the remote: Hi @s-pam, I assume you tried disabling and then reenabling the remote, correct? Dan Yes indeed. Thanks for the suggestion. I did file a support ticket so hopefully I can get some support to solve this.