We have recently performed P2Vs of HP Proliant systems into our Virtual Infrastructure and have observed a strange but consistent behavior and don't know if the Guests or the Hosts are to blame. In a nutshell, when the VM Guests are booted/rebooted they would go through the VMware POST and then the Windows 2003 Logo boot screen with the grey horizontal scroll for about 3-4 times then the screen in the console window would go black. We would close the console window and open a new one only to observe that the VM Guest rebooted again and would repeat with the VMware POST and the Windows 2003 Logo boot screen but this time it would startup without incident. Anyone else experience this...even further, did those that observe this behavior resolve it? Thanks in advance.
We receive a System has shutdown unexpectedly error when logging in and correlated event in the system log. One thing to mention is that we exposed the devmgr_show_nonpresent_devices and removed all old devices from the device manager except for some in the 'Non-Plug and Play Drivers' as some of those can cause BSODs if removed. In addition, we have removed all hardware related software and disabled/removed from the registry any HP and or other hardware related services.
These were dual dual-core pCPU servers moving to 2 vCPU VM Guests. We have verified that we are still using the ACPI Multiprocessor PC driver. However, the driver seems pretty old dated 2002 with version 5.2.3790.1830. We used PlateSpin which automatically deploys the VMware Tools. Our procedures were identical during our last massive P2V effort but the only difference is that we are on 3.5U2 versus the last effort being on 3.5U1. We will attempt to redeploy the VMware Tools. Are there any other suggestions or other areas to review? Thanks.
Are you meaning using the /sfc option or just running through the repair through Windows setup?