It doesn't matter what VM solution he uses - 64-bit virtual machines require VT-x extensions when using an Intel CPU. AMD supports segmentation, so you can have a fully software-virtualized 64-bit OS running, whereas Intel does not so it requires the hardware extensions.

Basically he needs to find the setting in his BIOS (it'll be labeled virtualization extensions, VT-x, etc.) and enable it, or dual boot.

Michael Wright

On Tue, Sep 20, 2011 at 2:38 PM, Connor Reed < conman2305@hotmail.[redacted] > wrote:

Jefferey,

When you boot into the BIOS, make sure that any sort of 'simplified' or 'easy' BIOS options aren't enabled. It should be somewhere under CPU or Advanced. If all else fails, you can use VMWare Player, which is free and just as good as VirtualBox, but it should allow you to disable Hardware Acceleration. That being said, it is a beast to set up in Linux, so try to get VirtualBox working first.

Good Luck,

Connor Reed

---

Date: Tue, 20 Sep 2011 17:07:55 -0400
Subject: Re: LUG: Virtual Machine Help
From: mewtamer@gmail.[redacted]
To: lug@lists.ncsu.[redacted]

According to the BIOS, my CPU is an Intel Core i7 2600 running at 3.4 Ghz. A quick google search brought me to this page: http://ark.intel.com/products/52213/Intel-Core-i7-2600-Processor-%288M-Cache-3_40-GHz%29 claiming that the CPU in question supports VT-x. Still cannot find a relevant option in the BIOS.

As for VirtualBox, it forces the acceleration on Virtual Machines configured for 64-bit Guest OSes. Switching to 32-bit helps none, as the copy of Win7 that came with the computer is strictly 64-bit. Beginning to wish I had had the forsight to make sure I had a copy of TinyXP either on my external hard drive or CD-R before leaving home.

The only thing I need Windows for at the moment is to re-flash my Android Phone(a Samsung Acclaim). My first attempt was to run the flashing software under Wine, but it stalls when it attempts to communicate with the phone. I would hate to have to set-up a dual-boot for a single application.

On Mon, Sep 19, 2011 at 11:24 PM, Brian Cottingham < spiffytech@gmail.[redacted] > wrote:

I'm not sure if it's complaining about something 64-bit, on virtualization extensions. You can try opening the settings for your VM and going to System -> Acceleration. Uncheck the VT-x/AMD-v box and see if the problem goes away.

Virtualbox seems to be shipping with hardware acceleration enabled by default, but many older CPUs (and some newer Intel CPUs) don't support virtualization extensions. If your BIOS doesn't mention VT-x or AMD-v this sounds like the likely problem to me.