Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. Applying storage QoS policy fails with unsupported operating system in SCVMM 2016

Applying storage QoS policy fails with unsupported operating system in SCVMM 2016

View products that this article applies to.

Symptoms

When you try to apply a storage QoS in System Center Virtual Machine Manager, you receive the following error message:

The Storage QoS Policy '<policy GUID>' cannot be applied to a VHD for a virtual machine on a host that runs an unsupported operating system.

↑ Back to the top

Cause

Windows Server 2016 Storage Quality of Service (QoS) policies can be applied only to virtual machines that are running Windows 2016 hosts and VM version 8.0 or later.

↑ Back to the top

Resolution

To resolve this issue, make sure that the following conditions are true:
  • The virtual machine is on a Windows Server 2016 host.
  • The VM version is 8.0 or later. The VM version is displayed on the General tab when you view the VM properties.

    To upgrade the VM version, follow these steps:
    1. Shut down the virtual machine.
    2. On the VMM console, right-click the virtual machine, and then select Update Functional Level.

↑ Back to the top

More Information

For more information, see Storage Quality of Service.

Storage QoS supports two deployment scenarios:
  • Hyper-V using a Scale-Out File Server
    This scenario requires both of the following:
    • Storage cluster that is a Scale-Out File Server cluster
    • Compute cluster that has least one server with the Hyper-V role enabled

    For Storage QoS, the Failover Cluster is required on Storage servers, but the Compute servers don't have to be in a failover cluster. All servers (used for both Storage and Compute) must be running Windows Server 2016. If you don't have a Scale-Out File Server cluster deployed for evaluation purposes, see Windows Server 2012 R2 Storage: Step-by-step with Storage Spaces, SMB Scale-Out and Shared VHDX (Physical). This contains step-by-step instructions to build one by sing either existing servers or virtual machines.
  • Hyper-V using Cluster Shared Volumes
    This scenario requires both of the following:
    • Compute cluster with the Hyper-V role enabled. 
    • Hyper-V using Cluster Shared Volumes (CSV) for storage - Failover Cluster is required. All servers must be running the same version of Windows Server 2016. 

↑ Back to the top

Keywords: kb

↑ Back to the top

Article Info
Article ID : 3198624
Revision : 1
Created on : 1/7/2017
Published on : 10/19/2016
Exists online : False
Views : 399