-
Notifications
You must be signed in to change notification settings - Fork 494
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix complaints about VT-x/AMD-V on CPUs lacking this feature #149
base: master
Are you sure you want to change the base?
Conversation
I'm also having that problem; I will try your patch, @glenux. |
It works well with WinXP, but there is still an issue at Windows 8 final boot (after setup). I'm not sure, but it seems that Microsoft has enabled Hyper-V and make the system still requires VT-x/AMD-V features after installation. i don't know how to test & disable it (if someone can help..). |
For me, WinXP wasn't booting but Win7 was (haven't tried Win8 as I have an actual installation of that on another partition). I found this suggestion worked, though I had to then tweak a setting like RAM allocation before it would recognize the change. The main problem is, although they boot now, all the XP VMs are the same, running IE6. I think there's something magic that happens when the ievms script runs that installs the different versions for you... can I trigger that to go again, now the VMs work? I did try running the bash script again, but it didn't do anything new. Update: heckit, I'm just going to download and run the installers manually in the VMs for IE7 and IE8. Will let you know how that goes. Update 2: works fine :) Now if it could just fix my IE8 bug in my website for me, that would be lovely. |
I've not looked at the IE8 issue but the reason you need to set CPUs to 1 is that VirtualBox requires VT-x/AMD-V for a guest to have more than 1 cpu. It would be better to not turn off the feature at all just set the cpus to 1. |
This patch fixes the issue for me :+1 . Setting CPU count to 1 was necessary, but doesn't hurt for my case (Windows XP anyways). |
|
This fix worked for me on an old laptop running Ubuntu. For OS X it seems that you can use sysctl such as described here: http://fortysomethinggeek.blogspot.com/2012/11/getting-cpu-info-from-command-line-in.html I don't have a Mac at the moment so I can't do it myself for now. |
"will will" should be just "will"
- remove the striked-through stuff - remove the reference to mondern.IE - add linkebreak for easy copy-pasting to curl-line
The previous change was not enough.
* Move the installation section up above the file-size-sections * Update markdown syntax so have better formatting
Detect CPU features and disable VT-x/AMD-V and related options on VM if needed.
Note: on machines lacking VT instructions, a strange complaint remains "VT-x is not available (VERR_VMX_NO_VMX)" if CPU number is not set to 1, so i forced it. (even on a machines with 4 cpus...)