I have a Lenovo Thinkpad with Windows7 OS. I downloaded micro cloud foundary and vm ware player. When I tried to boot micro Cloud Foundry in my system (Intel i7- 2760QM which is 64 bit) through VM player, I got the error "This Kernel requires an x86-64 CPU. but only detected an i686 CPU."
I even enabled Intel Virtualization Technology through BIOS as suggested in other posts, but I am still getting the same error.
Apart from this, I also checked the processor compatibility with the VMware utility and it shows that it is compatible.
Any suggestions ?
Here are the hardware requirements for VM Player.
It's possible you need to enable Intel virtualization in your BIOS.
I think you have to install a 64bit windows.
Related
Windows:
Now, I want to install a VMWare Workstation on the Windows Google Cloud Platform instance and next install another OS on that VMWare Workstation.
But I get this BSOD.
Linux:
Now, I want to install a VMWare Workstation on the Linux Google Cloud Platform instance and next install another OS on that VMWare Workstation.
But I get this error.
This host supports intel VT-x. but the Intel VT-x implementation is incompatible.
This host does not support Intel EPT hardware assisted MMU virtualization.
Module "CPUIDEarly" power on failed.
Failed to start the virtual machine.
How can I do it?
I agree with Martin that you may not want to run VMware workstation, but you may need nested virtualization for other stuff like VMware ESXi/qemu.
GCE VMs do support nested virtualization please see Enabling Nested Virtualization for VM Instances on how to do it. This will enable VT-x support inside the VM.
It is rather useless to install a type 2 (hosted) hypervisor inside a GCE virtual machine.
There are a) other options for VMware hosting or b) migrate these containers with Velostrata.
c) That one error message (assuming you'd go the proposed nested virtualization route) might require monitor.allowLegacyCPU = "true" in file config.ini, because it seems the CPU is not supported by VMware Workstation 14 (this at least works for some elder Intel® Xeon® CPU).
I have a project that requires me to create an esxi server within VirtualBox. Upon creation of the esxi server, i seem to run into the error below when i try to power on a newly created VM within the esxi.
Any idea how to get around this? The VirtualBox infrastructure is running on 2014 macbook pro which supports virtualization.
Have you enabled VT-x option
That's under System > Acceleration > Hardware virtualization
I have a window7 (32 bit) machine. I installed Virtual Box and created a VM (Windows 2012 {64bit} with enabled VT-x/AMD-V,Nested Paging).
I want to enable Hyper-V on this VM any Idea?
I tried following links but not working for me:
Link1
Link2
but in my case I am using Virtual Box.
How can I enable Hyper-V feature?
Do you want to expose VT-x/AMD-V to the guest system in the VM so it can run Hyper-V inside VM? As far as I know, VirtualBox does not support it, but VMWare does, even in their free VMWare Player.
I have been running Windows Phone 8 emulator in VMWare Player without problems. Yes, it required manual editing of .vmx file, but is works reliably and without any problems at all.
If you decide to give VMWare Player a try, make sure you have VT-x/AMD-V available and enabled on your physical host computer. Then add the following setting to your VMWare machine:
hypervisor.cpuid.v0 = "FALSE"
mce.enable = "TRUE"
and you should be able to start Hyper-V inside your VM.
For more information, see these links:
Unable to use Hyper-V platform inside a Windows 8 virtual machine
How to Enable Windows Server 2012 Hyper-V Role in VMware
and some useful topics on VirtualBox forums which explain why the feature is not available on VirtualBox:
https://forums.virtualbox.org/viewtopic.php?f=1&t=20589
https://forums.virtualbox.org/viewtopic.php?f=2&t=52625&p=304452
I really miss this feature on VirtualBox because I find VMWare Player to be bloated and it slows the host system down much more than VirtualBox does.
There didn't seem to be a dedicated Virtualization SE, so...
I am looking to install VMware vSphere Hypervisor 5.1 (or an older version if it helps) on a 64bit AMD A8 architecture.
Is there a path to doing this without destroying/having to reinstall Windows 8 already preinstalled by the Vendor (Acer), making it one of the VMs instead?
Or in general? (Eg. on another PC running 32bit Ubuntu, where I would like to "insert" a Hypervisor as well).
Use VMware Converter. It converts a physical machine into a VM during runtime. It is freely downloadable after registering on the VMware site:
http://www.vmware.com/products/converter/
Yes, you can install VMware Workstation and then install vShpere Hypervisor 5.1 as a guest OS. I have done that before. VMware Workstation supports the so called nested virtualization which means you it can expose the hardware virtualization feature of CPU which is required by vSphere to the guest OS. If you don't want to pay for VMware Workstation, you can use VMware Player which is free but capable of nested virtualization.
Environment:
Motherboard: Asus P5Q3 Deluxe
Processor: Intel(R) Core(TM)2 Quad CPU Q8200 # 2.33GHz 2.34 GHz
Installed Memory (RAM): 4.00GB
OS: Windows 7 Home Premium
Scenario:
I am trying to run OpenShift Origin in VirtualBox and when clicking 'Start' I am getting the error:
"VT-x/AMD-V hardware acceleration is not available on your system. Your 64-bit guest will fail to detect a 64-bit CPU and will not be able to boot".
From my searches on the internet, it seems that such a setting is available in the BIOS however I have been unable to find it.
So I am considering that such an option may not be available on my system?
If this is the case, what options do I have in regards to running OpenShift Origin in VirtualBox?
The specification on the Intel website suggests that your CPU doesn't support hardware virtualization (look for the 'Virtualization Technology (VT-x)' setting):
http://ark.intel.com/products/36547/intel-core2-quad-processor-q8200-4m-cache-2_33-ghz-1333-mhz-fsb
Hardware virtualization is a requirement for 64-bit guests in VirtualBox, and there is no workaround.