Problem with differencing VHDx in hyper-v 2012 R2

Question

hi friends
in my windows 2012 R2 Datacenter, i deployed a windows server 2012 R2 Datacenter VM ( i selected its hard disk be Dynamically expanding VHDX) & installed OS & then i syspred it & turned it off & removed that VM from hyper-v snap-in.
now i tried to use that as a parent VHDX for Differencing child VHDXs for a new VM.
so i created a new VM & created a differencing VHDx which has that is parent.
the problem is when i turn on the VM, its doesn't boot & i get the following strange error:
i also checked event viewer for all hyper-v nodes in Application & services logs but there is no error & all events describe that VM has started successfully.
what to it can be related?
i have done the same scenario for win 2008 R2 enterprise VMs (VHD hard disk) many times & there was never such problem.
is it isue related to VHDX hard disks?
help please
thanks in advanced

Answer 1

The config looks OK for this Gen 1 VM, except the odd memory configuration.
Can you look up the Hyper-V logs on the host:
particularly hypervisor/operational and VMMS/admin?
You can use Powershell to collect the logs if you like.
Here's a sample script. After running the script to load the function you can run:
Get-HVEventLog -Computername MyHVHost-Days 7
Sam Boutros, Senior Consultant, Software Logic, KOP, PA http://superwidgets.wordpress.com (Please take a moment to Vote as Helpful and/or Mark as Answer, where applicable) _________________________________________________________________________________
Powershell: Learn it before it's an emergency http://technet.microsoft.com/en-us/scriptcenter/powershell.aspx http://technet.microsoft.com/en-us/scriptcenter/dd793612.aspx
Sam,
i corrected the memory settings & assigned static memory as 1024 MB.
there was two blocks of scripts in that website, i don't which of them i must run.
i verified my event viewer as i had done earlier, i the following are the only events which are are logged in all hyper-v related notes:
hyper-v-hyperVisor node:
Hyper-V successfully created a new partition (partition 3).
Hyper-v-synthnic node:
'test4' Network Adapter (7F8B9901-BBF5-4541-B586-33A5EE906B49) started successfully. (Virtual Machine ID D3589B09-C269-46CE-9BD1-51A3C95C04BF)
'test4' Network Adapter (d3589b09-c269-46ce-9bd1-51a3c95c04bf--7f8b9901-bbf5-4541-b586-33a5ee906b49) Disconnected from virtual network. (Virtual Machine ID D3589B09-C269-46CE-9BD1-51A3C95C04BF)
Hyper-v-worker node:
'test4' started successfully. (Virtual machine ID D3589B09-C269-46CE-9BD1-51A3C95C04BF)
and also in Custom node\ Administrative events, an error is logged continuously ---->
 Microsoft-Windows-Kernel-EventTracing/Admin :
Session "" failed to start with the following error: 0xC000000D (event ID 2)