Yeah, Virtualbox/VMware can't be used at the same time as Hyper-V. Theoretically, the latest Virtualbox can use Hyper-V as a backend, but I couldn't get it to work in practice.
Personally, I've completely moved away from Virtualbox and over to Hyper-V. Docker Desktop uses Hyper-V out of the box, and I was able to get GNS3 working with Hyper-V, so I'm pretty content. For what it's worth, Windows users don't have to use "Docker Desktop" and could instead create a Linux VM in Virtualbox and run Docker there instead. Docker Desktop is just more Windows user friendly. (Of course, in the next few months, we might get WSL 2 on Windows 10, which will include a real Linux kernel in a thinner virtualization layer, which would allow people to run Docker on Windows without the full Hyper-V VM, but I digress. I'll be exploring that more once it's officially released.) David Cook Systems Librarian Prosentient Systems 72/330 Wattle St Ultimo, NSW 2007 Australia Office: 02 9212 0899 Direct: 02 8005 0595 -----Original Message----- From: Koha-devel <koha-devel-boun...@lists.koha-community.org> On Behalf Of Mark Tompsett Sent: Tuesday, 4 February 2020 3:03 AM To: Koha-devel <koha-devel@lists.koha-community.org> Subject: Re: [Koha-devel] Trouble in setting up kohadevbox on Win10 prof Greetings, My virtualbox didn’t play nice with Hyper-V. And various windows features keep turning it back on, GRRRR! Hit the Windows Key and type “windows features” Hit the Windows Key + W combo to bring up the Windows Settings panel of the Start Screen. Click on Turn Windows features on or off. When the Turn Windows features on or off dialog appears, look for Hyper-V and deselect it. Click OK. Restart your computer when prompted. dism.exe /Online /Disable-Feature:Microsoft-Hyper-V dism.exe /Online /Disable-Feature:Microsoft-Hyper-V /all Restart your computer. bcdedit /set hypervisorlaunchtype off Restart your computer After that, had some issues as my virtualbox, git bash, and vagrant were out of date. So updated those. Then I was lazy: vagrant up It bombed, because of linux-headers something. vagrant ssh sudo apt install linux-headers<tab and find the right one> exit vagrant halt vagrant up It then correctly provisioned. So, while Owen's shared script may be valid, I'm not sure it is necessary to get too detailed. Also, Jonathan Druart made a good point about the SYNC_REPO path being your local windows path, not the one on the VM. GPML, Mark Tompsett _______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
signature.asc
Description: PGP signature
_______________________________________________ Koha-devel mailing list Koha-devel@lists.koha-community.org https://lists.koha-community.org/cgi-bin/mailman/listinfo/koha-devel website : http://www.koha-community.org/ git : http://git.koha-community.org/ bugs : http://bugs.koha-community.org/
