I used virtualization through VirtualPC 2007 on this computer, an Athlon 64 X2 4200+ with a Gigabyte GA-M55SLI-S4 motherboard, and it worked perfectly. The Athlon 64 X2 even support Hardware-Assisted Virtualization, so things actually run pretty smooth.
Now I've upgraded to Windows Server 2008 so I can run virtual machines with the new Hyper-V (RC0), but when I try to start any virtual machine it gives me an error saying "The virtual machine could not be started because the hypervisor is not running." What?? I just installed it. Did I miss configuring something?
The error dialog box has a "See details" linke, upon clicking this link it reveals the following information:
The virtual machine could not be started because the hypervisor is not running. The following actions may help you resolve the problem:
1) Verify that the processor of the physical computer has a supported version of hardware-assisted virtualization.
2) Verify that hardware-assisted virtualization and hardware-assisted data execution protection are enabled in the BIOS of the physical computer. (If you edit the BIOS to enable either setting, you must turn off the power to the physical computer and then turn it back on. Resetting the physical computer is not sufficient.)
3) If you have made changes to the Boot Configuration Data store, review these changes to ensure that the hypervisor is configured to launch automatically.
Um, ok… What's the problem. It sounds like it could be any number of things. Well, lets start checking things off the list.
1) Yes, I know my cpu supports hardware-assisted virtualization. AMD's documentation states so, and VirtualPC 2007 was able to use it.
3) Um.. I didn't change anything, so it wont be this.
Ok, it must something to do with option number 2.
Let go check the BIOS settings to make sure it's turned on; which it should be, after all it was working with VirtualPC 2007 just fine. Well, after inspecting my BIOS settings, I discovered that there isn't a setting in my motherboards BIOS to turn it on or off. Hmm… That's interesting.
Time to check for a BIOS update. Well, as it turns out, it doesn't look like Gigabyte has an update for my motherboard that will enable any virtualization features within the BIOS.
Stalemate… I guess I'll have to wait until the final release of Hyper-V or until may Gigabyte puts out a BIOS update for my motherboard.
I'm assuming the final release of Hyper-V wont support my motherboard/cpu configuration, since their main target for Hyper-V is server, but hopefully they take into account the scenario of using virtualization heavily in a development environment where you don't have a "server" class cpu in your machine.
Update 7/2/2008: I received the 11H BIOS update from Gigabyte for this motherboard (GA-M55SLI-S4) and it enabled Virtualization (AMD-V) in the bios perfectly.
Update 11/20/2008: You can download the GA-M55SLI-S4 11H BIOS Update here.
- 10 Oct 2020
- 01 Jul 2020
- 06 Apr 2020
- 11 Mar 2020
- 15 Feb 2020
Recent on Build5Nines.com
- 04 Dec 2020
Latest Cloud News: Apple on K8s, IoT, Microsoft Pluton and more! (November 20, 2020 Build5Nines Weekly)20 Nov 2020
Latest Cloud News: .NET 5 Released, Apple Silicon M1 CPU, and more! (November 12, 2020 Build5Nines Weekly)12 Nov 2020
- 11 Nov 2020
Latest Cloud News: Kubernetes, Terraform, Teams Multi-Login and more! (November 5, 2020 Build5Nines Weekly)05 Nov 2020
This site is a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to Amazon.com. We also participates in affiliate programs with Udemy, and other sites. This site is compensated for referring traffic and business to these companies.