Most Popular in Linux
-
GNOME Login Screen Mockups, Videos
-
FSFE on AVM v. Cybits
-
Why we should allow DRM on open source platforms
-
Pentaho Business Analytics Gets an In-Memory Boost
-
Examining Stallman's Law
-
Greg Kroah-Hartman moves to the Linux Foundation
-
Apple Might Lose A $1.6 Billion Lawsuit For Using The Word 'iPad'
-
Sprint Reports Strong iPhone Sales in Q4 2011
-
Canonical's Ubuntu System Management Service Landscape become default in Ubuntu 12.04
-
Ubuntu 10.10 (Maverick Meerkat) end-of-life reached on April 10, 2012
Can you help fix my broken VM?
Can you help fix my virtual machine? (details inside) Running Virtualbox 3.2.6
Host machine: Windows 7 (64bit - Enterprise edition) on a compal hel80 with a Core 2 Duo T7200
The guest machine is Gentoo Linux (also 64 bit).
Everything was working fine until this morning. The host machine went to sleep while the guest was running. When I woke it up, the machine Blue Screened. After restarting, I tried to launch the guest and I receive the error "This kernel requires an x86-64 CPU, but only detected an i686 CPU."
In the virtualbox log I found the following:
HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_MSR_LOCKED_OR_DISABLED
HWACCM: VMX_MSR_IA32_FEATURE_CONTROL=1
There's no option in my bios to enable virtualization, but I assume it's on since I was able to run the guest successfully in the past.
I tried uninstalling virtualbox and reinstalling - using the same guest, but to no avail. I also tried booting (the guest machine) off the install cd, but get the same error. I made a new machine using the same virtual harddrive - same error.
Any other suggestions?
Host machine: Windows 7 (64bit - Enterprise edition) on a compal hel80 with a Core 2 Duo T7200
The guest machine is Gentoo Linux (also 64 bit).
Everything was working fine until this morning. The host machine went to sleep while the guest was running. When I woke it up, the machine Blue Screened. After restarting, I tried to launch the guest and I receive the error "This kernel requires an x86-64 CPU, but only detected an i686 CPU."
In the virtualbox log I found the following:
HWACCM: No VT-x or AMD-V CPU extension found. Reason VERR_VMX_MSR_LOCKED_OR_DISABLED
HWACCM: VMX_MSR_IA32_FEATURE_CONTROL=1
There's no option in my bios to enable virtualization, but I assume it's on since I was able to run the guest successfully in the past.
I tried uninstalling virtualbox and reinstalling - using the same guest, but to no avail. I also tried booting (the guest machine) off the install cd, but get the same error. I made a new machine using the same virtual harddrive - same error.
Any other suggestions?
More Stories in Ask Metafilter: Linux
- Chumby & Last.fm
- How do I increase partition size in a RAID 1 array with minimal downtime?
- Boot ubuntu to the commandline
- I don't have the money, honey--but it's got the time.
- Flash Video Troubles
- halp i losted mah bricks
- SSH with telnet -e as a ForceCommand: secure?
- Whoa, Whumpscutt followed by Vivaldi is jarring...
- TCP WTF
- Linux (Ubuntu) filter: Why aren't my login supplementary groups correct?
Most Popular Stories
A fix for those "Pairing Record Missing" errors
Net Calculator
Coolest keyboard ever
Diablo 3 Slow on Mac? Here is a Solution
ILOM Sunservice login incorrect
7 Online Resources To Trace The History Of Your House
Daily iPhone App: Elenints matches Triple Town's planning with a few new tricks
Planning Board Rendering Unveils New Glass-Enclosed Apple Store for Stanford
Jumpstart Error: Unsupported version (3.0).
Fieldrunners 2 coming next month