question

Joe-1392 avatar image
0 Votes"
Joe-1392 asked ·

VMHostSupportedVersion update config version

When can I update my VMs? According to the docs here: https://docs.microsoft.com/en-us/windows-server/virtualization/hyper-v/deploy/upgrade-virtual-machine-version-in-hyper-v-on-windows-or-windows-server#supported-vm-configuration-versions-for-semi-annual-channel-hosts

v1903 should allow me to update to 9.1

Edition Windows 10 Pro
Version 20H2
Installed on ‎8/‎14/‎2020
OS build 19042.844
Experience Windows Feature Experience Pack 120.2212.551.0

I'm running version 1904 according to the above string.


> Get-VMHostSupportedVersion

Name Version IsDefault
---- ------- ---------
Microsoft Windows 10 Anniversary Update/Server 2016 8.0 False
Microsoft Windows 10 Creators Update 8.1 False
Microsoft Windows 10 Fall Creators Update/Server 1709 8.2 False
Microsoft Windows 10 April 2018 Update/Server 1803 8.3 False
Microsoft Windows 10 October 2018 Update/Server 2019 9.0 True
Microsoft Windows 10 May 2019 Update/Server 1903 9.1 False
Microsoft Windows 10 May 2020 Update/Server 2003 9.2 False

but it does not work.

> Update-VMVersion myvm -Force
WARNING: No update was performed for the virtual machine "myvm" because its configuration version is already
at the maximum level supported by this server. For clustered servers, the maximum supported configuration version can
be limited by the cluster functional level.


Is there something I need to do to enable this update feature that exists on my host?



windows-server-hyper-vwindows-10-virtualization
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

XiaoweiHe-MSFT avatar image
0 Votes"
XiaoweiHe-MSFT answered ·

Hi,

According to the "Get-VMHostSupportedVersion", version 9.1 and 9.2 is not supported, so the VM is unable to update configuration version, would you please run "winver" in powershell and then show the screenshot of the Hyper V host system version for us.

Thanks for your time!
Best Regards,
Anne


If the Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our [documentation][20] to enable e-mail notifications if you want to receive the related email notification for this thread.
[20]: https://docs.microsoft.com/en-us/answers/articles/67444/email-notifications.html

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Joe-1392 avatar image
0 Votes"
Joe-1392 answered ·

This appears to be the same information I already provided above. What else do you need?


75592-image.png



image.png (14.1 KiB)
·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Joe-1392 avatar image
0 Votes"
Joe-1392 answered ·

I'm not sure if you understand my question.

Microsoft Documentation says that semi-annual release channel should support VM Configuration version 9.1.

I am on that channel from what I can tell, and my windows version is higher than the documentation says supports 9.1 (Windows 10 May 2019 Update (version 1903)).

In fact, my host even says it supports 9.1 AND 9.2 (which is not even in documentation) but they are not default..? Is that correct?

So, where is the disconnect here between the documentation and reality? Why does my host not support what documentation says it should?

·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

ejsiron avatar image
0 Votes"
ejsiron answered ·

I haven't looked at these in a while, but I had not ever heard that 9.1 or 9.2 moved out of "experimental" status. They have no feature or fix data beyond 9.0. I have a lot of suppositions that I could make here, but the only guess that I've got enough background to publish would be that if you get your hands on a v9.1 or v9.2 VM, it will run on this host. The ability to run a VM at that level does not necessarily mean that it can update VMs to that level.

· 3 ·
10 |1000 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

I feel you, but the docs literally say

The following table lists the VM configuration versions for hosts running a currently supported semi-annual channel version of Windows

which implies that configuration version 9.1 is a valid and usable version on a windows version OLDER than what I have installed/running, so why wouldn't I be able to upgrade the configuration version to that?

Further, the article with the feature data was last updated on 05/22/2019 which is just after 9.1 was supposedly available as 'valid'... so, why start listing 9.1 as valid/available when it's not?

0 Votes 0 ·

Well, again, the ability to read a file and the ability to transform a file do not necessarily go hand-in-hand. Without inside knowledge, the most likely probability is that 9.1 and 9.2 versions exist somewhere, but don't have sufficiently compelling changes for Microsoft to produce a public transform routine that they would then need to support. It's also possible that these versions embed information that only makes sense in Azure, which would mean there's no point in adding an on-premises transform routine. Don't lose sight of the fact that the only thing that we know for certain about these versions is that they have higher version numbers. Version 9.0 implements all known Hyper-V functionality and has no published defects.

1 Vote 1 ·

Hi,

Thanks for your information, I will try to feedback the issue with MS and trying to confirm if VM configuration version 9.1 is available on Host OS version 1904.

Best Regards,
Anne

0 Votes 0 ·