Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    stormiS
    @mthird said: Spoke to soon. While the updates succeeded, one of the nodes is rebooting every few minutes due to an HA self-fence. Could you open a dedicated thread and ping me there?

  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    P
    @andriy.sultanov I finally got around to fixing my capture card and I gotta say, it's a real pain to be using both methods and doesn't feel "correct" especially when there are warnings about possibly losing dom0 configurations after updates and the knowledge base saying that the old hide PCI from dom0 method is now considered obsolete. Perhaps the best solution would just be to provide users with a CLI command that would add that particular device to the xl pci-assignable-list if it doesn't fall into classes 01XX, 02XX or 03XX. Because I had added my GPU to my VM using the webUI, but then I also wanted to add the capture card through the console, but it appears that in the end you basically need to undo what's been done in the webUI and do it all through the console, otherwise you'd add the capture card manually with command line and then that would remove the GPUs... So I think some sort of manual override is necessary, even if it's a CLI option and then once that's done we could go into the webUI to enable it once the device has been marked as safe to passthrough.

  • All Xen Orchestra related questions/reports

    3k Topics
    29k Posts
    P
    Hello XCP-NG Devs, I ran into a problem where the XCP-NG keep telling XOA that there are updates waiting, but I've run "yum update" on all of the active hosts in the pool but I'm still getting the error "NOT_SUPPORTED_DURING_UPGRADE()" Here's the what I see in the error log: { "code": "NOT_SUPPORTED_DURING_UPGRADE", "params": [], "call": { "duration": 9, "method": "VM.set_VCPUs_max", "params": [ "* session id *", "OpaqueRef:0c912f80-7929-c60d-0d26-ebd74823d57d", 4 ] }, "message": "NOT_SUPPORTED_DURING_UPGRADE()", "name": "XapiError", "stack": "XapiError: NOT_SUPPORTED_DURING_UPGRADE() 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:64:5) at processImmediate (node:internal/timers:452:9) at process.callbackTrampoline (node:internal/async_hooks:130:17)" } Is there any way I can check the entire cluster for what upgrades are waiting? Alternatively, is there a way I can for the rolling pool update to start over and check each host? Thank you, -peb2

  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!

  • Non-English speakers

    37 Topics
    136 Posts
    J
    @AtaxyaNetwork Merci pour tes recherches ! Oui "cd_label" serait cool comme ajout au plugin ce qui permet sur les distro type Fedora/Redhat de ne pas avoir de boot_command à gérer