osuwildlifer, on 23 April 2012 - 11:18, said:
I'm curious as to the reasoning behind a default setting in Hyper-V server. When you initially configure the role, it lists the location of virtual hard disks. The default location it gives you is c:\Users\Public\Documents\Hyper-V\Virtual Hard Disks.
This seems like a slightly weird choice to me. Why did they make that the default location? Does it have to do with shared access to VMs? What benefits does putting them there provide?
A *default location* is generally the first place that an operating system (desktop or server) looks for things. It's no different in Hyper-V (or Windows Server 2K12) than in VirtualBox, VMware, Windows 8, or even Windows 7. This can be changed at VM-creation time (example - private VMs that you don't want shared at all); again, like any of the products I outlined above. That particular choice is because the default settings are for shared (public) VMs (hence that default location two levels down in the Public folder).
I've been kicking around Hyper-V in Windows Server 2K12 (formerly Windows 8 Server) because it's not as restrictive as the same feature is in Windows 8 (client) - SLAT is not a requirement, nor is 4 GB of RAM. (While I have 4 GB of RAM on the host, the Q6600 does not support SLAT. Fortunately, i5-2500k *does* support SLAT, so when I finally get the opportunity to finish my build, this issue goes away.)
I have one question regarding client (specifically, Windows XP) support in Hyper-V - how solid is it compared to other virtualization products (especially desktop virtualization)? I create primarily Windows-based VMs for application-level troubleshooting), and right now, I use primarily VirtualBox for this Being able to replace a third-party utility with an included with-the-OS utility sounds mighty attractive!