Categories

  • All news regarding Xen and XCP-ng ecosystem

    142 Topics
    4k Posts
    B
    @olivierlambert ok that's great, I didn't even notice, thanks!
  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    yannY
    @Tristis-Oris yes it is likely you're using a newer kernel, we likely need to rebuild the agent using a newer version of the netlink crate.
  • 3k Topics
    27k Posts
    P
    @MajorP93 you say to have 8GB Ram on XO, but it OOMkills at 5Gb Used RAM. did you do those additionnal steps in your XO Config ? You can increase the memory allocated to the XOA VM (from 2GB to 4GB or 8GB). Note that simply increasing the RAM for the VM is not enough. You must also edit the service file (/etc/systemd/system/xo-server.service) to increase the memory allocated to the xo-server process itself. You should leave ~512MB for the debian OS itself. Meaning if your VM has 4096MB total RAM, you should use 3584 for the memory value below. - ExecStart=/usr/local/bin/xo-server + ExecStart=/usr/local/bin/node --max-old-space-size=3584 /usr/local/bin/xo-server The last step is to refresh and restart the service: $ systemctl daemon-reload $ systemctl restart xo-server
  • Our hyperconverged storage solution

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