Link to home
Start Free TrialLog in
Avatar of creativenetworks
creativenetworksFlag for United States of America

asked on

Hyper-V error

I am running Microsoft Server 2008 R2 patched out and attempting to run a Hyper-V session but can't seem to get it to go.

I get the following error in the Error Log:

'New Virtual Machine' could not initialize. (Virtual machine ID 36DB615D-5440-456E-A5D3-2902900C8562).

It's a brand new i3-2400 on a DP67BA Motherboard with 16gb of RAM and a clean 750gb HD.

I've verified that the bios is the latest release and that Virtualization is on in the bios.

Any ideas?
Avatar of Svet Paperov
Svet Paperov
Flag of Canada image

Do you have an antivirus running on the server? If yes, you need to exclude the VM configuration and VHD folders from it.

What is the event ID ?

Is this the first VM that you create or an existing one? Do you have problems with other VMs?
Avatar of creativenetworks

ASKER

Event ID is 3040.

I've never created a VM before and this is a test system I am trying to configure before I start to use it.  Needless to say, I'm a little bit frustrated by it at this point.

No AV on the server.  Just a new install of Server 2008 R2.
It seams as problem with permissions to me.

Did you try the steps from the blog http://technet.microsoft.com/en-us/library/dd581971%28WS.10%29.aspx ?
I just read that SP1 must be installed.  Downloaded and installing now.  Will follow upon completion.
ASKER CERTIFIED SOLUTION
Avatar of Svet Paperov
Svet Paperov
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Hyper-V runs but the VM's do not.  I apologize as it's an i5-2400 and it does support, and is turned on in bios.  I'll check the EDBF in the bios after SP1 installs.

Thanks!
After I installed SP1 the VM's would start.  I'm now attempting to install SBS 2011 NFR but think I may have a bad .iso file as it craps out at 24% each time.

I'll keep you posted on how this goes.
Bad .iso.  after download again, installed fine.  Was surprised to find out that SP1 was the culprit but found an interesting article where it was working for everyone.

I'll still aware points because I'm grateful for the help!

Thanks again