Solved Hyper-V, Macrium viBoot VM, slow shutdown

Since I enabled Hyper-V and run Macrium viBoot VMs, shutdown time increased dramatically (10+ minutes) whereas startup time did not increase, and the computer also did not slow down in normal operation.

Is the increased shutdown time normal?

Haydon said:

Since I enabled Hyper-V and run Macrium viBoot VMs, shutdown time increased dramatically (10+ minutes) whereas startup time did not increase, and the computer also did not slow down in normal operation.

Is the increased shutdown time normal?

Click to expand...

I've not used viBoot but not noticed anything out of the ordinary with Hyper V, VHDX or VMWare VM's

Haydon said:

Since I enabled Hyper-V and run Macrium viBoot VMs, shutdown time increased dramatically (10+ minutes) whereas startup time did not increase, and the computer also did not slow down in normal operation.

Is the increased shutdown time normal?

Click to expand...

No issue for me. You are closing down the viboot VM first?

In the Hyper-V Manager console, (viBoot) VM panel in the lower right:
What is Turn Off ...
What is Shut Down ...

Haydon said:

What is Turn Off ...

Click to expand...

A hard shoutdown, the same as killing the power for a physical machine while it's running.

Haydon said:

What is Shut Down ...

Click to expand...

An orderly shutdown of the OS, then turning off the power.

Continuing to troubleshoot the issue, I notice the following sequence.

Create new (viBoot) VM >
VM starts automatically because the pertinent box was ticked off >
Error message 'Enhanced session not available' >
Click OK >
VM restarts >
Lo and behold, the enhanced session window (empty brown screen) opens >
Click 'Basic session' button >
VM restarts >
Basic session window with my familiar desktop appears >
I can toggle between basic session and enhanced session without any error message appearing

Is this behavior normal?

Update: Shutdown time is now normal, but the little hiccup has become repeatable, it happens every time I create a new viBoot VM

Update #2: I'm very surprised to learn from the docs that the host OS also runs under Hyper-V!

Update #3: The viBoot VMs themselves appear to be OK , just the hiccup right before their 1st run remains unexplained.

Haydon said:

Update #2: I'm very surprised to learn from the docs that the host OS also runs under Hyper-V!

Click to expand...

This is because Hyper-V is a type 1 hypervisor. Here is a post I wrote a few years ago.





The MS docs are slightly misleading. The hypervisor is a layer that fits between the hardware and the OS. This layer is needed to run Hyper-V vms and is often referred to as Hyper-V. Hyper-V is really the management gui that interfaces with the hypervisor. It is rather semantics though as without Hyper-V installed, there is no type 1 hypervisor, so in effect they are the same thing.


If you did not have Hyper-V installed or type 2 system like virtualbox, system would simply be :



If you had Hyper-V installed, but no Hyper-V vms running, or any type 2 system, system would simply be :



So normally, if you have installed Hyper-V, with no vms running, system looks like above, and one might think there is a performance penalty. I have never detected an penalty in performance between having the hypervisor enabled or not.

MS docs are clear, IMHO. After enabling Hyper-V, Windows is just another VM, like viBoot, for example.

After the latest WU and MR update, all issues are gone.

I had been chipping away at the issues before that, though. My note taking in all this could have been better, next time something similar happens, I would have to reinvent the steps taken.

In any case, all issues have disappeared, I will mark this thread 'Solved', thanks to all who responded

Haydon said:

MS docs are clear, IMHO. After enabling Hyper-V, Windows is just another VM, like viBoot, for example.

View attachment 29137

Click to expand...

That is really a simplification of things. Hyper-V is only one type of hypervisor - there are others e.g. ESXi

Thus the hypervisor layer is not necessarily Hyper-V based (or even Windows based)

MS documents show it like that, but that is because they only talk about Hyper-V

In the end, it is semantics if you install Hyper-V as your hypervisor tool.

I don't think my graphics is that much of a simplification, here is another one, which is snipped from Wikipedia. Of course MS talks about Hyper-V only, that's the exact name of their native (bare metal) hypervisor product.

Haydon said:

I don't think my graphics is that much of a simplification, here is another one, which is snipped from Wikipedia. Of course MS talks about Hyper-V only, that's the exact name of their native (bare metal) hypervisor product.

View attachment 29143

Hypervisor - Wikipedia

en.wikipedia.org

Click to expand...

That is the same as my original picture - just drawn differently.

And that's the same as my picture just with specific names :)

Haydon said:

And that's the same as my picture just with specific names :)

View attachment 29151

Click to expand...

er yes, obviously......

So, we are in agreement then :)

BTW, I made that specific picture myself (using PowerPoint and Paint) to suit the topic and title of this thread. It's not a picture that I got from MS, MR, Wiki or from anywhere else. I think you made your own pictures too

Haydon said:

So, we are in agreement then :)

BTW, I made that specific picture myself (using PowerPoint and Paint) to suit the topic and title of this thread. It's not a picture that I got from MS, MR, Wiki or from anywhere else. I think you made your own pictures too

Click to expand...

No mine were images pasted from online articles.

Hi there

@cereberus

If you say install an OS on a physical VHDX without enabling HYPER-V there's obviously a "Skeltal OS" running to present in GUI form a menu to select an OS to load, accept input from the user and load the desired OS from a Disk or even a USB device in the first place -

e.g

So what is this OS - it must be some sort of minimal OS to be able to present a GUI and run a boot loader to select an OS from the menu.

Cheers
jimbo