![]() When you're done, you have Vagrant destroy the VM(s) again. You script the VM(s) you need using the Vagrantfile, then Vagrant and the VM provider create the desired VM and give you access (via SSH, port forwardings, custom network config, and shared filesystems). Vagrant users expect that the virtualization application becomes invisible you don't want to need to touch it at all. ![]() Not a Vagrant expert, just a long time user, and a recent Apple Silicon user, so I would welcome UTM support! Is exposing VM configuration to the Vagrantfile necessary? This isn't really compatible with UTM because it stores a ist in the VM bundle. ![]() Looking at some example Vagrantfiles using the Virtualbox provider, it seems like configuration of the VM is done in the Vagrantfile (for example CPU cores, memory, networking).
0 Comments
Leave a Reply. |