![]() NFS errors To avoid NFS errors, while installing, ensure the firewall will accept connections: Apple > System Preferences > Security & Privacy > Firewall > Firewall Options.or, use the Hyper-V provider for Vagrant instead of VirtualBox.This will get VirtualBox working, but will prevent you from using any Hyper-V VMs you may have, such as Windows Phone emulators. Disable Hyper-V through 'Add/Remove Windows Features' in Control Panel and reboot.To turn Hyper-V back on set it back to auto instead of off In command prompt, run bcdedit /set hypervisorlaunchtype off to turn off Hyper-V and reboot.If you have Hyper-V enabled – which may be the default if you have installed Visual Studio – you'll get the above errors trying to boot up a VM in VirtualBox. VirtualBox is incompatible with Microsoft's Hyper-V.(Some laptops require you to remove the power cable and battery for 30 seconds ) It is not an optional performance enhancement. If that does not help, make sure you enable Hardware Virtualization Technology (VT-x or AMD-V) in BIOS. If you are on Windows and you get "guest machine entered an invalid state" - "poweroff", try downloading a 4.3.15 build of VirtualBox ( there is a known problem with 4.3.14 on Windows).MediaWiki-Vagrant needs to run on a 64-bit virtual machine, in part because it uses use deb packages from WMF production that are only built for the amd64 architecture. MediaWiki-Vagrant will not run on a host that doesn't support VT-X because it specifies a 64bit guest (virtual machine). Make sure that vagrant/mediawiki repository is up to date:.attaching old VM harddrive to the new profile) This thread discusses some ways to work around it (e.g. Vagrant rarely loses pairing with your VM.If you get warnings that your VirtualBox Guest Additions are the wrong version, you can try installing the vagrant-vbguest plugin which updates them automatically.The initial setup may take a long time if it seems to hang somewhere but there are no errors, just give it a while. You might want to compare the output of the initial run of vagrant up in your terminal with this sample. Use to check that Apache/PHP is up and running.Error: Puppet :: Parser :: AST :: Resource failed with error ArgumentError: Could not find declared class.If you got any puppet errors you might need to init puppet submodules, on vagrant directory run git submodule update -init.If you run into error message like "Couldn't open file $CLONED_REPOSITORY/trusty-cloud", try the following command: vagrant up -provider=virtualbox.If you get errors from vagrant up, instead install the most recent versions of VirtualBox and Vagrant.If you're running recent Debian or Ubuntu, try sudo apt-get install virtualbox vagrant to install the packages for VirtualBox and Vagrant. You can try installing the versions of VirtualBox and Vagrant that your Linux distribution provides. ![]() one saying "No wiki found." by running vagrant destroy vagrant up which will rebuild the virtual machine without repeating the most time-consuming parts of the installation process.
0 Comments
Leave a Reply. |