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
    • Tristis OrisT

      Continuous replication auto start

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      7
      0 Votes
      7 Posts
      402 Views
      tonyp90T
      Looks like the new build keeps retention snapshots in single VM instead of creating multiple VMs. Wasn't able to replicate the issue. I thought that the update wouldn't solve the problem because my build was still much newer than this thread.
    • stormiS

      XCP-ng 8.3 updates announcements and testing

      Watching Ignoring Scheduled Pinned Locked Moved News
      530
      1 Votes
      530 Posts
      236k Views
      I
      I am testing QCOW2. I do create 190 VMs on a single SR. The latency is growing with the count of VDIs on SR. [image: 1779297675818-3cbbd0d1-c3c1-4e9d-b74b-1933b6a64c51-image.jpeg] I got FC attached HPE AllFlash Storage. The other SR on same Storage has no performance impact. [image: 1779298232433-30494607-9e20-401f-b4c1-f04e03f0385d-image.jpeg] First 52 VMs was created without any problem. Than problems started. This VMs failed: #53 #94 #99 #100 #104 #106 #109 #110 #113 #115 #117 #120 #122 #124 #125 #128 #131 #136 #138 #145 #146 #152 #154 [... still pending] It loos like VDI.create for CloudConfigDrive runs into timeout. { "id": "0mpe928xl-jc1cgkgsmi", "properties": { "method": "vm.create", "params": { "name_label": "xcp-ng-vm156.lab.company.net", "name_description": "Test VM", "template": "0521468a-882b-9dd7-5add-2be588a389f8", "clone": false, "existingDisks": { "0": { "name_label": "xcp-ng-vm156.lab.company.net C", "$SR": "43dbbe8e-039a-e66c-f6cb-d88de4f4d962" } }, "CPUs": 4, "memory": 4294967296, "VIFs": [ { "network": "261a821c-a373-ba36-2c44-487ed0e1a202" } ], "cloudConfig": "**secret**", "coreOs": false, "bootAfterCreate": true, "destroyCloudConfigVdiAfterBoot": true, "tags": [ "win-cloud-init", "DUMMY" ], "hvmBootFirmware": "uefi" }, "name": "API call: vm.create", "userId": "033c2a08-7b45-4782-92f6-43acb73fe172", "type": "api.call" }, "start": 1779292916409, "status": "failure", "updatedAt": 1779294849770, "end": 1779294849770, "result": { "name": "HeadersTimeoutError", "code": "UND_ERR_HEADERS_TIMEOUT", "message": "Headers Timeout Error", "call": { "duration": 302136, "method": "VDI.create", "params": [ "* session id *", { "name_label": "XO CloudConfigDrive", "other_config": {}, "read_only": false, "sharable": false, "SR": "OpaqueRef:97a26f7e-0536-84de-f72c-49f11635df2d", "type": "user", "virtual_size": 10486272 } ] }, "stack": "HeadersTimeoutError: Headers Timeout Error\n at FastTimer.onParserTimeout [as _onTimeout] (/usr/local/lib/node_modules/xo-server/node_modules/undici/lib/dispatcher/client-h1.js:642:28)\n at Timeout.onTick [as _onTimeout] (/usr/local/lib/node_modules/xo-server/node_modules/undici/lib/util/timers.js:162:13)\n at listOnTimeout (node:internal/timers:585:17)\n at processTimers (node:internal/timers:521:7)" } } The support tunnel is open, id: 40797 Feel free, it's lab environment.
    • MathieuM

      Host crash during backup

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      11
      0 Votes
      11 Posts
      1k Views
      BrantleyHobbsB
      @Danp fully patched 8.3 (through the most recent May patches). XO commit d810e (master commit e3a58). I usually update XO around the first of each month; so it's a little bit behind master. There are crash logs in /var/crash. I can provide a log bundle if needed, or copy/paste some info here if I know what to provide.
    • D

      xe-gues-utilities woes on openSUSE Leap 16

      Watching Ignoring Scheduled Pinned Locked Moved XCP-ng
      3
      0 Votes
      3 Posts
      34 Views
      D
      @AtaxyaNetwork no error but also no xe-linux-distribution service installed or available...
    • N

      Create a new SR: qcow2 failure

      Watching Ignoring Scheduled Pinned Locked Moved Management
      9
      7
      0 Votes
      9 Posts
      191 Views
      N
      @florent said: where does this disk comes from From my Redhat 10 @florent said: if you have access to your SR from the outside, you can also put the qcow2 file directly I create a VM to be a NFS to access the 3 HDs, the qcow disks are on the Redhat 10 that I was trying to import from. Do you mean I put the qcow disks on one of the HDs and access them when I create a VM?
    • M

      Too many snapshots

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      48
      2
      0 Votes
      48 Posts
      3k Views
      florentF
      @julienXOvates PR is here https://github.com/vatesfr/xen-orchestra/pull/9868 fbeauchamp opened this pull request in vatesfr/xen-orchestra open fix(xo-web): ignore the number of snapshot of replicated VM in the health dashboard #9868
    • A

      GPU share to more Windows VMs on same XCP-NG node

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      10
      0 Votes
      10 Posts
      366 Views
      A
      @tjkreidl I found that some Intel PRO GPU card have SRV-IO without any additional license, but this functionality is supported in Linux kernel 6.12 and up. I hope in new XCP-NG will have 6.12+ and support GPU sharing.
    • M

      XO Console: Modifier keys stuck, unable to enter passwords

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      14
      0 Votes
      14 Posts
      2k Views
      poddingueP
      Thanks for the clarification, @dsmteam !
    • acebmxerA

      Some dashboard loading issues with v6

      Watching Ignoring Scheduled Pinned Locked Moved Xen Orchestra
      8
      5
      0 Votes
      8 Posts
      193 Views
      MathieuRAM
      @acebmxer Hi, Do you use an admin users or do you use a non admin users with RBAC/ACL-V2? What is the ouput of /rest/v0/users/me? Also, what is the ouput of /rest/v0/dashboard?
    • J

      Backups Fail with ENOENT: no such file or directory

      Watching Ignoring Scheduled Pinned Locked Moved Backup
      8
      0 Votes
      8 Posts
      349 Views
      J
      @pierrebrunet sorry for the delay in responding... I scored some time out of the office. Before replying, I rebuilt the XO server using the latest version and created a new backup identical to the last. Just wanted to be sure this issue wasn't fixed... I've attached the log. 2026-05-20T21_41_04.958Z - backup NG.json.txt
    • F

      Reverting to a snapshot in XO Lite

      Watching Ignoring Scheduled Pinned Locked Moved XO Lite
      1
      0 Votes
      1 Posts
      19 Views
      No one has replied
    • maximsachsM

      XCP-ng 8.3: Broadcom BCM57414 `bnxt_en` Driver Fails to Probe on HPE DL380a Gen12

      Watching Ignoring Scheduled Pinned Locked Moved Hardware
      10
      2 Votes
      10 Posts
      713 Views
      maximsachsM
      @yannsionneau @thierryescande Thank you very much for the updates! We are scheduling some downtime on the services in the upcoming weeks, then I hope to be able to try out all your suggestions. Our fallback plan is to switch the Broadcom network cards for other Melanox cards. I will be posting the results once we have them!