In this case, Windows Server 2003 R2 physical server was converted (captured) into guest VM on Hyper V cluster based on Windows Server 2012 operating system. Physical disk drives were successfully captured into VHDs. Virtual machine has booted successfully, and installation of hyper v integration services was initiated. Installation of integration services, was requesting reboot of the VM. After the restart, the VM was failing to boot with BSOD, and was complaining about WDFLDR.sys.
In order to fix this situation, I've booted the vm into last known good configuration. Checked the following registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000: There was Group (REG_SZ) value and was having Base for the value data.
Changing the data into WdfLoadGroup :
In order to fix this situation, I've booted the vm into last known good configuration. Checked the following registry key HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Wdf01000: There was Group (REG_SZ) value and was having Base for the value data.
Changing the data into WdfLoadGroup :
And, installing the Hyper V Integration Services has fixed the issues. Installation of Integration services requested for restart, and the VM has rebooted successfully (without BSOD).
No comments:
Post a Comment