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

    Virtual Machine restarts

    Scheduled Pinned Locked Moved Compute
    8 Posts 2 Posters 1.5k Views 2 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.
    • M Offline
      Magoo 0
      last edited by Danp

      In the afternoon, everyone, I hereby request your help.
      I have a ProLiant DL380p Gen8 server with raid 0
      a Virtual Machine Windows server 2019 this one has a program with a database a few months ago that happens to me when trying to backup the database the virtual machine restarts if you want to send a file from the virtual machine to the cloud there is a lot of feces restart
      i.e. the virtual machine restarts for no apparent reason
      Can anyone help even with little information.
      thanks

      The reason supplied by user \Administrator for the last unexpected shutdown of this computer is: Other (Unplanned)
      Reason Code: 0xa000000
      Problem ID:

      The system has rebooted without cleanly shutting down first. This error could be caused if the system stopped responding, crashed, or lost power unexpectedly.

      1 Reply Last reply Reply Quote 0
      • DanpD Danp moved this topic from News on
      • olivierlambertO Offline
        olivierlambert Vates 🪐 Co-Founder CEO
        last edited by

        Hi,

        Have you started to look at https://xcp-ng.org/docs/troubleshooting.html ?

        Is your XCP-ng fully up to date?

        M 1 Reply Last reply Reply Quote 0
        • M Offline
          Magoo 0 @olivierlambert
          last edited by

          @olivierlambert
          thanks in advance for your quick reply xcp-ng 8.2.1

          thank you in advance for your quick response xcp-ng 8.2.1 I had this problem at another time and then without doing anything it worked fine and now this problem reappeared I don't know what else to do
          this virtual machine has a very important database

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

            Read the logs to try making sense of the event 🙂 (see which ones in the link I posted)

            M 1 Reply Last reply Reply Quote 0
            • M Offline
              Magoo 0 @olivierlambert
              last edited by

              @olivierlambert
              Sorry but I'm not sure what to look for in daemon.log

              I have a lot of information almost always the same as what I'm sending you. daemon.txt

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

                dmesg is a good first start, xl info too. Try to see around the time the VM crashed.

                M 1 Reply Last reply Reply Quote 0
                • M Offline
                  Magoo 0 @olivierlambert
                  last edited by

                  @olivierlambert
                  I can't thank you for the help you are giving me I took some data here they aredmesg.txt

                  M 1 Reply Last reply Reply Quote 0
                  • M Offline
                    Magoo 0 @Magoo 0
                    last edited by

                    @Magoo-0
                    I can't thank you for the help you are giving me I took some data here they are

                    xl info.txt

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