[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Virtualbox 64 bit guest option is missing



On Fri, 24 Aug 2012 20:52:06 +0200, Artifex Maximus wrote:

> On Fri, Aug 24, 2012 at 3:51 PM, Camaleón <noelamac@gmail.com> wrote:

>>> The question is I need to upgrade my CPU to any VT capable CPU or is
>>> there any solution staying at the current CPU?
>>
>> Well, you can stil install a 32-bits guest OS but for 64-bits you need
>> a VT-x enabled micro, yes.
> 
> OK, now a lovely little E8400 power my machine which is VT-x and VT-d
> capable.
> 
> http://ark.intel.com/products/33910/Intel-Core2-Duo-Processor-E8400-%286M-Cache-3_00-GHz-1333-MHz-FSB%29

This one looks better, your system will thank (more cache, fsb speed yet 
still the same low TDP) :-)

>>> If I change the CPU am I need to reinstall Virtualbox?
>>
>> I don't think so.
> 
> Well. Still no 64 bit option and System/Acceleration tab is disabled in
> my Virtualbox. Any idea why? Motherboard? BIOS?

Sure, your BIOS has to provide an option to toggle "on" VT-x, if no, ask the 
manufacturer for a BIOS update or how to enable this.

And as you seem to be running a 64-bits host OS there shouldn't be more 
tweaks to do.

> My system is:
> "Linux artifex 3.2.0-3-amd64 #1 SMP Mon Jul 23 02:45:17 UTC 2012 x86_64 GNU/Linux"
> 
> dmesg:
> "[    0.051573] CPU0: Intel(R) Core(TM)2 CPU         E8400  @ 3.00GHz stepping 0a
> ...
> [    0.140066] Brought up 2 CPUs
> [    0.140068] Total of 2 processors activated (11970.46 BogoMIPS)."
> 
> vboxdrv related lines (what and why legacy support warning?): "
> [   55.378467] vboxdrv: Found 2 processor cores. 
> [   55.378878] vboxdrv: fAsync=0 offMin=0x22e offMax=0xc57 
> [   55.378926] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'.
> [   55.378928] vboxdrv: Successfully loaded version 4.1.18_Debian (interface 0x00190000).
> [   55.452749] vboxpci: IOMMU not found (not registered) 
> [  160.448576] warning: `VirtualBox' uses 32-bit capabilities (legacy support in use)"

I think the warning is harmless. I also get it from another native applications 
(e.g., ntpd) and IIRC, the message came from a library (libpcap) but is pointless.

Greetings,

-- 
Camaleón


Reply to: