There are also some other things to mind. You need to pick a specific image from the Vagrant cloud which supports Hyper-V (my usual VirtualBox images were not available in Hyper-V format). When starting out I noticed, Vagrant needs to run as a user with administrative privileges due to the way Hyper-V works. I encountered many issues when trying out Vagrant with Hyper-V. You can download my Vagrantfile and provisioning script here. I think I should try VMWare next to see if it will provide a better experience. Not only that but several alternative solutions are required outside of Hyper-V because of lack of features. A lot of things which work out of the box with Vagrant and VirtualBox require effort to get working in Hyper-V. In this blog post I’ll describe my experiences. These annoyances drove me to try out Vagrant with Hyper-V (running an Ubuntu 21.04 guest on a Windows 11 host). For example CPUs getting stuck when assigning multiple CPUs to a VM and issues with auto adjusting the guest resolution when resizing the VM window. Recently however I’m experiencing more issues with Virtualbox.
I’ve used Vagrant since 2015 in combination with Virtualbox for creating development machines.
0 kommentar(er)
