Categories

  • All news regarding Xen and XCP-ng ecosystem

    143 Topics
    4k Posts
    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.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    F
    I know we can snapshot VMs in XO Lite, but is there actually a way to revert a VM to a particular snapshot in the XO Lite GUI? I can't seem to find that function. Is it CLI only, Xen Orchestra notwithstanding?
  • 3k Topics
    28k Posts
    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
  • Our hyperconverged storage solution

    47 Topics
    745 Posts
    J
    @Mathieu-L linstor n l was included in my original post. All nodes were updated to May 2026 Security and Maintenance Updates for XCP-ng 8.3 LTS, all nodes were restarted. May 2026 Updates #2 for XCP-ng 8.3 LTS was released, and a couple days later I installed on all hosts. No host restarted. When xen04 was restarted, that is when this issue happened. I had used systemctl restart linstor-controller here (https://xcp-ng.org/forum/post/105309) to restart the controller.
  • 35 Topics
    113 Posts
    olivierlambertO
    Ah excellente nouvelle Je passe le sujet en résolu !