- work in progress
MediaWiki-Vagrant uses a 64-bit virtual machine, which requires hardware virtualization (VT-X) support to run.
On Windows, VirtualBox and Hyper-V cannot both make use of VT-X at the same time. Even if no Hyper-V virtual machines are running, if Hyper-V is installed and enabled VirtualBox will fail to run 64-bit VMs.
If you need Hyper-V to be enabled for Visual Studio mobile emulators, WSL 2, Docker for Windows or other needs, you can use Hyper-V as a VM provider for Vagrant.
Disabling Hyper-V to use VirtualBoxEdit
Remember this will not work with Docker for Windows or WSL 2, if you use those technologies. They are committed to Hyper-V.
- open 'Turn Windows features on and off' from start menu search
- Turn off 'Hyper-V'
- reboot when done
- go back to MediaWiki-Vagrant page and follow VirtualBox directions
Using Hyper-V providerEdit
Setting up networkingEdit
Networking must be manually configured in the Hyper-V Manager. Create a virtual switch and set it up with a NAT configuration. The Default Switch that comes with recent builds of Windows 10 is suitable and should work just fine.
Using the providerEdit
To use Hyper-V providers, you will have to run Vagrant from an Administrator console.
Hit 'Windows' key, type 'PowerShell', right-click on 'Windows PowerShell' and select 'Run as Administrator'. Click through UAC dialog if necessary. Because vagrant instruments Hyper-V, you must run at least most vagrant commands as administrator.
Now check out MediaWiki-Vagrant if necessary, go to the directory and:
vagrant settings smb_shares yes vagrant up --provider=hyperv
This should prompt you for your virtual switch name and have you up and running soon.