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
    J
    Hey @Andrew, thanks very much for looking that up and providing the suggestions! Re. option 2: it's possible to just hide the T600 from dom0 and remove the R9 270 from the machine? dom0 won't complain that it's missing a GPU, or take control of the only GPU in the system?
  • 3k Topics
    27k Posts
    S
    As an observation ; I'm going to draw attention to @majorp93's point about rebooting the servers after ALL nodes have been upgraded. Historically we would move all VMs off master, upgrade master, restart its toolstack, then reboot master, then move VMs from Node 1 to master so we could begin the upgrade on Node1. Normally works ok but last time around it caused all sorts of problems. Previously it had felt right to upgrade master in its entirety including the reboot before moving on to the next host and rinse, repeat - but this cost us a lot of time, corruptions and pain. TLDR: Perhaps add a footnote to the docs that when upgrading a pool the reboots should take place as a final step across the pool only after all nodes have been updated.
  • 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