I have met with the following problem.
Hardware: DELL Laptop E6430(CPU: I7 3520M)
Host OS : Windows7 professional(64 bit)
Guest OS: Ubuntu 12.04(32 bit)
VMM: virtualbox 4.2.16
I need to do some development on KVM with a windows 7 environment. Things can be made sure are that VT-X are opened in BIOS and can be recognized by windows 7.(Passed securable test.)
I can't post screenshot for my low reputation, sorry for that :-(
VT-x| AMD-V option in virtualbox is also opened.
But when I typed cat /proc/cpuinfo | grep vmx, I found no related output.
I tried to close VT-D in BIOS and then reopened it as google told me, but in vain.
Note that after I closed VT-D in BIOS, virtualbox just told me that vt-x | AMD-V was not available anymore, which I suppose means virtualbox knows the existence of that CPU feature.
So I thought KVM can not be used by windows 7, am I right? If not, I hope that somebody can tell me why there is no VMX in my guest OS. Thanks in advance!
Thanks for answering, I finally installed Ubuntu 12.04 with windows7 on the same hard disk. As for my issue, virtualbox don't support full virtuallization, so I could not see any VMX feature in my Guest OS, but vmware do, which suits me well.
Related
After a recent kernel update for Centos 7.4, Paravirtualized DomUs under Xen stooped booting. They just crash on boot.
Apparently it seems a new restriction in RHEL 7 kernel. And there are some suggestions i found in different forums to switch to HVM or PVHM. Problem is that most of Paravirt DomUs are installed on plain disks (without partitions). But to convert them to HVM or PVHM they need Grub installed inside the VM which need partition table. So it is a full reinstallation :(
Centos guys say it is something RHEL need to fix. So is this a bug which can be fixed in near future ? or is that RHEL just dont want its kernel to run on Paravirt vms any more ?
Had the same issue, and as a hack workaround installed the CentOS Xen kernel before upgrading to 7.4. Had no issues booting with that kernel in place. If RedHat fixes their kernel it should be relatively simple to switch back to it.
I am trying to install Mirantis OpenStack on a Linux VM in Proxmox using the provided virtualbox scripts. The problem is I get the error: VT-x is not avalable(VERR_VMX_NO_VMX) when I try to run the launch script.
I have nested virtualization enabled on the server.
I tried with Ubuntu and Linux Mint so far.
I did not change any config.
Any idea why it does that and how to solve the problem?
EDIT:
The server knows VT-d. Does that mean it knows VT-x too or is it 2 separate things?
According to druss.co, there are approximately three common reasons for this issue:
VT-x or AMD-V isn't enabled in your BIOS
Hyper-V virtualization is enabled
Your CPU doesn’t support VT-x or AMD-V virtualization
Solution 1: enable VT-x / AMD-V in your BIOS
Restart your computer and enter the BIOS (Escape / F2 / Delete, depending on MoB). Search for your virtualization setting, and set it to enabled.
Solution 2: Disable Hyper-V virtualization in Windows
Open a command shell as administrator (run cmd.exe as administrator). Then execute the following code:
dism.exe /Online /Disable-Feature:Microsoft-Hyper-V
Alternatively, you go to the control panel, select Program section -> Turn Windows features on or off, then disable Hyper-V and reboot.
Solution 3: Get a new CPU with VT-X / AMD-V support.
Hope it helps!
I have been trying maybe weeks now to figure out how to configure VirtualBox to have 1366x768 resolution on a linux guest, which is on a windows 8.1 host.
My configuration:
Windows 8.1 as host
Linuxmint 17.1 as guest (tried ubuntu and debian too but no luck)
Virtualbox 4.3.26 and its extension pack
Laptop is powerful with 16GB ram and 4GB Nvdia
My problem is that it doesn't matter what I used, nothing worked.
Please do not post the answers on most known websites, I tried them already.
Once your VM is started, you need to run the VBox Linux Guest Additions.
First try to run it from the VirtualBox window's menu:
Devices >> Insert guest Additions CD image...
and follow the instructions.
If that fails, open a terminal and go to the directory where you CD reader is mounted (/run/media/ on Fedora or /media/ on Ubuntu for example).
Then type command sudo ./VBoxLinuxAdditions.run
Complete instructions can be found on the VirtualBox user manual
Once Guest Additions are installed, reboot your virtual machine. You should be able to resize your screen to your heart's content.
I installed the new VirtualBox 5.0.0_BETA2 and it solved my all problems. Great product is getting ready! Cant wait the latest release. more than a PERFECT software. Now you can remove top bar and/or bottom bar easily. Show what you need.
If you are having problem like me with 1366x768 I recommend you to install latest versin of VB even if it is Beta!
I have been trying to install that but it produces an error saying that the processor is not compatible with x64. I tried VMWare Player and Microsoft Virtual PC. I also read about disabling virualization but it's not working.
By enabling virtualization from the BIOS setup of the main machine it worked!
Problem installing x64 guest OS with vmware Server
You can try with this, it reveals some very useful informations http://support.microsoft.com/windowsserver2003x64
Host OS is x64 Win 2003.
Trying to load x64 iso (Ultrabac) and get the following:
"Attempting to load an x64 operating system, however this CPU is not compatible with x64 mode. Please install a 32-bit X86 operating system. Setup cannot continue. Press any key to exit."
So I ran Processor Check for 64-Bit Compatibility and it came up ok.
Anyone have any ideas?
You also need a BIOS that supports virtualisation extensions - checkso
a) that your BIOS has this setting
b) that it is set to ON