Page 1 of 1

processors?

Posted: 8. Jul 2009, 06:31
by htc
i've googled like crazy and done just a little forum browsing but can't seem to find a list of supported processors.

i've run vmware5&6 extensively on an older amd processor that finally died, amd am going to make my first real build and have read the phenom's don't support virtualization. and in looking into processors on newegg it seems that even some of the newer intels don't (not sure though the listed virtualization supported there seems to be some type of intel virtualization.

was just wondering if there was a list some where of the processors that support virtualbox.

thanks, htc :?

Re: processors?

Posted: 8. Jul 2009, 11:19
by fixedwheel
htc wrote:and have read the phenom's don't support virtualization.
AFAIK all AMD socket AM2 and newer support virtualisation and even more nested paging, but the system boards BIOS has to support it too

info for intel CPU you get at processorfinder.intel.com enter the CPU family and in the results list toggle the features you want.



anyway, you actually need VT-x or AMD-V virtualisation support only for 64bit guests or guest SMP ...
sandervl in http://forums.virtualbox.org/viewtopic.php?t=1823 wrote:You are mistaken. VT-x and AMD-V are slower by design. Only the arrival of nested paging can change that.

Re: processors?

Posted: 8. Jul 2009, 16:18
by htc
i would swear i read in maximum pc some time ago that the first quad phenoms didn't support virtualization. may have to take another look at amd now though.

thanks so far, htc

Re: processors?

Posted: 8. Jul 2009, 18:13
by tlu
fixedwheel wrote: anyway, you actually need VT-x or AMD-V virtualisation support only for 64bit guests or guest SMP ...
sandervl in http://forums.virtualbox.org/viewtopic.php?t=1823 wrote:You are mistaken. VT-x and AMD-V are slower by design. Only the arrival of nested paging can change that.
Funny - I can't confirm this. I'm also having problems with SMP, and they vanish if I go back to 1 processor. However, if I disable VT-x my guest (Windwos XP 32-bit)becomes extremely slow which is contrary to what sandervl wrote. Perhaps something has changed in VB 3.0 since he wrote that?