~ Chuck Timon | Senior Support Escalation Engineer
Welcome back! In this post, I want to talk about a customer issue that, from a System Center Virtual Machine Manager perspective, is something a little out of the ordinary.
A customer uses System Center 2012 R2 Virtual Machine Manager (VMM 2012 R2) to manage standalone Hyper-V servers. The servers are configured with Dynamic Disks formatted with NTFS partitions. The Dynamic Disks host virtual machine files, and drive letters and volume labels are assigned. Here is an example:
Before I go further, I want to be clear that I mean 'Dynamic Disks' in the context of a Host and not a virtual machine. For those who need a quick refresher, please see the following:
The primary problem in this case involves the path to the destination storage for the virtual machine files. If a virtual machine is created locally on the Hyper-V server itself, a drive letter (associated with the path to the local storage) is available when selecting a destination for the virtual machine files and is reflected in the configuration after the virtual machine is created.
When deploying a virtual machine to the same Host using VMM, a drive letter is not available in the wizard. Instead, a volume GUID with a label is presented as a selection to the user.
After the deployment completes, an inspection of the virtual machine properties shows the path with the volume GUID:
Does it work? Yes it does. As you can see here, I have two virtual machines hosted on this Dynamic Disk (
), one created in Hyper-V and the other in VMM, and they are functioning properly.
The concern from the customer perspective is that it is an inconvenience having to remember GUIDs, and not having a drive letter (in the VMM UI only) could cause confusion for their users. However, implementing meaningful labels for these Dynamic Disks could help resolve a lot of the confusion.
The bottom line is that Dynamic Disks are rarely used in a virtualization environment to host virtual machine files, and they are being deprecated going forward. Therefore, at some point in the future, they will no longer be relevant. Nevertheless, this will be brought to the attention of our Product Team.
This issue is also applicable in System Center 2012 Virtual Machine Manager Service Pack 1 (SP1).
Thanks, and come back again soon!
Chuck Timon | Senior Support Escalation Engineer | Microsoft Enterprise Platforms Support