virtualbox.org

Running Virtual Box 4.3.28 in a windows 2012 vmware 64 bit R2 machine. I keep getting this message when I try and open my 64 bit Centos 7 vagrant vm.
This kernel requires an x86-64 CPU, but only detected an i686 CPU. This processor is unsupported in CentOS 7

How can I get this working? Read many posts tried almost all of them with no luck so far. Need this for a project I am joining. I have attached a log.

Vagrant is not supported here, so for further support you will need to reproduce the problem without using it.

What I can tell you from the log is:
- VM is configured for 32 bits linux - VT-x is not detected from the CPU - VirtualBox falls back to software mode - You won't be able to run 64 bits linux until you fix the VT-x issue. Have a look at I have a 64bit host, but can't install 64bit guests

Neither is nested virtualization supported.

Missed that bit, thank you for pointing it out Perry

Well I thought it important enough to jump in since VMX is not going to be passed to the guest = No 64_Bit guests.

You did well indeed.

Do you think it will ever be possible to have the support for Virtual Box to run in a nested virtual environment? The big issue for me is I was told that VMware workstation and Virtualbox will not play nicely on the same physical box. Wanted to try and avoid 2 compters. I do have an ESXi vSphere 5.0 server and if I could have gotten this working it would have been very sweet and fast.

I even went into the Virtual Host setting and enabled the VT-x on the vmware host. Maybe something else was getting this service. Would what I was trying to do work on hyperbox?

gmurphy wrote:Do you think it will ever be possible to have the support for Virtual Box to run in a nested virtual environment?

Not unless paying customers start asking for it in significant numbers, or someone contributes the code. Even then I suspect that the feature would wither on the vine, since multiple layers of virtualization will not a high performing computer make.

Well, I can tell you running this from a Hypervisor like ESXi is much faster than a local setup because I have a machine with 48 GB of ram. My laptop could never support that.

What happens when you nest that hypervisor?
ESXi + guest + ESXi +guest = ?

gmurphy wrote:Well, I can tell you running this from a Hypervisor like ESXi is much faster than a local setup because I have a machine with 48 GB of ram. My laptop could never support that.

I don't understand that comment at all. How is the laptop involved? You have ESXi running on it? How you do come by a laptop with more memory than supplied OS can use? If the laptop can use it, then how can you expect indirect access (from a VM) to be faster than direct access? Are you sure you aren't confusing short term OS performance issues with hardware performance?