How to Manually Remove a Damaged Hyper-V Virtual Machine


If you see such errors in the Hyper-V event log, and fail to delete the damaged virtual machine in the Hyper-V manager. Just go to ‘C:\ProgramData\Microsoft\Windows\Hyper-V\Virtual Machines’ and delete the file which filename is  the same as the virtual machine ID. After that, the damage virtual machine should be gone in your Hyper-V manager. If … Continue reading How to Manually Remove a Damaged Hyper-V Virtual Machine

Hyper-V: A device attached to the system is not functioning


We have a Windows 2008 Hyper-V cluster VM failed every night in the past week. And it gives me the error: 'VM-01' Microsoft Emulated IDE Controller (Instance ID {83F84444B-8DCA-4152-9EDA-2CA8B33034B8}): Failed to Power on with Error 'A device attached to the system is not functioning.' (0x8007001F). (Virtual machine ID 1241E22E-E750-44C7-91F7-7588C8FBB9AE) After a quick search, I found … Continue reading Hyper-V: A device attached to the system is not functioning

SQL Server Virtualization Recommendations on Hyper-V


Nice article talking about the best practice of running SQL server on Hyper-V: http://mssqldude.wordpress.com/2011/11/02/sql-server-virtualization-recommendations-on-hyper-v/  Lock Pages in Memory. In fact, this is quickly becoming a STANDARD recommendation on all SQL Server boxes and VMs that are dedicated as database servers. Virtual SCSI-attached virtual disks for all data disks give the best performance for SQL Server. … Continue reading SQL Server Virtualization Recommendations on Hyper-V

Troubleshoot Hyper-V Cluster Node Blue Screen Issue


We had an incident last Friday – couple Hyper-V cluster nodes went to blue screen and rebooted themselves. With the Windows debugging tool and some knowledge of Cluster, I think I have figured it out. 1) Run Windows Debug Tool, and set the symbol path: SRV*C:\Symbols*http://msdl.microsoft.com/download/symbols 2) Copy the dump file to your local, the … Continue reading Troubleshoot Hyper-V Cluster Node Blue Screen Issue