ML
    • Recent
    • Categories
    • Tags
    • Popular
    • Users
    • Groups
    • Register
    • Login

    Hyper-V VMs in Stopping Critical State

    Scheduled Pinned Locked Moved IT Discussion
    hyper-vhyper-v 2012 r2virtualization
    28 Posts 6 Posters 14.8k Views
    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.
    • Alket_tuxA
      Alket_tux
      last edited by

      nothing in the logs.. yes i tried to kill, nothing happened

      wirestyle22W 1 Reply Last reply Reply Quote 0
      • wirestyle22W
        wirestyle22 @Alket_tux
        last edited by

        @Alket_tux said in Hyper-V VMs in Stopping Critical State:

        nothing in the logs.. yes i tried to kill, nothing happened

        You're killing VMWP.EXE ?

        Alket_tuxA 2 Replies Last reply Reply Quote 1
        • Alket_tuxA
          Alket_tux @wirestyle22
          last edited by

          @wirestyle22 yes

          wirestyle22W 1 Reply Last reply Reply Quote 0
          • Reid CooperR
            Reid Cooper
            last edited by

            Is there anything running on your Hyper-V host other than the Hyper-V utilities? Lots of things can cause Hyper-V to pause if installed alongside.

            Alket_tuxA 1 Reply Last reply Reply Quote 0
            • wirestyle22W
              wirestyle22 @Alket_tux
              last edited by

              @Alket_tux It successfully terminates the process but still shows itself as stopping critical? What does 'nothing happened' mean?

              Alket_tuxA 1 Reply Last reply Reply Quote 0
              • Alket_tuxA
                Alket_tux @wirestyle22
                last edited by

                @wirestyle22 i rebooted the server, and i have been 30 minutes now just seeing shutting downservice: hyper-v machine management*

                wirestyle22W 1 Reply Last reply Reply Quote 0
                • Alket_tuxA
                  Alket_tux @Reid Cooper
                  last edited by

                  @Reid-Cooper no, nothing, team viewer only

                  1 Reply Last reply Reply Quote 0
                  • wirestyle22W
                    wirestyle22 @Alket_tux
                    last edited by

                    @Alket_tux Can you turn off that service and attempt to reboot?

                    Alket_tuxA 1 Reply Last reply Reply Quote 0
                    • Alket_tuxA
                      Alket_tux @wirestyle22
                      last edited by

                      @wirestyle22 it means that the state of the vm is running again, it just does not show the resources allocated to it

                      1 Reply Last reply Reply Quote 0
                      • Alket_tuxA
                        Alket_tux @wirestyle22
                        last edited by

                        @wirestyle22 i tried to do that, but it did not stop, it remained in stopping state.. and in the logs it showed that the vm-s were running so this service cannot be stoppoed

                        1 Reply Last reply Reply Quote 0
                        • Alket_tuxA
                          Alket_tux
                          last edited by

                          i have not inserted integration services manually but yesterday everything worked fine..
                          by the way i have emulex nic's and in google i found that it might be a problem

                          wirestyle22W 1 Reply Last reply Reply Quote 0
                          • wirestyle22W
                            wirestyle22 @Alket_tux
                            last edited by

                            @Alket_tux I also found NIC related issues listed

                            Alket_tuxA 1 Reply Last reply Reply Quote 0
                            • Alket_tuxA
                              Alket_tux @wirestyle22
                              last edited by

                              @wirestyle22 i found some kb related solutions but haven't applied yet

                              wirestyle22W 1 Reply Last reply Reply Quote 0
                              • wirestyle22W
                                wirestyle22 @Alket_tux
                                last edited by wirestyle22

                                @Alket_tux From what I've been reading they didn't help. Hopefully yours is different. What VM's are you running? OS's and everything

                                Alket_tuxA 1 Reply Last reply Reply Quote 0
                                • Alket_tuxA
                                  Alket_tux @wirestyle22
                                  last edited by

                                  @wirestyle22 windows server 2012 r2 my primary server
                                  hyper v role on top of it
                                  6 ws2012 r2 vm's created

                                  Alket_tuxA 1 Reply Last reply Reply Quote 1
                                  • Alket_tuxA
                                    Alket_tux @Alket_tux
                                    last edited by

                                    @Alket_tux all working fine until yesterday, when i left my office and let windows update
                                    on all servers

                                    1 Reply Last reply Reply Quote 0
                                    • ObsolesceO
                                      Obsolesce @Alket_tux
                                      last edited by

                                      @Alket_tux said in Hyper-V VMs in Stopping Critical State:

                                      Hello guys,
                                      i ve been in trouble with hyper v on ws 2012 r2.. the issue is that when i restart my server Hyper-v Virtual machine management service takes an eternity to stop, so i hard reboot.. after that my machines are in runnig state.. also when i try to shutdown my vm-s, their state goes to stopping critical.. any ideas would be helpful..
                                      thanks

                                      When you shut down a Hyper-V server, the default settings for all of your VMs is to save the state of the VM. After that, your server will shut down. Depending on the number of VMs you have, it could take a little bit to save the state of all of them. It has to write the memory to disk, etc. Also, the default startup option is to start the VMs if they were started when they went down, which is why they are back up when you boot up your hypervisor.

                                      If you are killing your server during this process, you are hurting your VMs. This will cause critically stopped states. Hopefully they are .vhdx disks to help prevent corruption.

                                      wirestyle22W Alket_tuxA 2 Replies Last reply Reply Quote 3
                                      • wirestyle22W
                                        wirestyle22 @Obsolesce
                                        last edited by

                                        @Tim_G said in Hyper-V VMs in Stopping Critical State:

                                        @Alket_tux said in Hyper-V VMs in Stopping Critical State:

                                        Hello guys,
                                        i ve been in trouble with hyper v on ws 2012 r2.. the issue is that when i restart my server Hyper-v Virtual machine management service takes an eternity to stop, so i hard reboot.. after that my machines are in runnig state.. also when i try to shutdown my vm-s, their state goes to stopping critical.. any ideas would be helpful..
                                        thanks

                                        When you shut down a Hyper-V server, the default settings for all of your VMs is to save the state of the VM. After that, your server will shut down. Depending on the number of VMs you have, it could take a little bit to save the state of all of them. It has to write the memory to disk, etc. Also, the default startup option is to start the VMs if they were started when they went down, which is why they are back up when you boot up your hypervisor.

                                        If you are killing your server during this process, you are hurting your VMs. This will cause critically stopped states. Hopefully they are .vhdx disks to help prevent corruption.

                                        Oh I misread the OP. I thought he originally shut this down properly. @Alket_tux you just attempted to reboot the hypervisor without shutting down the VM's initially, am I reading that correctly now?

                                        Alket_tuxA 1 Reply Last reply Reply Quote 0
                                        • Alket_tuxA
                                          Alket_tux @Obsolesce
                                          last edited by

                                          @Tim_G i did stop my server forcefully a couple of times, 😞

                                          1 Reply Last reply Reply Quote 0
                                          • Alket_tuxA
                                            Alket_tux @wirestyle22
                                            last edited by

                                            @wirestyle22 yes,, because i could not shut down the vm's as they went in stopping critical state

                                            wirestyle22W 1 Reply Last reply Reply Quote 0
                                            • 1
                                            • 2
                                            • 1 / 2
                                            • First post
                                              Last post