Hi all. I find myself confused with Server 2012 Hyper-V processes, and design as well.
First, and I'm just curious because it's odd, why when you create a new VM and a new VHDX to go with it, you don't have any choice of making it a Fixed Disk? Per Microsoft's own Technet articles on the subject, they recommend fixed-sized VHDs for production servers. Well thankfully production servers account for only a small percentage of the world's server population so forcing people to double their work by converting a newly creatd VHD makes sense! =P
:) Anyway I saw no way to make it a Fixed disk during creation - I can see some safeguarding concepts in that but is that their main reason for making it that way?
And to my question: the process seems to be that you Convert the disk, making a 2nd disk in the process and then to tell the VM to use the newly created VHD. This process hasn't gone successfully for me yet. I create a new VHDX via this conversion process, give it a slightly different name. I then Shut Down the VM and edit the VM properties to point to this new disk, which is in the same directory location as the old VHD. I go to start it up and I get "Boot Failure" (the actual error is longer but it's the standard one).
Thinking taht was odd, I repeated the whole thing again (after deleting previous VMs and VHDs). This time instead I converted the disk but saved it to a different location on the same physical disk on the server. I then deleted the VHD that was being used, renamed my new one, copied it over to the same path as where the old one was, and booted the VM. Nope, can't even get that far, I get aHyper-V error about the IDE/Atapi account not having permissions.
I have my share of problems with Windows 8 Client Huper-V as well - it just seems this stuff should be easy and yet I am constantly having problems with it at a fundamental usage level nevermind more advanced features.
Thank you for any insight and answers!