And vagrant is not aware of that VM.Ĭonfig.vm.network "private_network", ip: "192.168.33.10"Ĭonfig.vm.network "private_network", ip: "192.168.33. The VM is created and VirtualBox identifies it, but fails to initialize after boot and exits with an error. Running `vagrant up` should create and start a VM. VBoxManage: error: Details: code NS_ERROR_FAILURE (0x80004005), component ConsoleWrap, interface IConsole VBoxManage: error: To fix this problem, switch to 'Host-only Network' attachment type in the VM settings. VBoxManage: error: For your convenience a host-only network named 'Legacy vboxnet11 Network' has been created with network mask '255.255.255.0' and IP address range '192.168.33.1' - '192.168.33.254'. If you wish to use KVM as the provider, refer the below article on how to use vagrant with KVM. You can also use KVM instead of VirtualBox. Stderr: VBoxManage: error: Host-only adapters are no longer supported! For the purpose of this guide, we will be using Vagrant with VirtualBox as the provider to build our ansible lab. The end of the log contains the following message:Ĭommand:
0 Comments
Leave a Reply. |