Virtual Machines - Hyper V - Rampage V Extreme Errors

[Counteragent]

Hi Guys,

After some help on an issue I'm having. I'm running Rampage V Extreme MB with Extreme CPU, and I've installed Hyper V to my Windows 10 Machine.

When I attempt to load a virtual machine, either one I've exported and a newly created one I receive an error along the lines of:

The application encountered an error while attempting to change the state of

failed to start.

So I went into BIOS and ensured the Virtualization was ENABLED and re booted and same problem.

Do you think this is a BIOS issue?

When Machines first posts I see this:

ACPI BIOS Revision 0603

Do I need to update BIOS?

I'm running several RAID Arrays whats the best way to go here? Unplug SATA cables from all HDDs n update BIOS?

Cheers

[Nate152]

Hello Counteragent

You can let all your hardware connected when performing the bios update. Here is a guide you can follow, rename the bios file to R5E.CAP

You might lose your raid though.

Let's hope this fixes you up. 🙂

http://rog.asus.com/forum/showthread.php?1142-How-to-use-ASUS-ROG-USB-BIOS-Flashback

[Nate152]

After reading this I don't think it's a bios problem.

http://vdinotes.com/2013/08/07/hyper-v-2012-logon-failure-errors-and-fix/

[Korth]

Korth wrote:
I went for the Xeon E5-1680-3 proc ...
2) I also realize the R5E mobo isn't specifically engineered for the server market. But do the BIOS workarounds/fixes/errata identified in the Intel Xeon E5-3 Processor Specification Update tend to be fully implemented? (Aside, perhaps, from irrelevant errata involving ECC, RDIMMs, etc.)

Understand that Haswell-E (Core i7) and Haswell-EP (Xeon) procs are basically interchangeable in this context, mainly because these i7 procs have evolved from (or are actually low-binned E5 parts) built around Xeon-based architectures.

This Intel errata document identifies all sorts of "bugs" within the processor - many of these processor-related issues can't be fixed (yet), many can be fixed (by Intel) in processor microcode revisions, many can be fixed (by mobo manufacturers like Asus) in chipset firmware updates. Many of the errata involve advanced instructions used by things like virtual machines and hypervisors.

Asus is very protective (almost paranoid) with their proprietary firmware, they evidently don't want to give away any advantages to the competition, their documentation is woefully vague. For end-users this means we'll never know whether they've implemented any firmware-level workarounds for processor design flaws which affect hypervisor execution.

[Counteragent]

Korth wrote:
Understand that Haswell-E (Core i7) and Haswell-EP (Xeon) procs are basically interchangeable in this context, mainly because these i7 procs have evolved from (or are actually low-binned E5 parts) built around Xeon-based architectures.

This Intel errata document identifies all sorts of "bugs" within the processor - many of these processor-related issues can't be fixed (yet), many can be fixed (by Intel) in processor microcode revisions, many can be fixed (by mobo manufacturers like Asus) in chipset firmware updates. Many of the errata involve advanced instructions used by things like virtual machines and hypervisors.

Asus is very protective (almost paranoid) with their proprietary firmware, they evidently don't want to give away any advantages to the competition, their documentation is woefully vague. For end-users this means we'll never know whether they've implemented any firmware-level workarounds for processor design flaws which affect hypervisor execution.

So to get to the short n curlies of it, to just put it straight forward *ITS not going to work?*

Does anyone else run Hyper V virtuals on their Rampage V Extreme?

You don't think a BIOS update may resolve this?

[Nate152]

Does this help you Counteragent?

http://www.howtogeek.com/76532/how-to-install-or-enable-hyper-v-virtualization-in-windows-8/

[Counteragent]

Nate152 wrote:
Does this help you Counteragent?

http://www.howtogeek.com/76532/how-to-install-or-enable-hyper-v-virtualization-in-windows-8/

g'day Nate152,

Yes I can confirm Hyper V has been installed from the Features area.. I done this first up when I found it was not by default... I know its installed as I go into the application, create my Hyper V machine with the settings and I get the error when I try starting the Hyper V Machine.

[Korth]

If you can identify the exact cause of failure then you can look it up in Intel errata documents.

If you want to confirm/deny whether specific fixes have been implemented in BIOS then you need to use a server-supported motherboard (like the SuperMicro C7X99-OCE, for example) which comprehensively documents every issue the manufacturer addressed. I've never seen Asus provide such answers before.

But you're running an R5E with BIOS 0603? There have been ten BIOS revisions since 0603. I would install the latest R5E firmware (BIOS 1701) - it may turn out that Asus has already fixed your particular HyperV issue for all we know.

[Counteragent]

Korth,

Thanks mate you've given me some hope.

I'm not very familiar with updating the BIOS etc.. as I understand the MB has 2 BIOS chips. Is there a feature within the BIOS where I can say for example copy BIOS 1 to BIOS 2 and then update BIOS 1?

And in the event of any errors / problems I can go to BIOS 2 n bring PC up?

Cheers

[Nate152]

Read my last post before trying a bios update, it may be your solution.