Categories

  • All news regarding Xen and XCP-ng ecosystem

    139 Topics
    4k Posts
    P
    @dinhngtu said in XCP-ng Windows PV tools announcements: @probain The canonical way is to check the product_id instead https://docs.ansible.com/projects/ansible/latest/collections/ansible/windows/win_package_module.html#parameter-product_id The ProductCode changes every time a new version of XCP-ng Windows PV tools is released, and you can get it from each release's MSI: No problem... If you ever decide to have the .exe-file as a separate item. Not bundled within the zip-file. Then I would be even happier. But until then, thanks for everything!

  • Everything related to the virtualization platform

    1k Topics
    14k Posts
    M
    @flakpyro said in log_fs_usage / /var/log directory on pool master filling up constantly: One of our pools. (5 hosts, 6 NFS SRs) had this issue when we first deployed it. I engaged with support from Vates and they changed a setting that reduced the frequency of the SR.scan job from 30 seconds to every 2 mins instead. This totally fixed the issue for us going on a year and a half later. I dug back in our documentation and found the command they gave us xe host-param-set other-config:auto-scan-interval=120 uuid=<Host UUID> Where hosts UUID is your pool master. Thank you very much for checking your documentation and sharing your fix! I will try your approach on my pool master. Best regards

  • All Xen Orchestra related questions/reports

    3k Topics
    26k Posts
    olivierlambertO
    Create an appliance with all those VMs and configure the order and delay inside it.

  • Our hyperconverged storage solution

    38 Topics
    693 Posts
    D
    @pilow : thanks for let me know your experience. I was afraid someone would say that. Unfortunately for us going out of XOSTOR is not so simple because we really need VM mobility to allow for host maintenance which otherwise we would not be able to perform and budgeting for a redundant external storage is not an option either. The annoying thing is that before start this journey with Vates we did engage with them and made them aware of our environment ( it is a migration from vmware) and no one has ever mention that could have been a problem to store so many VMs into xostor so I am really hope that support can shed some light and provide some fix to the situation. Overall is not a bad experience but waiting for 3 / 4 minutes for a VM to start when you are in hurry is not really great.

  • Non-English speakers

    31 Topics
    90 Posts
    olivierlambertO
    Yes, account aren't related