XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login
    1. Home
    2. Popular
    Log in to post
    • All Time
    • Day
    • Week
    • Month
    • All Topics
    • New Topics
    • Watched Topics
    • Unreplied Topics

    • All categories
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      187
      1 Votes
      187 Posts
      19k Views
      J
      Installed and working on my lab test machine, HP ProLiant DL165 G7 with AMD Opteron 6136 CPU and 32 GB of RAM.
    • A

      XO Community edition backups dont work as of build 6b263

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      64
      0 Votes
      64 Posts
      1k Views
      R
      @florent Great work, thanks for the fixes
    • K

      XO6 Possible Issue with Lock Sidebar Button

      Watching Ignoring Scheduled Pinned Locked Moved Solved Management
      8
      0 Votes
      8 Posts
      64 Views
      K
      @lsouai-vates Duly noted. If amd when you do get a moment, could you have a look at https://xcp-ng.org/forum/post/94297 and offer up any guidance on how I can stop the debug log entries and also the double timestamp entries in the audit.log file? Thank you.
    • P

      Graph in v0.12.0 (48bf9)

      Watching Ignoring Scheduled Pinned Locked Moved XO Lite
      6
      0 Votes
      6 Posts
      95 Views
      lsouai-vatesL
      @ph7 good new, we also have a fix on tooltip overflow! https://github.com/vatesfr/xen-orchestra/pull/8779 J0ris-K opened this pull request in vatesfr/xen-orchestra open fix(web-core): fix tooltip overflow when too close to the edge #8779
    • R

      PCI Passthrough Missing Capabilities in Guest

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      5
      0 Votes
      5 Posts
      66 Views
      R
      @andSmv Thanks for the good info! Sure if you guys provide the beta I would be more than happy to test. Unfortunately, I only have access to this hardware for another week before I need to ship it out. If you can get me the beta today or tomorrow I can get it in place and start exercising it over the weekend. Thanks!
    • stormiS

      XCP-ng 8.2 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      711
      2 Votes
      711 Posts
      1m Views
      A
      @gduperrey Installed and running on a few pools. Working correctly as expected.
    • L

      Coral TPU PCI Passthrough

      Watching Ignoring Scheduled Pinned Locked Moved Compute
      38
      0 Votes
      38 Posts
      8k Views
      andSmvA
      @Niall-Con Thank you! I'll take a look to that and will ping you to test on real hardware. Just need to find time (in the middle of storm right now), so it'll take one or two weeks most probably.
    • I

      XEN Orchestra JSON-RPC automation questions

      Watching Ignoring Scheduled Pinned Locked Moved Unsolved Infrastructure as Code json-rps powershell 5 websocket automation deploy clone
      10
      0 Votes
      10 Posts
      398 Views
      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?
    • olivierlambertO

      XOSTOR hyperconvergence preview

      Watching Ignoring Scheduled Pinned Locked Moved XOSTOR
      457
      1
      5 Votes
      457 Posts
      525k Views
      H
      Hello, I plan to install my XOSTOR cluster on a pool of 7 nodes with 3 replicas, but not all nodes at once because disks are in use. consider: node1 node2 node ... node 5 node 6 node 7. with 2 disks on each sda: 128GB for the OS sdb: 1TB for local sr ( for now ) I emptied node 6 & 7. so, here is what i plan to do: On ALL NODES: setup linstor packages Run the install script on node 6 & 7 to add their disks so: node6# install.sh --disks /dev/sdb node7# install.sh --disks /dev/sdb Then, configure the SR and the linstor plugin manager as the following xe sr-create \ type=linstor name-label=pool-01 \ host-uuid=XXXX \ device-config:group-name=linstor_group/thin_device device-config:redundancy=3 shared=true device-config:provisioning=thin Normally, i should have a linstor cluster running of 2 nodes ( 2 satellite and one controller randomly placed ) with only 2 disks and then, only 2/3 working replicas. The cluster SHOULD be usable ( i'm right on this point ? ) The next step, would be to move VM from node 5 on it to evacuate node 5. and then add it to the cluster by the following node5# install.sh --disks /dev/sdb node5# xe host-call-plugin \ host-uuid=node5-uuid \ plugin=linstor-manager \ fn=addHost args:groupName=linstor_group/thin_device That should deploy satelite on node 5 and add the disk. I normally should have 3/3 working replicas and can start to deploy others nodes progressively. I'm right on the process ? aS mentionned in the discord, i will post my feedbacks and results from my setup once i finalized it. ( maybe thought a blog post somewhere ). Thanks to provide xostor in opensource, it's clearly the missing piece for this virtualization stack in opensource ( vs proxmox )
    • F

      Failed vm restore

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      16
      0 Votes
      16 Posts
      171 Views
      florentF
      @frank-s yes please the more detailed the bug report is, the easier it is to fix
    • M

      XO VM Backup Started and never completed

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      7
      1 Votes
      7 Posts
      66 Views
      M
      Workaround found here https://xcp-ng.org/forum/post/94626 Seems like turning "Use NDB to transfer disk if available" switch ON and save backup job, then turn the switch OFF and save backup job again, will fix the issue. Thanks to @RobWhalley and have a nice day everyone.