XCP-ng
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Some VMs are shutting down autmatically

    Scheduled Pinned Locked Moved Xen Orchestra
    6 Posts 4 Posters 760 Views 1 Watching
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • A Offline
      aithorusa
      last edited by aithorusa

      This post is deleted!
      1 Reply Last reply Reply Quote 0
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        If there's no log from the hypervisor perspective, it means they maybe crashed. Anything in the VM itself? (logs and so on)

        A 1 Reply Last reply Reply Quote 0
        • A Offline
          aithorusa @olivierlambert
          last edited by

          @olivierlambert No, nothing is generated in the logs. The VMs just shut down after a while. Normally, a message pops up as well asking for a reason why Server 2016 was shut down but not in this case.

          1 Reply Last reply Reply Quote 0
          • olivierlambertO Offline
            olivierlambert Vates 🪐 Co-Founder CEO
            last edited by olivierlambert

            You can check logs on XCP-ng to see if you have any info. My gut feeling is it's more guest related 🙂

            1 Reply Last reply Reply Quote 0
            • T Offline
              tony
              last edited by

              Power issue can cause the host to turn off because writing any logs, is your UPS is working correctly? May be check the host runtime.

              1 Reply Last reply Reply Quote 0
              • ronivayR Offline
                ronivay Top contributor
                last edited by ronivay

                What does the memory min/max settings look like in the advanced tab of those VM's? You could try to set the dynamic min/max to same values. Could very well be that your guest OS doesn't handle it properly when host is trying to dynamically adjust the available VM memory. Although this shouldn't happen (afaik) if there's plenty of memory available on the host, but worth a try at least.

                1 Reply Last reply Reply Quote 0
                • First post
                  Last post