locked
Virtual Machines not auto starting on Server 2016 std RRS feed

  • Question

  • Hello

    I have a host server running 2 VMs which do not auto start on reboot of host.

    Host has 64GB RAM and the VMs have 16GB RAM each.

    All VMs have integration services enabled.

    Started delay - 0

    Set to save state on shutdown of host

    Auto start if it was already on.

    Event log shows this:

    An error occurred while performing server startup action for virtual machine.

    I can restart the VMs with no problem its only when the host is rebooted.


    Tuesday, June 16, 2020 7:45 AM

Answers

  • So it looks like this is a common issue with Server 2016.

    I think *touch wood* I've managed to sort it.

    it's taken a long time to get to the resolution due to production server / wanting to spend my time out of hours.

    This problem was occurring on 2 of my Server 2016 VMs on the host.

    I've changed the page file on both VMs from automatic to 1024MB min and 10240MB Max on C.

    Increased the VHDX a little so there was enough free space (>10GB)

    I then went in to the startup and recovery > write debugging information and set this to none.

    I've rebooted lots of times and cannot replicate the problem.

    • Marked as answer by Alphanumbers Friday, July 3, 2020 3:16 PM
    Friday, July 3, 2020 3:15 PM

All replies

  • Try changing the setting to always start the VM upon system boot, not just those that were 'already on'.  I think that when you ask to save the state of the VM on system shutdown, you are putting the machine into a non-running state at system shutdown.  Therefore, when the system shuts down, you actually have no VMs that are running.  Ergo, no VMs start because none were 'already on'.

    tim

    Tuesday, June 16, 2020 12:41 PM
  • Unfortunately they were defaulted to that state and it did the same thing.

    I've tried different variants of settings and have even recreated the VM and reinstalled hyperv role.

    Tuesday, June 16, 2020 1:22 PM
  • Hi,

    Try to install the latest update for your host and VM.

    And also check the the event logs (Hyper-V-VMMS and Hyper-V-Worker). It may have tried and failed for some reason. Also check here and with manufacturer that hardware is supported.

    https://www.windowsservercatalog.com/

    Best Regards,

    Daniel


    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Wednesday, June 17, 2020 7:09 AM
  • Hi,
    Just want to confirm the current situations.
    Please feel free to let us know if you need further assistance.
    Best Regards,
    Daniel

    Please remember to mark the replies as answers if they help.
    If you have feedback for TechNet Subscriber Support, contact

    Monday, June 22, 2020 8:27 AM
  • Unfortunately i am still having trouble.

    when Im restarting my guest machines they're going offline and freezing. we're having to force off/on these machines.

    Monday, June 22, 2020 11:20 AM
  • What does the event log from within the VM say the problem is?

    tim

    Monday, June 22, 2020 12:30 PM
  • So it looks like this is a common issue with Server 2016.

    I think *touch wood* I've managed to sort it.

    it's taken a long time to get to the resolution due to production server / wanting to spend my time out of hours.

    This problem was occurring on 2 of my Server 2016 VMs on the host.

    I've changed the page file on both VMs from automatic to 1024MB min and 10240MB Max on C.

    Increased the VHDX a little so there was enough free space (>10GB)

    I then went in to the startup and recovery > write debugging information and set this to none.

    I've rebooted lots of times and cannot replicate the problem.

    • Marked as answer by Alphanumbers Friday, July 3, 2020 3:16 PM
    Friday, July 3, 2020 3:15 PM