Categories

  • All news regarding Xen and XCP-ng ecosystem

    145 Topics
    5k Posts
    marcoiM
    for the latest updates. the test pool didnt move the vms when i went to reboot. so i moved them manually. rebooted master, move vms back patched and reboot 2nd test server in the pool. Skipped trying rolling reboot in prod and followed the same process. both pools went well without other issues.
  • Everything related to the virtualization platform

    1k Topics
    15k Posts
    poddingueP
    Thanks, keep us posted!
  • 3k Topics
    29k Posts
    P
    Hello, To wrap up this last issue: the 500 errors backing up to S3 B2 are network contention related. There is some kind of contention with my link to B2 and having 8 VMs backing up simultaneously sometimes triggers these errors. Last weekend I reduced concurrency to 3 and every VM was successfully backed up - no VM level retries. I can't tell if some file parts were retried since these are only logged when the AWS_MAX_ATTEMPS are exhausted and the VM backup fails. So, these are not B2 issues and the default AWS_MAX_ATTEMPS is probably fine for most scenarios. I'll leave my at 10 following rclone defaults. Thank you, Pedro
  • Our hyperconverged storage solution

    50 Topics
    796 Posts
    olivierlambertO
    Great, thanks for the feedback!
  • 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