I was seeing the same Event Log error in the same type of environment (ESXi 4.1 + Win2k8 R2). I followed the above suggestion, also thinking it odd that such a device even existed in Windows. The Event Log errors goes away on subsequent snapshots, but the snapshot still fails claiming it timed out trying to suspend I/O.
I'm seeing this on any VM I have SQL installed on. Does this match others experiences?
Hello. Was there a resolution to this? Or this is expected behavior? I am seeing similar Windows event logs for two brand new vSphere 5 virtual machines where one is running MS SQL 2008 R2 and the other is Exchange 2010 SP1. Both of these virtual machines have RDMs (created via SnapDrive and used by SnapManager for backups) and a dedicated VMDK (independent disk) for the Windows page file. NetApp Virtual Storage Console reports that it fails to backup the virtual machines because the resulting VMware snapshot fails along with these errors within Windows. No virtual floppy drive or controller was part of the virtual machine hardware, however, one is seen within Windows. Disabling the virtual floppy device controller and drive seems to address the event viewer issue but VMware snapshots still fail due to independent disks and/or RDMs. Related KB article:
I am having the same problem with smvi and protection manager. Working with ESXi 5.0U1 and smvi v4.1. I see this with machines that run SQL or Web services.
I found an interesting artifact from this. If you go to the VM that is failing, and look at the device manager's hidden devices:
To work around this behavior and display devices when you click Show hidden devices:
Click Start, point to All Programs, point to Accessories, and then click Command Prompt.
At a command prompt, type the following command , and then press ENTER:
Type the following command a command prompt, and then press ENTER:
Troubleshoot the devices and drivers in Device Manager.
NOTE: Click Show hidden devices on the View menu in Device Manager before you can see devices that are not connected to the computer.
You will see hidden disk drives, hidden storage volumes, and possibly hidden ShadowStorage devices.
If you clear all of these devices, you should get a good snapshot. But, in my test so far, they come right back and then the snapshot fails again.
My thought is that these extra devices represent the snapshot process creating shadows and that they aren't closing out properly and get left behind. Haven't gotten any further than that yet, but I am continuing to look and test.