Backtrack not loading---CPU doesnt support VT-x

[rtcwlomax]

Hi All,

First post and a complete noob to Backtrack and VM so looking for some advice.

I have tried to load Backtrack 5.2 through Virtualbox and keep getting the following error

This kernel requires x86-64 CPU, but only detected an i686 CPU. Unable to boot - please use kernel appropriate for your CPU.

Having done some searching around I found that enabling VT-x on the CPU will solve this problem however I also discovered that my CPU does not support VT-x.

After further searching I cant seem to find another solution. Has anybody got any ideas how to fix or should I D/L another version of Backtrack? Would a BIOS update help if there is one availible?

System Info:
OS Name Microsoft Windows 7 Home Premium
Version 6.1.7601 Service Pack 1 Build 7601
Other OS Description Not Available
OS Manufacturer Microsoft Corporation
System Name DELL-PC
System Manufacturer Dell Inc.
System Model Studio 1555
System Type x64-based PC
Processor Intel(R) Core(TM)2 Duo CPU P7450 @ 2.13GHz, 2133 Mhz, 2 Core(s), 2 Logical Processor(s)
BIOS Version/Date Dell Inc. A11, 29/03/2010
SMBIOS Version 2.5
Windows Directory C:\Windows
System Directory C:\Windows\system32
Boot Device \Device\HarddiskVolume2
Locale United Kingdom
Hardware Abstraction Layer Version = "6.1.7601.17514"
User Name DELL-PC\Damien
Time Zone GMT Daylight Time
Installed Physical Memory (RAM) 3.00 GB
Total Physical Memory 2.99 GB
Available Physical Memory 1.90 GB
Total Virtual Memory 5.99 GB
Available Virtual Memory 4.69 GB
Page File Space 2.99 GB
Page File C:\pagefile.sys

[digimaori]

Hey ya,

Sorry this cpu dose not support Virtualization Technology, only way to get bt working on your lappy is to do a dual boot running windows and linux on the same MBR

Chur

Digi

[scottm99]

I've never used Virtualbox, but always had good luck with 32-bit versions of BackTrack under VMWare products. I use VMWare Workstation now, and have used the free VMWare Server.

[rtcwlomax]

thanks for replies guys.

The Gnome 32bit version of BT5 has worked for me without this issue