cannot create VM with PAE

[flyingfrog81]

Cannot create the VM with Vagrant using more than 2048MB of RAM and 1 CPU, also we need to disable PAE by inserting in the Vagrantfile, the only working configuration is this:

  config.vm.provider "virtualbox" do |vb|
    vb.name = "azdora"
    vb.memory = 2048
    vb.cpus = 1
    vb.customize ["modifyvm", :id, "--pae", "off"]
  end

The system is configured as:
host : Scientific Linux release 6.6 (Carbon)
VBox : Oracle virtualbox 4.3.24r98716

[flyingfrog81]

The host has both pae and svm enabled, the host cpu is a: Dual-Core AMD Opteron(tm) Processor 2218

[flyingfrog81]

Maybe there is something related to the Virtual Box guest additions, we are using a base CENTOS box from https://atlas.hashicorp.com/puppetlabs/boxes/centos-5.11-32-nocm
After installing the vagrant-vbguest plugin it will update the guest additions of the running VM but only after the first boot so we still need to run the machine without pae for the first boot to succeed.

==> default: Machine booted and ready!
GuestAdditions versions on your host (4.3.24) and guest (4.3.16) do not match.
..
...
Installing Virtualbox Guest Additions 4.3.24 - guest version is 4.3.16

then we power cycle the VM and we have:

==> default: Machine booted and ready!
GuestAdditions 4.3.24 running --- OK.

then we halt the machine and modify the vagrantfile back as it should be:

  config.vm.provider "virtualbox" do |vb|
    vb.name = "azdora"
    vb.memory = 4096
    vb.cpus = 2
  end

and we get the usual error:

==> default: Waiting for machine to boot. This may take a few minutes...
The guest machine entered an invalid state while waiting for it
to boot. Valid states are 'starting, running'. The machine is in the
'poweroff' state. Please verify everything is configured
properly and try again.

If the provider you're using has a GUI that comes with it,
it is often helpful to open that and watch the machine, since the
GUI often has more helpful error messages than Vagrant can retrieve.
For example, if you're using VirtualBox, run `vagrant up` while the
VirtualBox GUI is open.

[flyingfrog81]

The bug appears with all versions of the base box, namely 1.0.0 and 1.0.1

[flyingfrog81]

The VirtualBox console reports this error:

Failed to open a session for the virtual machine azdora.
AMD-V is disabled in the BIOS (or by the host OS). (VERR_SVM_DISABLED).