Derek Lalor

Environment setup:
- HP DL580 G5 CPU x 4 +132GB RAM running Windows Server 2008 + SP1.
- Virtual machines are running Windows Server 2003 + SP2.

Originally the application environment was migrated to virtual platform by
building environment on new virtual machines and then simply copying those
VHDs into new VMs, dropping them off the network and rejoining under new
server name. I then noticed the behavior where VMs would go into perpetual
reboot after taking snapshot. The snapshots are saved on the same volume as
the VM host machine.

I did some research and hit upon a couple of posts reporting similar
behavior but the propsed resolution did not work. I then suspected this was
perhaps the result of not doing a proper sys-prep of the machines. I rebuilt
the environments using sys-prepped images and have encountered this behavior
again - I take a snapshot which is generated successfully, server then goes
into perpetual reboot, I reapply the snapshot but server then seems to have
been knocked off the network and I have to remove from AD and rejoin.

Below are errors from HyperV logs associated with this behavior. Has anyone
encountered this issue before. Should I perhaps be saving the snapshots to a
different volume?

Error #1:
The Virtual Machines configuration BCB9DC58-B50E-4DF0-A325-7944860B089F at
'E:\VM\<%SERVERNAME%>' is no longer accessible: The I/O operation has been
aborted because of either a thread exit or an application request.
(0x800703E3)

Error #2:
The Virtual Machines configuration BCB9DC58-B50E-4DF0-A325-7944860B089F at
'E:\VM\\<%SERVERNAME%>' is now accessible.