Bug 714361

Summary: VT-x/AMD-V Not found in Kernel 3.0
Product: [Fedora] Fedora Reporter: Stephen <spoffley>
Component: kernelAssignee: Kernel Maintainer List <kernel-maint>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: rawhideCC: aquini, extras-orphan, fedora-ocaml-list, gansalmon, itamar, jonathan, kernel-maint, madhu.chinakonda, rex.cc.tsai, rjones
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-30 07:24:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Stephen 2011-06-18 12:53:16 UTC 
Description of problem:

I have Four virtual machines set up in VirtualBox, 3 are 64 Bit windows and one is a 32 Bit Linux Distribution.  Using version 4.08 of VirtualBox, on Kernel , 3.0-0.rc3.git0.3.fc16.x86_64 the VT-X/AMD-V Acceleration is not found, using the same version of VirtualBox on Fedora 14, Kernel 2.6.35.13-92.fc14.x86_64 it works correctly.  This means that under Fedora 14 I can run both my 32 bit Virtual machine and my 64 Bit Virtual machines, however in Rawhide I can only run my 32 Bit machine.

This was Ok until the update to Kernel 3.0.  My processor is an Intel Core 2 Solo, SU3500

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.  Run VirtualBox, Machine settings no longer show the VT-x/AMD-V setting
2.
3.
  
Actual results:

64 Bit Virtual machines no longer run under Kernel 3.0

Expected results:

64 Bit Virtual machines should run, as they did under kernel 2.6
Additional info:
Comment 1 Richard W.M. Jones 2011-06-18 18:28:39 UTC 
No idea what the component should be, but not virt-ctrl.
Comment 2 Rex Tsai 2011-06-29 15:17:40 UTC 
This issue will be fixed in 4.0.10 http://www.virtualbox.org/ticket/9071
Comment 3 Chuck Ebbert 2011-06-30 07:24:04 UTC 
virtualbox bug, not a kernel bug