From: Tim Daneliuk on
On 12/19/2009 7:04 AM, Helmut Schneider wrote:
> Tim Daneliuk wrote:
>
>> I have a machine running Win/XP Pro SP3 hosting VirtualBox 3.1.
>
> And XP is XP64?! You cannot virtualize a 64bit OS within a (Windows)
> 32bit environment.
>
> Helmut

Yup, I've discovered that this is, indeed, the problem.

--
----------------------------------------------------------------------------
Tim Daneliuk tundra(a)tundraware.com
PGP Key: http://www.tundraware.com/PGP/

From: Tim Daneliuk on
On 12/19/2009 9:21 AM, Tim Daneliuk wrote:
> On 12/19/2009 7:04 AM, Helmut Schneider wrote:
>> Tim Daneliuk wrote:
>>
>>> I have a machine running Win/XP Pro SP3 hosting VirtualBox 3.1.
>>
>> And XP is XP64?! You cannot virtualize a 64bit OS within a (Windows)
>> 32bit environment.
>>
>> Helmut
>
> Yup, I've discovered that this is, indeed, the problem.
>

Well ... that wasn't it after all. I get the same exact problem
using Ubuntu 64 bit at the host.

--
----------------------------------------------------------------------------
Tim Daneliuk tundra(a)tundraware.com
PGP Key: http://www.tundraware.com/PGP/

From: Michael Sierchio on
Warren Block wrote:
> Tim Daneliuk <tundra(a)tundraware.com> wrote:
>> I have a machine running Win/XP Pro SP3 hosting VirtualBox 3.1.
>>
>> The hardware happily boots the Ubuntu amd64 CDROM natively and FreeBSD 8.0
>> also boots fine - well ... up to the point where it has to ID the hard
>> drive, but that's another story.
>>
>> IOW, the hardware is 64-bit capable (It is an Intel mobo w/a Pentium-D
>> 940 w/EMT64 option).
>>
>> HOWEVER, when I run VirtualBox and try to install the 64 bit version
>> of FreeBSD in a VM, it get a "CPU doesn't support long mode" error
>> during the FreeBSD virtual booting process. FreeBSD 8.0 i386 works
>> fine.
>>
>> 'Anyone run across this before and/or have a fix?
>
> Not me, but some suggest it involves enabling virtualization settings in
> the BIOS:
>
> http://www.virtualbox.org/ticket/2061

I have a T9300 -based laptop, with virtualization enabled in the BIOS,
and get the same error.