Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    P
    @dinhngtu tried on a Windows Server 2025 VM, UEFI BIOS working well, no reboot needed
  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    yannY
    @wlp94114 for example, did you get any warnings in the kernel logs about the firmware version mismatch?
  • 3k Topics
    27k Posts
    T
    Offering feedback that my implementation of the XO CCM (v1.0.0-rc.1) into my K8s cluster was successful; I validated that the nodes were labeled as expected. I attached screenshots from Rancher and the CLI. In my lab, I use OCNE 1.9 (Oracle Cloud Native Environment) on Oracle Linux 9.7. In my setup, I edited the kubeadm-config ConfigMap and on all nodes added the Kubelet argument for the cloud provider. I restarted the Kubelet on all nodes and then deployed the CCM via Method 1 per the documentation From my setup to set the cloud-provider: kubectl edit cm kubeadm-config -n kube-system apiServer: extraArgs: cloud-provider: external controllerManager: extraArgs: cloud-provider: external sudo vim /etc/sysconfig/kubelet KUBELET_EXTRA_ARGS="--fail-swap-on=false --cloud-provider=external" sudo systemctl daemon-reload && sudo systemctl restart kubelet [image: 1770418969929-rancher_xo_ccm_labels-resized.png] [image: 1770419178223-ocne_xo-ccm_pod.png]
  • Our hyperconverged storage solution

    40 Topics
    715 Posts
    I
    @ronan-a Thanks
  • 31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related