virtualbox.org

I am not as technical as all of your but let me give this a try,

I am running Windows 7 from Windows Server 2012 R2 on a VPS, with 6GB of RAM and 2 Intel Xeon E5-2420 CPUs,

I want to select 2 CPUs, however Virtualbox sees 4 CPUs but the option to select more than one is greyed out.

Since it's a VPS i can't check in the BIOS if Virtualization is enable ... but (limited knowledge) it's a virtual server so it must be?

I tried Enableng I/O APIC after seeing that in another thread but to no avail.

So yea, i am lost and not too knowledgeable, any suggestions are very welcome.

If you are running Virtualbox in a virtualized environment, the main hypervisor being run on the VPS would have to pass VT-x through to the guest OS you are running Virtualbox in. If the hypervisor does not pass VT-x through to its guests, Virtualbox running in one of those guests will not see VT-x and won't run multi-processor guests or 64-bit guests, or recent 32-bit Windows that needs VT-x anyway.

If the main hypervisor the VPS is running is Virtualbox, you're definitely dead in the water. Virtualbox does not pass VT-x to a guest.

Hey Scott,

Sorry, can you explain that to me like i am five? and how i could find out the answers inside the VPS to what you said please? I want to progress with this but even after googling the terms you used i am confused.

Running one virtual platform inside another (e.g. VirtualBox inside a Hyper-v server platform) is called nested virtualization. We don't recommend nested virtualization for many reasons, one of which is that the VT-x CPU feature (hardware assisted for virtualization, like a GPU accelerates graphics) will not be available to VirtualBox because it is grabbed by the outer VM layer and not shared with the inner layers.

There are a number of features which VirtualBox cannot do if VT-x (or AMD-v) is not available. Among them is allocating >1 vCPU to a guest. Another is running any 64bit VM. Another is running any version of Windows from 8.0 onwards.