Subcategories

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

    362 Topics
    3k Posts
    T
    @andriy.sultanov Here are the logs. To your second question. I thought I was able to pass through devices from XO and then the host reboots. Maybe I misunderstood how this worked. Are you saying I need to do this in the console and then XO? Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] PCI.get_dom0_access_status R:1f40280dd69a failed with exception Server_error(INTERNAL_ERROR, [ 126 ]) Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] Raised Server_error(INTERNAL_ERROR, [ 126 ]) Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 1/15 xapi Raised at file ocaml/xapi-aux/helper_process.ml, line 17 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 2/15 xapi Called from file ocaml/xapi/pciops.ml, line 73 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 3/15 xapi Called from file ocaml/xapi/pciops.ml, line 95 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 4/15 xapi Called from file ocaml/xapi/pciops.ml, line 99 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 5/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 6/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 7/15 xapi Called from file ocaml/xapi/xapi_pci_helpers.ml, line 213 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 8/15 xapi Called from file ocaml/xapi/message_forwarding.ml, line 141 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 9/15 xapi Called from file ocaml/xapi/rbac.ml, line 188 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 10/15 xapi Called from file ocaml/xapi/rbac.ml, line 197 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 11/15 xapi Called from file ocaml/xapi/server_helpers.ml, line 77 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 12/15 xapi Called from file ocaml/xapi/server_helpers.ml, line 96 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 13/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 24 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 14/15 xapi Called from file ocaml/libs/xapi-stdext/lib/xapi-stdext-pervasives/pervasiveext.ml, line 39 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace] 15/15 xapi Called from file ocaml/libs/log/debug.ml, line 250 Jul 7 16:42:08 xcp-ng-01 xapi: [error||62070 :::80|dispatch:PCI.get_dom0_access_status D:7ee7c7e624f9|backtrace]
  • ACLs, Self-service, Cloud-init, Load balancing...

    89 Topics
    763 Posts
    R
    I see your point. Thank you!
  • 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

    65 Topics
    493 Posts
    S
    I am attempting to create a VM through REST with curl. I keep getting the following error: [ { "instancePath": "", "schemaPath": "#/required", "keyword": "required", "params": { "missingProperty": "name_label" }, "message": "must have required property 'name_label'" }, { "instancePath": "", "schemaPath": "#/required", "keyword": "required", "params": { "missingProperty": "template" }, "message": "must have required property 'template'" } ] So far as I can tell, the data I am sending to the XOA is correct: { "name_label": "AAATestVM001", "template": "903c3e42-47f9-189e-3ea7-623e91c0ccd5-905ab443-e415-4d52-bfef-e14b147eac4e", "auto_poweron": true, "memory": 4294967296, "vdis": [ { "size": 85899345920, "name_label": "AAATestVM001_1", "sr": "839dea70-7c11-a143-bd4f-f2f8426bb469" } ], "vifs": [ { "network": "8af13cf7-c290-0622-19f0-d16d43587ec0" } ] } Can anyone tell if there appears to be any errors in the data I am sending? Thanks.
  • 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?
  • GPN GRE/VxLAN Tunnel - connect/access from other Devices?

    1
    0 Votes
    1 Posts
    76 Views
    No one has replied
  • DUPLICATE_MAC_SEED

    6
    0 Votes
    6 Posts
    175 Views
    I
    @DustinB Here is the backup job configuration: [image: 1743536286372-0459c49d-0b84-4585-9bb8-e3c79bac771b-image.png] [image: 1743536250474-6c3f31b2-aeb7-4d96-b441-3248af6f27a2-image.png]
  • Upgrade to XO v5.105 seems broken

    9
    2 Votes
    9 Posts
    539 Views
    I
    @ph7 Thank you. It seems to work like that. I'll wait for this fix.
  • XO CE 82ed2 and 5c390 update.

    4
    0 Votes
    4 Posts
    380 Views
    olivierlambertO
    Note: just do a yarn && yarn build and it will work. The XO 6 build might be broken, but that's not surprising, it could happens.
  • SQL Database support and XO HA

    7
    0 Votes
    7 Posts
    221 Views
    I
    @olivierlambert Happy to hear
  • Just an idea :) - (SATA controller passthrough)

    3
    0 Votes
    3 Posts
    195 Views
    lsouai-vatesL
    @ScarfAntennae hello, and thanks for the suggestion. I am discussing it with the XO Team to add it to our next features. Have a good day!
  • Bonded interface viewing support in XO

    23
    1 Votes
    23 Posts
    3k Views
    lsouai-vatesL
    @flakpyro yes, indeed that exactly what I was talking about. The XO6 new interface will provide more information, but I am noting the missing type of bound to discuss it with XO team for next feature.
  • With qcow2 format support coming, could we then import KVM vm's ?

    3
    0 Votes
    3 Posts
    289 Views
    I
    Works with .raw at the moment. If you disconnect it from the vm and migrate it to another SR its converter to vhd.
  • resourceSet issues

    4
    7
    0 Votes
    4 Posts
    223 Views
    I
    @olivierlambert ack.
  • Trial period extension for on-going tests

    3
    1
    0 Votes
    3 Posts
    165 Views
    Y
    @Danp Hi, Thanks for quick support.
  • How to deploy XO on ESXi

    5
    0 Votes
    5 Posts
    224 Views
    D
    @yzgulec said in How to deploy XO on ESXi: I just used VMware Converter for V2V (seems more practical for me) Installing from Source or using an installation script from the community is also very straight-forwards. Maybe 10 minutes worth of setup for the OS and then for at least my github it's a single line installation.
  • Simulating network cable disconnect

    11
    0 Votes
    11 Posts
    2k Views
    O
    @splastunov I realize this thread is old, but I think there is important info to keep connected to this thread for future readers. The IP locking trick doesn't seem to prevent all traffic -- it only prevents traffic that has an IP that isn't 255.255.255.255 (and possibly others as well). That is, I can still successfully acquire a DHCP IP even when the IP locking mechanism is engaged. I think this is important for others to know since it doesn't fully isolate VMs like the OP wanted. UPDATE: Setting the locking mode to "disabled" is what you want -- not "locked". Disabled will drop all traffic; locked simply checks if the set of IPs in the VM is permitted. Source: https://docs.xenserver.com/en-us/citrix-hypervisor/networking/manage.html#vif-locking-mode-states
  • host connection error

    3
    1
    0 Votes
    3 Posts
    94 Views
    P
    @irtaza9 Sometimes when I have been tinkering with a host, I get a red triangle. Then just pressing Enabled and then Disabled can get rid of the triangle and the host back in business again.
  • 0 Votes
    10 Posts
    261 Views
    D
    @julien-f said in Enhancement suggestion: Filter showing VMs that don't have the agent installed: XO does not support this for halted VMs but that could be added indeed. Can you change the title of my thread to "Enhancement suggestion: Update 'ManagementAgentDetected?' to support halted VMs" ?
  • XO High Availability

    6
    0 Votes
    6 Posts
    284 Views
    DanpD
    @irtaza9 You should be able to login with the default credentials after you restart the xo-server service with systemctl restart xo-server.service.
  • Web Hook plugin

    2
    0 Votes
    2 Posts
    109 Views
    olivierlambertO
    Hi, Before enabling the plugin, you need to configure it in the Plugin view.
  • XOA on a vSphere VM

    4
    0 Votes
    4 Posts
    179 Views
    DanpD
    @yzgulec You will likely need to install the fix given in the following post for XOA to function correctly on vSphere -- https://xcp-ng.org/forum/post/50279
  • Difference between "pool", "host" and "server".

    Solved
    6
    0 Votes
    6 Posts
    1k Views
    pdoniasP
    @andrewperry Exactly
  • Lots of performance alerts after upgrading XO to commit aa490

    28
    0 Votes
    28 Posts
    5k Views
    Bastien NolletB
    @ph7 Some of the errors you encountered are intended. We don't allow values in the "Virtual Machines" field if "Exclude VMs" is disabled and "All running VMs" is enabled, because it would make the plugin configuration confusing. However you're right, there seems to be an issue when the VMs are selected and then removed. The value becomes an empty list instead of being undefined, which causes the validation to fail when we try to turn off the "Exclude VMs" option. I'm going to create a task on our side so that we can plan to resolve this problem. In the meantime you can work around the problem by deleting the monitor and recreating a new one with the same parameters.
  • S3 Backup - maximum number of parts

    1
    0 Votes
    1 Posts
    71 Views
    No one has replied