Categories

  • All news regarding Xen and XCP-ng ecosystem

    141 Topics
    4k Posts
    B
    I also added windows build so that people can help with testing also on windows. It's a static build, no need for installer, just single zipped .exe file. No dependencies.
  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    E
    Hi, I had to shut down my XCP-ng system to add a replacement for a previously failed NVMe that was attached to my TrueNAS SCALE VM, which also involved moving around a couple of the PCIe cards. I thought this would be a good opportunity to catch up with the upgrades, so also applied those during the shutdown/reboot. Following the upgrade and installing the replacement NVMe I can no longer boot my TrueNAS SCALE VM, it fails with: vm.start { "id": "81e6cde8-baba-5f2e-0a08-a4d9f3e0a41e", "bypassMacAddressesCheck": false, "force": false } { "code": "INTERNAL_ERROR", "params": [ "xenopsd internal error: Cannot_add(0000:af:00.0, Device_common.QMP_Error(2, \"{\\\"error\\\":{\\\"class\\\":\\\"GenericError\\\",\\\"desc\\\":\\\"Failed to initialize 11/15, type = 0x1, rc: -1\\\",\\\"data\\\":{}},\\\"id\\\":\\\"qmp-000012-2\\\"}\"))" ], "call": { "duration": 8798, "method": "VM.start", "params": [ "* session id *", "OpaqueRef:63502630-5729-b5d4-4ef2-49d6c14e07bd", false, false ] }, "message": "INTERNAL_ERROR(xenopsd internal error: Cannot_add(0000:af:00.0, Device_common.QMP_Error(2, \"{\\\"error\\\":{\\\"class\\\":\\\"GenericError\\\",\\\"desc\\\":\\\"Failed to initialize 11/15, type = 0x1, rc: -1\\\",\\\"data\\\":{}},\\\"id\\\":\\\"qmp-000012-2\\\"}\")))", "name": "XapiError", "stack": "XapiError: INTERNAL_ERROR(xenopsd internal error: Cannot_add(0000:af:00.0, Device_common.QMP_Error(2, \"{\\\"error\\\":{\\\"class\\\":\\\"GenericError\\\",\\\"desc\\\":\\\"Failed to initialize 11/15, type = 0x1, rc: -1\\\",\\\"data\\\":{}},\\\"id\\\":\\\"qmp-000012-2\\\"}\"))) at Function.wrap (file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/_XapiError.mjs:16:12) at file:///usr/local/lib/node_modules/xo-server/node_modules/xen-api/transports/json-rpc.mjs:38:21 at runNextTicks (node:internal/process/task_queues:60:5) at processImmediate (node:internal/timers:454:9) at process.callbackTrampoline (node:internal/async_hooks:130:17)" } As far as I can see, all the passthrough devices are correctly specified. Is the device referenced in the error this: af:00.0 PCI bridge: Intel Corporation Device 4fa1 (rev 01) Could this be caused by my switching a couple of the PCIe cards around, as one of them is an NVMe expansion that is passed through to TrueNAS (but this does show up correctly under it's own ID). This is XCP-ng 8.3 running on a Supermicro X11DPH-T. Cheers.
  • 3k Topics
    27k Posts
    S
    @florent 100% agree, sadly not an option in this particular scenario. Had hoped for a hidden switch that would allow backups to be downgraded to ova but tbh the API will do the job just fine. Thanks all; appreciated
  • Our hyperconverged storage solution

    39 Topics
    706 Posts
    nikadeN
    @irtaza9 it scans all the VDI's on the SR to see if something has changed, if there's a need for coalesce and so on. I dont think it will be a big issue if you increase the auto-scan-interval value to lets say 5 minutes (300 seconds), but do remember, that everything regarding the VDI's on the SR will take up to 5 minutes to update, as well as triggering coalesce after removing snapshots.
  • 31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related