On 09/22/2010 05:52 AM, Alexey Eromenko wrote:
>
>
> On Wed, Sep 22, 2010 at 11:43 AM, gilbert marzon
> <[email protected] <mailto:[email protected]>> wrote:
>
> Hi Alexey,
>
> Thanks to your reply, VT-x is on the system menu and yes
> its ticked,?please check the ?attached log file.
>
> Cheers,
>
>
>
>
> Having VT-x enabled in the GUI means nothing.
>
> VT-x is not active. Your CPU does not support it. "Pentium M's" don't
> support VT-x, only Core 1 Duo (Core Duo) or Core 2 Duo (some models).
>
> VirtualBox checks it, and runs your VM in software mode.
> Look at line 635 from your log:
> 00:00:01.552 HWACCM: No VT-x or AMD-V CPU extension found. Reason
> VERR_VMX_NO_VMX
>
> To make sure it is actually *active* -- you need to look at VirtualBox
> VM window (where your Guest OS runs), and mouse roll-over the "V"
> symbol, where you see network and disk activity of your VM
>
To note, I have quite a few systems that I run FreeBSD on that do not
have hardware virtualization support in the systems' CPUs.
Make sure you are using the latest version of VirtualBox as the version
3.0.8 has less support for FreeBSD (from what I remember).
------------------------------------------------------------------------------
Start uncovering the many advantages of virtual appliances
and start using them to simplify application deployment and
accelerate your shift to cloud computing.
http://p.sf.net/sfu/novell-sfdev2dev
_______________________________________________
VBox-users-community mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/vbox-users-community
