Vagrant

Every feature, in the format's own order: whether every VM target can do it, whether Isoloom produces it, and how (or why not). See the overview for the rule.

Vagrant

75% of 35 portable features (25 done, 3 partly, 7 to do; 61 features in all). From Vagrant 2.4.9 (config.vm, network types, provisioners).

Machine settings (config.vm)

Key	Every target	Implemented	Notes
`allow_fstab_modification`	n/a	No	Shared folders are off: the project is copied into each VM
`allow_hosts_modification`	n/a	No	Isoloom writes /etc/hosts itself (names of the other machines)
`allowed_synced_folder_types`	n/a	No	Shared folders are off: the project is copied into each VM
`base_address`	No	No	Cloud VMs get their MAC and addresses from the provider
`base_mac`	No	No	Cloud VMs get their MAC and addresses from the provider
`boot_timeout`	Yes	Yes	Fixed: 10 minutes
`box`	Yes	Partly	From `machines..vm.os, or machines..vm.image.vagrant`; not yet: built-in Windows Server 2022 and Windows 11 boxes
`box_architecture`	Yes	Not yet	A CPU architecture field (amd64, arm64)
`box_check_update`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_ca_cert`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_ca_path`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_checksum`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_checksum_type`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_client_cert`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_disable_ssl_revoke_best_effort`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_insecure`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_location_trusted`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_download_options`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_extra_download_options`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`box_server_url`	Yes	Not yet	Custom images (a box URL, a Proxmox template, a cloud image)
`box_url`	Yes	Not yet	Custom images (a box URL, a Proxmox template, a cloud image)
`box_version`	Yes	Yes	From `machines.*.vm.image.vagrant_version, or a built-in pin`
`clone`	n/a	No	Starts from another Vagrant machine; machines start from their image
`cloud_init`	Yes	Another way	Via provisioning steps run any setup
`cloud_init_configs`	Yes	Another way	Via provisioning steps run any setup
`cloud_init_first_boot_only`	Yes	Another way	Via provisioning steps run any setup
`communicator`	Yes	Partly	From `vm.os` (Windows: WinRM); not yet: Windows Server 2022 and Windows 11 boxes
`define`	Yes	Yes	From `machines`
`disk`	Yes	Not yet	Machines.*.resources.disk_gb
`disks`	Yes	Not yet	Machines.*.resources.disk_gb
`graceful_halt_timeout`	n/a	No	Vagrant tooling, not the environment's behavior
`guest`	Yes	Partly	From `vm.os` (Windows: WinRM); not yet: Windows Server 2022 and Windows 11 boxes
`host_name`	n/a	No	Old name of `hostname`
`hostname`	Yes	Yes	From the machine's name
`ignore_box_vagrantfile`	n/a	No	Vagrant tooling, not the environment's behavior
`network`	Yes	Yes	From `networks` (see the network types below)
`post_up_message`	n/a	No	Vagrant tooling, not the environment's behavior
`provider`	Yes	Yes	From `machines.*.resources` (see each provider below)
`provision`	Yes	Yes	From `machines.*.vm.provision` (see the provisioners below)
`provisioners`	n/a	No	Vagrant's own list behind `provision`
`synced_folder`	Yes	Yes	Disabled: the project is copied into each VM instead
`usable_port_range`	n/a	No	How Vagrant picks host ports for forwarded ports

Network types

Key	Every target	Implemented	Notes
`private_network`	Yes	Yes	From `networks and machines.*.networks`
`forwarded_port`	Yes	Yes	From `machines.*.services[].publish` (on the host's loopback)
`public_network`	Yes	Not yet	A network bridged to the outside (Compose `external`, a host bridge, a VPC)

Provisioners

Key	Every target	Implemented	Notes
`shell`	Yes	Yes	From `machines.*.vm.provision` (.sh), and Isoloom's own steps
`file`	Yes	Yes	The project, copied into each VM
`ansible_local`	Yes	Yes	From `machines.*.vm.provision` (.yml, .yaml)
`ansible`	Yes	Another way	Via ansible_local: the same playbooks, run inside the VM
`chef`	Yes	Another way	Via a `.sh` provisioning step can run any tool
`puppet`	Yes	Another way	Via a `.sh` provisioning step can run any tool
`salt`	Yes	Another way	Via a `.sh` provisioning step can run any tool
`cfengine`	Yes	Another way	Via a `.sh` provisioning step can run any tool
`docker`	Yes	Another way	Via `docker:` (containers come from the Compose output; VMs run services natively)
`podman`	Yes	Another way	Via `docker:` (containers come from the Compose output; VMs run services natively)
`container`	Yes	Another way	Via `docker:` (containers come from the Compose output; VMs run services natively)

Other settings

Key	Every target	Implemented	Notes
`config.ssh`	n/a	No	Vagrant tooling, not the environment's behavior
`config.winrm`	Yes	Yes	From `vm.os` (the Windows box's own account, over WinRM)
`config.winssh`	Yes	Not yet	With Windows guests (which make an environment VM-only)
`config.trigger`	n/a	No	Vagrant tooling, not the environment's behavior
`config.vagrant`	n/a	No	Vagrant tooling, not the environment's behavior

Vagrant: VirtualBox

100% of 5 portable features (5 done, 0 partly, 0 to do; 15 features in all). From Vagrant 2.4.9 (the provider's config class).

Settings

Key	Every target	Implemented	Notes
`auto_nat_dns_proxy`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`check_guest_additions`	n/a	No	Vagrant tooling, not the environment's behavior
`cpus`	Yes	Yes	From `machines.*.resources`
`customizations`	No	No	Raw commands for one hypervisor: no other target understands them
`customize`	No	No	Raw commands for one hypervisor: no other target understands them
`default_nic_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`destroy_unused_network_interfaces`	n/a	No	Vagrant tooling, not the environment's behavior
`functional_vboxsf`	n/a	No	Shared folders are off: the project is copied into each VM
`gui`	No	No	Display, input and host devices: containers and cloud VMs have none
`linked_clone`	n/a	No	Faster starts from one image: no change in behavior
`linked_clone_snapshot`	n/a	No	Vagrant tooling, not the environment's behavior
`memory`	Yes	Yes	From `machines.*.resources`
`name`	Yes	Yes	The environment and machine names, as the VM's display name
`network_adapter`	Yes	Another way	Via `config.vm.network private_network`, the same on every provider
`network_adapters`	Yes	Another way	Via `config.vm.network private_network`, the same on every provider

Vagrant: VMware Desktop

90% of 5 portable features (4 done, 1 partly, 0 to do; 24 features in all). From vagrant-vmware-desktop 3.0.5 (its config class).

Settings

Key	Every target	Implemented	Notes
`allowlist_verified`	n/a	No	Vagrant tooling, not the environment's behavior
`base_address`	No	No	Cloud VMs get their MAC and addresses from the provider
`base_mac`	No	No	Cloud VMs get their MAC and addresses from the provider
`clone_directory`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`cpus`	Yes	Another way	Via machines.*.resources, written in `vmx`
`enable_vmrun_ip_lookup`	n/a	No	Vagrant tooling, not the environment's behavior
`force_vmware_license`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`functional_hgfs`	n/a	No	Shared folders are off: the project is copied into each VM
`gui`	No	No	Display, input and host devices: containers and cloud VMs have none
`linked_clone`	n/a	No	Faster starts from one image: no change in behavior
`memory`	Yes	Another way	Via machines.*.resources, written in `vmx`
`nat_device`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`network_adapter`	Yes	Another way	Via `config.vm.network private_network`, the same on every provider
`network_adapters`	Yes	Another way	Via `config.vm.network private_network`, the same on every provider
`port_forward_network_pause`	n/a	No	Vagrant tooling, not the environment's behavior
`shared_folder_special_char`	n/a	No	Shared folders are off: the project is copied into each VM
`ssh_info_public`	n/a	No	Vagrant tooling, not the environment's behavior
`unmount_default_hgfs`	n/a	No	Shared folders are off: the project is copied into each VM
`utility_certificate_path`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`utility_host`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`utility_port`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`verify_vmnet`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`vmx`	Yes	Partly	From `machines.*.resources`; not yet: only displayName, numvcpus and memsize
`whitelist_verified`	n/a	No	Vagrant tooling, not the environment's behavior

Vagrant: Parallels

100% of 5 portable features (5 done, 0 partly, 0 to do; 15 features in all). From vagrant-parallels 2.4.7 (its config class).

Settings

Key	Every target	Implemented	Notes
`check_guest_tools`	n/a	No	Vagrant tooling, not the environment's behavior
`cpus`	Yes	Yes	From `machines.*.resources`
`customizations`	No	No	Raw commands for one hypervisor: no other target understands them
`customize`	No	No	Raw commands for one hypervisor: no other target understands them
`destroy_unused_network_interfaces`	n/a	No	Vagrant tooling, not the environment's behavior
`functional_psf`	n/a	No	Shared folders are off: the project is copied into each VM
`linked_clone`	n/a	No	Faster starts from one image: no change in behavior
`linked_clone_snapshot`	n/a	No	Vagrant tooling, not the environment's behavior
`memory`	Yes	Yes	From `machines.*.resources`
`name`	Yes	Yes	The environment and machine names, as the VM's display name
`network_adapter`	Yes	Another way	Via `config.vm.network private_network`, the same on every provider
`network_adapters`	Yes	Another way	Via `config.vm.network private_network`, the same on every provider
`optimize_power_consumption`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`regen_src_uuid`	n/a	No	Vagrant tooling, not the environment's behavior
`update_guest_tools`	n/a	No	Vagrant tooling, not the environment's behavior

Vagrant: libvirt

10% of 19 portable features (2 done, 0 partly, 17 to do; 146 features in all). From vagrant-libvirt 0.12.2 (its config class).

Settings

Key	Every target	Implemented	Notes
`autostart`	n/a	No	Vagrant tooling, not the environment's behavior
`boot`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`boot_order`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`cdroms`	No	No	Display, input and host devices: containers and cloud VMs have none
`channel`	No	No	Display, input and host devices: containers and cloud VMs have none
`channels`	No	No	Display, input and host devices: containers and cloud VMs have none
`clock_absolute`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`clock_adjustment`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`clock_basis`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`clock_offset`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`clock_timer`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`clock_timers`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`clock_timezone`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cmd_line`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`connect_via_ssh`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`cpu_affinity`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpu_fallback`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpu_feature`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpu_features`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpu_mode`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpu_model`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpu_topology`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpuaffinitiy`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cpus`	Yes	Yes	From `machines.*.resources`
`cpuset`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`cputopology`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`default_prefix`	n/a	No	Vagrant tooling, not the environment's behavior
`description`	n/a	No	Vagrant tooling, not the environment's behavior
`disk_address_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`disk_bus`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`disk_controller_model`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`disk_device`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`disk_driver`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`disk_driver_opts`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`disks`	Yes	Not yet	Machines.*.resources.disk_gb
`driver`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`dtb`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`emulator_path`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`features`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`features_hyperv`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`floppies`	No	No	Display, input and host devices: containers and cloud VMs have none
`forward_ssh_port`	n/a	No	Vagrant tooling, not the environment's behavior
`graphics_autoport`	No	No	Display, input and host devices: containers and cloud VMs have none
`graphics_gl`	No	No	Display, input and host devices: containers and cloud VMs have none
`graphics_ip`	No	No	Display, input and host devices: containers and cloud VMs have none
`graphics_passwd`	No	No	Display, input and host devices: containers and cloud VMs have none
`graphics_port`	No	No	Display, input and host devices: containers and cloud VMs have none
`graphics_type`	No	No	Display, input and host devices: containers and cloud VMs have none
`graphics_websocket`	No	No	Display, input and host devices: containers and cloud VMs have none
`host`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`host_device_exclude_prefixes`	n/a	No	Vagrant tooling, not the environment's behavior
`hyperv_feature`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`id_ssh_key_file`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`initrd`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`input`	No	No	Display, input and host devices: containers and cloud VMs have none
`inputs`	No	No	Display, input and host devices: containers and cloud VMs have none
`kernel`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`keymap`	No	No	Display, input and host devices: containers and cloud VMs have none
`kvm_hidden`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`launchsecurity`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`launchsecurity_data`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`loader`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`machine_arch`	Yes	Not yet	A CPU architecture field (amd64, arm64)
`machine_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`machine_virtual_size`	Yes	Not yet	Machines.*.resources.disk_gb
`management_network_address`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_autostart`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_device`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_domain`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_driver_iommu`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_guest_ipv6`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_iface_name`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_keep`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_mac`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_mode`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_model_type`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_mtu`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_name`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_pci_bus`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`management_network_pci_slot`	n/a	No	Vagrant's management network, used to provision (like the NAT interface elsewhere)
`memballoon_enabled`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memballoon_model`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memballoon_pci_bus`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memballoon_pci_slot`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memory`	Yes	Yes	From `machines.*.resources`
`memory_backing`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memorybacking`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memtune`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memtunes`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`mgmt_attach`	n/a	No	Vagrant tooling, not the environment's behavior
`nested`	Yes	Not yet	Nested virtualization: running VMs inside (makes an environment VM-only)
`nic_adapter_count`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`nic_model_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`nodeset`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`numa_nodes`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`nvram`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`password`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`pci`	No	No	Display, input and host devices: containers and cloud VMs have none
`pcis`	No	No	Display, input and host devices: containers and cloud VMs have none
`port`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`proxy_command`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`qemu_args`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`qemu_env`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`qemu_use_agent`	n/a	No	Vagrant tooling, not the environment's behavior
`qemu_use_session`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`qemuargs`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`qemuenv`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`random`	No	No	Display, input and host devices: containers and cloud VMs have none
`random_hostname`	n/a	No	Vagrant tooling, not the environment's behavior
`redirdev`	No	No	Display, input and host devices: containers and cloud VMs have none
`redirdevs`	No	No	Display, input and host devices: containers and cloud VMs have none
`redirfilter`	No	No	Display, input and host devices: containers and cloud VMs have none
`redirfilters`	No	No	Display, input and host devices: containers and cloud VMs have none
`rng`	No	No	Display, input and host devices: containers and cloud VMs have none
`serial`	No	No	Display, input and host devices: containers and cloud VMs have none
`serials`	No	No	Display, input and host devices: containers and cloud VMs have none
`shares`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`smartcard`	No	No	Display, input and host devices: containers and cloud VMs have none
`smartcard_dev`	No	No	Display, input and host devices: containers and cloud VMs have none
`snapshot_pool_name`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`socket`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`sound_type`	No	No	Display, input and host devices: containers and cloud VMs have none
`storage`	Yes	Not yet	Machines.*.resources.disk_gb
`storage_pool_name`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`storage_pool_path`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`suspend_mode`	n/a	No	Vagrant tooling, not the environment's behavior
`sysinfo`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`system_uri`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`title`	n/a	No	Vagrant tooling, not the environment's behavior
`tpm_model`	Yes	Not yet	With Windows guests (which make an environment VM-only)
`tpm_path`	Yes	Not yet	With Windows guests (which make an environment VM-only)
`tpm_type`	Yes	Not yet	With Windows guests (which make an environment VM-only)
`tpm_version`	Yes	Not yet	With Windows guests (which make an environment VM-only)
`uri`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`usb`	No	No	Display, input and host devices: containers and cloud VMs have none
`usb_controller`	No	No	Display, input and host devices: containers and cloud VMs have none
`usbctl_dev`	No	No	Display, input and host devices: containers and cloud VMs have none
`usbs`	No	No	Display, input and host devices: containers and cloud VMs have none
`username`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`uuid`	n/a	No	Vagrant tooling, not the environment's behavior
`video_accel3d`	No	No	Display, input and host devices: containers and cloud VMs have none
`video_type`	No	No	Display, input and host devices: containers and cloud VMs have none
`video_vram`	No	No	Display, input and host devices: containers and cloud VMs have none
`volume_cache`	n/a	No	Vagrant tooling, not the environment's behavior
`watchdog`	No	No	Display, input and host devices: containers and cloud VMs have none
`watchdog_dev`	No	No	Display, input and host devices: containers and cloud VMs have none

Vagrant: Hyper-V

25% of 4 portable features (1 done, 0 partly, 3 to do; 16 features in all). From Vagrant 2.4.9 (the provider's config class).

Settings

Key	Every target	Implemented	Notes
`auto_start_action`	n/a	No	Vagrant tooling, not the environment's behavior
`auto_stop_action`	n/a	No	Vagrant tooling, not the environment's behavior
`cpus`	Yes	Not yet	With Hyper-V hosts
`differencing_disk`	n/a	No	Faster starts from one image: no change in behavior
`enable_automatic_checkpoints`	n/a	No	Vagrant tooling, not the environment's behavior
`enable_checkpoints`	n/a	No	Vagrant tooling, not the environment's behavior
`enable_enhanced_session_mode`	No	No	Display, input and host devices: containers and cloud VMs have none
`enable_virtualization_extensions`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`ip_address_timeout`	n/a	No	Vagrant tooling, not the environment's behavior
`linked_clone`	n/a	No	Faster starts from one image: no change in behavior
`mac`	No	No	Cloud VMs get their MAC address from the provider
`maxmemory`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`memory`	Yes	Not yet	With Hyper-V hosts
`vlan_id`	Yes	Another way	Via `config.vm.network private_network`, the same on every provider
`vm_integration_services`	n/a	No	Vagrant tooling, not the environment's behavior
`vmname`	Yes	Not yet	With Hyper-V hosts

Vagrant: UTM

75% of 4 portable features (3 done, 0 partly, 1 to do; 12 features in all). From vagrant_utm 0.1.6 (its config class), for Apple Silicon Macs.

Settings

Key	Every target	Implemented	Notes
`check_guest_additions`	n/a	No	Vagrant tooling, not the environment's behavior
`cpus`	Yes	Yes	From `machines.*.resources`
`customizations`	No	No	Raw commands for one hypervisor: no other target understands them
`customize`	No	No	Raw commands for one hypervisor: no other target understands them
`directory_share_mode`	n/a	No	Shared folders are off: the project is copied into each VM
`functional_9pfs`	n/a	No	Shared folders are off: the project is copied into each VM
`icon`	n/a	No	How UTM shows the VM
`memory`	Yes	Yes	From `machines.*.resources`
`name`	Yes	Yes	The environment and machine names, as the VM's display name
`notes`	n/a	No	How UTM shows the VM
`wait_time`	n/a	No	Vagrant tooling, not the environment's behavior
`private_network`	Yes	Not yet	Not verified: vagrant_utm doesn't document `config.vm.network private_network`

Vagrant: QEMU

14% of 14 portable features (2 done, 0 partly, 12 to do; 34 features in all). From vagrant-qemu 0.6.3 (its config class), for Apple Silicon Macs.

Settings

Key	Every target	Implemented	Notes
`advanced_network`	Yes	Not yet	Private networks: QEMU gives a machine one private network (`advanced_network`), and needs vmnet or socket_vmnet on the Mac
`arch`	Yes	Not yet	A CPU architecture field (amd64, arm64)
`control_port`	n/a	No	Vagrant tooling, not the environment's behavior
`cpu`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`debug_port`	n/a	No	Vagrant tooling, not the environment's behavior
`default_qemu_dir`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`disk_resize`	Yes	Not yet	Machines.*.resources.disk_gb
`drive_interface`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`extra_drive_args`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`extra_image_opts`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`extra_netdev_args`	Yes	Not yet	With private networks on QEMU
`extra_qemu_args`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`firmware_format`	Yes	Not yet	Custom images with their own kernel and boot (makes an environment VM-only)
`graceful_timeout`	n/a	No	Vagrant tooling, not the environment's behavior
`homebrew_prefix`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`image_path`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`machine`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`mcast_addr`	Yes	Not yet	With private networks on QEMU
`memory`	Yes	Yes	From `machines.*.resources`
`net_device`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`net_mode`	Yes	Not yet	Private networks: QEMU gives a machine one private network (`advanced_network`), and needs vmnet or socket_vmnet on the Mac
`no_daemonize`	n/a	No	Vagrant tooling, not the environment's behavior
`other_default`	n/a	No	Vagrant tooling, not the environment's behavior
`qemu_bin`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`qemu_dir`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`smp`	Yes	Yes	From `machines.*.resources.cpus`
`socket_opts`	Yes	Not yet	With private networks on QEMU
`socket_vmnet_client`	Yes	Not yet	With private networks on QEMU
`socket_vmnet_socket`	Yes	Not yet	With private networks on QEMU
`ssh_auto_correct`	n/a	No	Vagrant tooling, not the environment's behavior
`ssh_host`	n/a	No	Vagrant tooling, not the environment's behavior
`ssh_port`	n/a	No	Vagrant tooling, not the environment's behavior
`tap_device`	Yes	Not yet	With private networks on QEMU
`vmnet_interface`	Yes	Not yet	With private networks on QEMU

Vagrant: ESXi

0% of 14 portable features (0 done, 0 partly, 14 to do; 53 features in all). From vagrant-vmware-esxi 2.5.2 (its config class), for standalone ESXi hosts.

Settings

Key	Every target	Implemented	Notes
`allow_overwrite`	n/a	No	Vagrant tooling, not the environment's behavior
`clone_from_vm`	n/a	No	Faster starts from one image: no change in behavior
`custom_vmx_settings`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`debug`	n/a	No	Vagrant tooling, not the environment's behavior
`encoded_esxi_password`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_disk_store`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_hostname`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_hostport`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_password`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_private_keys`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_resource_pool`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_username`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`esxi_virtual_network`	Yes	Not yet	Private networks: one ESXi port group per network
`guest_autostart`	n/a	No	Vagrant tooling, not the environment's behavior
`guest_boot_disk_size`	Yes	Not yet	Machines.*.resources.disk_gb
`guest_custom_vmx_settings`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`guest_disk_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`guest_guestos`	Yes	Not yet	With Windows guests (which make an environment VM-only)
`guest_mac_address`	No	No	Cloud VMs get their MAC address from the provider
`guest_memsize`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)
`guest_name`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)
`guest_name_prefix`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)
`guest_nic_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`guest_numvcpus`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)
`guest_snapshot_includememory`	n/a	No	Vagrant tooling, not the environment's behavior
`guest_snapshot_quiesced`	n/a	No	Vagrant tooling, not the environment's behavior
`guest_storage`	Yes	Not yet	Machines.*.resources.disk_gb
`guest_username`	n/a	No	Vagrant tooling, not the environment's behavior
`guest_virtualhw_version`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`guestos`	Yes	Not yet	With Windows guests (which make an environment VM-only)
`lax`	n/a	No	Vagrant tooling, not the environment's behavior
`local_allow_overwrite`	n/a	No	Vagrant tooling, not the environment's behavior
`local_failonwarning`	n/a	No	Vagrant tooling, not the environment's behavior
`local_lax`	n/a	No	Vagrant tooling, not the environment's behavior
`local_private_keys`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`local_use_ip_cache`	n/a	No	Vagrant tooling, not the environment's behavior
`mac_address`	No	No	Cloud VMs get their MAC address from the provider
`memsize`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)
`nic_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`numvcpus`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)
`resource_pool`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`saved_ipaddress`	n/a	No	Vagrant tooling, not the environment's behavior
`ssh_username`	n/a	No	Vagrant tooling, not the environment's behavior
`supported_guest_disk_types`	n/a	No	The plugin's own list of accepted values
`supported_guest_guestos`	n/a	No	The plugin's own list of accepted values
`supported_guest_nic_types`	n/a	No	The plugin's own list of accepted values
`supported_guest_virtualhw_versions`	n/a	No	The plugin's own list of accepted values
`virtual_network`	Yes	Not yet	Private networks: one ESXi port group per network
`virtualhw_version`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`vm_disk_store`	n/a	No	The user's own setup (how Vagrant reaches the hypervisor, where it stores things)
`vm_disk_type`	No	No	Hypervisor tuning: containers and cloud VMs have no such knob
`vmname`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)
`vmname_prefix`	Yes	Not yet	With the ESXi provider block (not verified on an ESXi host yet)