Run Vagrant on Windows 10 with AMD Ryzen

Vagrant
1

Hi,
I’ve been trying to run vagrant on AMD Ryzen procesors with Windows 10 installed, and everytime It stucks on SSH auth method: private key. I use VirtualBox provider.

I noticed, that the problem occurs only when I’m trying to run Ubuntu 18 or newer. On ubuntu 16 everything works fine.

The SCM virtualization option is enabled and Hyper-V is disabled, but I suspect that something is wrong with virtualzation support on AMD processors.

I tried on a few computers with AMD - everytime there is the same problem.
On Intel processors the same machine works fine.

I would be greatful for any solutions.

Thanks.

1 Like
2

I have the same issue with my Ryzen machine - a Lenovo M75q G2 with MS Win10prof.

Is there any workaround for this?

3

Yes, I have the solution.

You should increase number of CPU threads in Virtualbox and add more RAM.

Beside that, you can try add some options to your vagrant file in virtualbox section - maybe some of them will help you:

config.vm.provider "virtualbox" do |vb|
    vb.customize ["modifyvm", :id, "--ioapic", "on"]
    vb.customize ["modifyvm", :id, "--uart1", "0x3F8", "4"]
    vb.customize ["modifyvm", :id, "--uartmode1", "file", File::NULL]
end

After chaniging configuration, you should restart vagrant machine and everything should works.

Give me some feedback if it helped.
Best regards,
Sebastian

4

This didn’t help for me

I am using VirtualBox 6.1.36 and the latest version of vagrant and homestead. My machine is a Lenovo ThinkBook 15 Gen 2 AMD using windows 10.

I have enabled AMD V in the Bios and I have turned off Hyper-V and windows hypervisor platform and virtual machine platform in the windows settings.

5

You can try go to control panel, network settings, find network cards created by virtualbox (probably two adapters) - turn it off and turn it on. If it won’t help you can try add or remove host only adapters directly in virtualbox, to check if it is virtualbox issue.