I installed the closed source version of virtualbox (last edition) in 11.1 KDE 3.5. When I try to install virtualized Opensuse 11.2 64 bit it tells me my PC is a 32 bit and not capable of doing this.
a) my PC is actually an AMD64 Athlon with a 64 bit installation of 11.1
b) the vbox software should in all case be able to run 64 bit OS even on 32bit OS host (if you accept the overhead.
Where did I do an error in setting up?
Is this eventually a known issue? Didn’t see any indication of this.
32bit OS run well on this installation. So the issue is limited to 64 bit.
Starting an 64 bit operating system with virtual box requieres VT-x or, in your case, the AMD-V CPU extension. Maybe this is not supported by your CPU and this case it is greyed like in my box (sorry, my screenshot is not in english but you should be able to find it).
(Or maybe the check for activating the acceleration is simply missing)
Or, if it is supported by your CPU, is not enabled in your BIOS. Chances
are very good that if it is not explicitly enabled (by you) it is disabled
by default (I’ve yet to see a machine otherwise).
Go into your BIOS and enable Virtualization.
Good luck.
On 04/05/2010 04:06 PM, daKump wrote:
>
> Starting an 64 bit operating system with virtual box requieres VT-x or,
> in your case, the AMD-V CPU extension. Maybe this is not supported by
> your CPU and this case it is greyed like in my box (sorry, my screenshot
> is not in english but you should be able to find it).
> (Or maybe the check for activating the acceleration is simply
> missing)
>
> [image: http://i41.tinypic.com/aw5lsj.png]
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Just for completeness, this will affect 64-bit virtualization with a lot
of technologies including (but not necessarily limited to) KVM, Xen,
vmware, etc.
Good luck.
On 04/05/2010 04:32 PM, ab@novell.com wrote:
> Or, if it is supported by your CPU, is not enabled in your BIOS. Chances
> are very good that if it is not explicitly enabled (by you) it is disabled
> by default (I’ve yet to see a machine otherwise).
>
> Go into your BIOS and enable Virtualization.
>
> Good luck.
>
>
>
>
>
> On 04/05/2010 04:06 PM, daKump wrote:
>
>> Starting an 64 bit operating system with virtual box requieres VT-x or,
>> in your case, the AMD-V CPU extension. Maybe this is not supported by
>> your CPU and this case it is greyed like in my box (sorry, my screenshot
>> is not in english but you should be able to find it).
>> (Or maybe the check for activating the acceleration is simply
>> missing)
>
>> [image: http://i41.tinypic.com/aw5lsj.png]
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Just to be clear, ACTIVATION is what you want, and not deactivation. It
should be an option in the BIOS and if not then either your process or or
motherboard (or both) is not going to support what you are trying to do.
It may be called ‘AMD-V’ somewhere in there. Sorry if not, though. The
technology has been around for a while and I think most systems have it
now (AMD or Intel) but it’s not required for a host machine to run 64-bit
so I imagine it’s left out of some processors/motherboards for cost reasons.
Good luck.
On 04/06/2010 01:36 AM, stakanov wrote:
>
> This must be an issue with the motherboard, it does not offer to
> deactivate the virtualization of the AMD Athlon 64.
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
Oh, well, i know activation is the issue. It is only that on Gygabite and other boards I did find the “AMD virtualization” function on “disable” or “enable”. So I have been mis understandable. I think your intuition is right but not for cost reason. My board (ASRock) has been one of the last 939 mainboards to be produced by them for AMD64, switching then to AM2, and was probably technically not prepared for the technology. Pity but at least I do not search for hours for the reason.
Linux does get us used to use older hardware because it runs flawlessly. It did for once not come to my mind that it is getting old. Socket AM2, AM2+ and AM3 came by already. I simply did not notice as the system with a good quantity of RAM still runs like build yesterday.
Thanks for your indications though.
