Hi All, I am also getting same error for windows 7. Can you please suggest what to do to resolve this ?
Regards Sagar On Wednesday, 5 November 2014 04:19:44 UTC+5:30, GM wrote: > > Cool, thanks for your help with this. > > On Tuesday, November 4, 2014 5:32:54 PM UTC-5, Umair Chagani wrote: >> >> So a couple things: >> >> 1. Hyper-V cannot be run on Windows 7. Simple as that. You must have >> Windows 8 or a Server 2008+ >> 2. Your passive aggressive tone is uncalled for. >> 3. If you actually read the documentation about the Hyper-V provider >> located at (https://docs.vagrantup.com/v2/hyperv/index.html) you would >> see that your "problem" is clearly addressed. >> 4. Vagrant is open source. If you don't like the documentation or >> consider it "light and vapid", feel free to submit a pull request with >> updates. >> >> >> On Tue, Nov 4, 2014 at 4:52 PM, GM <gkm...@hotmail.com> wrote: >> >>> I'm trying to go through the Getting Started documentation at >>> https://docs.vagrantup.com/v2/getting-started/index.html and I'm >>> getting the following error message: >>> >>> C:\Users\gm>vagrant up >>> Bringing machine 'default' up with 'hyperv' provider... >>> ==> default: Verifying Hyper-V is enabled... >>> The Hyper-V cmdlets for PowerShell are not available! Vagrant >>> requires these to control Hyper-V. Please enable them in the >>> "Windows Features" control panel and try again. >>> >>> I'm someone who tries very hard to solve problems before asking for >>> help. I've spent hours on this error trying to understand it or at least >>> get past it, and now I've simply had it with Vagrant. I'm running the 3.0 >>> version of PowerShell as recommended on a Windows 7 Professional machine. >>> I've searched google up and down, installed and uninstalled different >>> versions of the Windows Management Framework, and tried a bunch of >>> powershell commands but I'm no closer to understanding what the problem is. >>> Some of the information I've come across is implying that Hyper-V is only >>> available in the "Windows Features" control panel on a Windows 8 machine >>> (then why does Vagrant give those instructions when it can very easily tell >>> what version of Windows I'm running). >>> >>> Does anyone have any experience with handling this error? My impression >>> is that the documentation at http://docs.vagrantup.com/ is somewhat >>> light and vapid, the kind of documentation that is only useful if >>> everything works perfectly. >>> >>> Thanks, >>> GM >>> >>> >>> >>> -- >>> You received this message because you are subscribed to the Google >>> Groups "Vagrant" group. >>> To unsubscribe from this group and stop receiving emails from it, send >>> an email to vagrant-up+...@googlegroups.com. >>> For more options, visit https://groups.google.com/d/optout. >>> >> >> -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/vagrant/issues IRC: #vagrant on Freenode --- You received this message because you are subscribed to the Google Groups "Vagrant" group. To unsubscribe from this group and stop receiving emails from it, send an email to vagrant-up+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/vagrant-up/38a5a4fa-29d1-4e87-a459-050dd1b30a62%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
