On Wed, Feb 10, 2021 at 10:00:47AM +0100, Emmanuel Kasper wrote:
config.vm.provider "virtualbox" do |v| v.customize ["modifyvm", :id, "--graphicscontroller", "vmsvga"] endThat could probably considered a vagrant issue. I found that it is a non-issue with 4.x up to 5.9, but 5.10+ is not compatible with the default choice. Not sure if the suggested graphics controller is vmsvga only in 6.1 or dependingon the host graphic card...It should be possible to change the OVF of the Vagrant Box or add this to the default Vagrantfile.Just to better understand your use case, why are you building the virtualbox guest additions ? This should not be needed anymore since kernel 5.6, see https://kernelnewbies.org/Linux_5.6#Support_for_VirtualBox_guest_shared_foldersor am I missing something ?
Well, it is automagically done by vagrant at provisioning time for the debian/testing64, maybe because the local Virtualbox installation has the extension installed?
This is now the (working) stanza used: config.vm.define "testing" do |vm5| vm5.vm.box = "debian/testing64" vm5.vm.network "private_network", ip: "192.168.33.20" vm5.vm.provider "virtualbox" do |vb5| vb5.memory = "4096" vb5.name = "testing" vb5.cpus = 2 vb5.customize ["modifyvm", :id, "--graphicscontroller", "vmsvga"] end end -- Francesco P. Lovergine