No AV scanning that box. I'm getting an event id 3070 and 3040. Unnamed VM' failed to initialize. (Virtual machine 64EF49F6-3922-44E1-BB24-254088FE6650) That takes me to this link http://technet.microsoft.com/en-us/library/dd581971(WS.10).aspx
Check the environment in which the start virtual machine operation was being attempted, including: 1. access and permissions to the configuration file, memory file and all image files 2. prior error messages in the event log 3. available RAM on the system 4. configuration settings 5. disk space for the memory file and any expanding virtual hard disks All of these should've been OK. Just doing a straight upgrade. On Fri, Mar 26, 2010 at 8:08 AM, Miller Bonnie L. < mille...@mukilteo.wednet.edu> wrote: > Are you running any file-level AV software on the host server? That’s > the only thing I can think of that I’ve seen completely kill off guests like > that. http://support.microsoft.com/kb/961804. > > > > -Bonnie > > > > *From:* Steve Ens [mailto:stevey...@gmail.com] > *Sent:* Thursday, March 25, 2010 7:26 PM > > *To:* NT System Admin Issues > *Subject:* Upgrade from 2008 to 2008 r2 > > > > Kicked off an upgrade before I left of a Hyper V virtual machine. Went > through the upgrade and let it run. At home now, thinking the upgrade > should be finished. Taking a look at Hyper V Manager and the machine is > nowhere to be seen. I took a snapshot before I ran the upgrade, but that > doesn't show up in the console. The backup files do seem to be there, but > what's the easiest way to bring the server back from the dead? I've done > these upgrades a bunch of times on a test server, with no issues. ANy > ideas? > > > > > > > > > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
