[Bug 714361] New: VT-x/AMD-V Not found in Kernel 3.0

bugzilla at redhat.com bugzilla at redhat.com
Sat Jun 18 12:53:17 UTC 2011


Please do not reply directly to this email. All additional
comments should be made in the comments box of this bug.

Summary: VT-x/AMD-V Not found in Kernel 3.0

https://bugzilla.redhat.com/show_bug.cgi?id=714361

           Summary: VT-x/AMD-V Not found in Kernel 3.0
           Product: Fedora
           Version: rawhide
          Platform: x86_64
        OS/Version: Linux
            Status: NEW
          Severity: unspecified
          Priority: unspecified
         Component: virt-ctrl
        AssignedTo: extras-orphan at fedoraproject.org
        ReportedBy: spoffley at gmail.com
         QAContact: extras-qa at fedoraproject.org
                CC: extras-orphan at fedoraproject.org,
                    fedora-ocaml-list at redhat.com
    Classification: Fedora
      Story Points: ---


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:

-- 
Configure bugmail: https://bugzilla.redhat.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.


More information about the ocaml-devel mailing list