vagrant_utm 0.0.1 → 0.1.1

checksums.yaml

@@ -1,7 +1,7 @@
 ---
 SHA256:
-  metadata.gz: a3fb5b4444402858a94f7d14c05bcc536749f405e5fa7c4ea8c84656a9f2dbee
-  data.tar.gz: 8e2c1b654f105d996504cc8c5f03276c421389fe414ff3c81c020bd0e4525179
+  metadata.gz: e58e1f0313976a35281a3233fe67d4150f84c8ec51ed41c2ca55256ba9cae05e
+  data.tar.gz: b5b234e460ef8517720492d3b5695cf771cd52efdd0a60c172ec3d644931b535
 SHA512:
-  metadata.gz: 30371d09843505b8a0bf16f1e2c454470e9459b454b0dcd94b52a525a64a95f1d0bb61fb3ec7434c4cf9e37e3889b15542ba7aaa2d2ac6cc6b26a95ab4c4f8fe
-  data.tar.gz: b6c93091338e29b4a41ad83c2e112e3c554384da447243ed3a4a45849e4779d7de9281cfd5b5a5b75958821db6c570ddb705c0c0162e98766100029bbc86ec9f
+  metadata.gz: fb95231d43a7f9731d7b36823ff7e991b5e11c9113a60590120b21fcd0d6b420116fe7d39e3465e579e5c1548071d562b50b94142c5f4bb689d13c24a671271b
+  data.tar.gz: b3a7b1655c81f270c6aa8399668fcfd5862201f9d00e9532ba00b7e9609e2d6dc7b5a986b502fd447b39dd303bb92ce1b9f513b7c09e2fa2ccf4a801de5878c4

data/CHANGELOG.md

@@ -1,5 +1,45 @@
-## [Unreleased]
+## [0.1.1] - 2024-12-03 
 
-## [0.1.0] - 2024-07-13
+IMPORTANT: This version of the plugin only works with UTM version 4.5.1 and above, and is incompatible with 0.0.1 version of the plugin.
 
-- Initial release
+### Added
+
+- command: add new vagrant command `vagrant ip-address` (9252020)
+- command: add help messages to custom plugin commands (a35466f)
+- action: Set mac address when bringing up new machine (0efe15b) 
+
+### Changed
+
+- plugin: Make config.vm.box mandatory for this plugin (b5be5e8)
+
+### Fixed
+
+- disposable: allow disposable start only for machines already created (cbf591e)
+- up: Set given mac address or random mac address for first interface of a machine to get different IPs of a same base box. 
+
+### Removed
+
+- Driver: Removed support for UTM version 4.5.x (9aea46e)
+
+## [0.1.0] (Beta) - 2024-11-30
+
+IMPORTANT: This version of the plugin only works with UTM version 4.5.1 and above, and is incompatible with previous versions of the plugin.
+
+### Added
+
+- driver: add new driver for UTM version 4.6.x (13d0ca0)
+- vagrant: add vagrant box support (f7accad)
+- command: support `vagrant package` command (39fb5a5)
+
+
+### Removed
+
+- Drop support for `utm_file_url` from provider config (4fb0ac0)
+- Remove support for importing utm files in zip format (c988671)
+
+
+
+## [0.0.1] (Pilot release) - 2024-08-08 
+
+* Initial release with all basic vagrant commands
+* Uses UTM file in zip format from a url as VM box to import

data/README.md

@@ -15,9 +15,7 @@ vagrant plugin install vagrant_utm
 
 ```ruby
 Vagrant.configure("2") do |config|
-  config.vm.provider :utm do |utm|
-    utm.utm_file_url = "https://github.com/naveenrajm7/utm-box/releases/download/debian-11/debian_vagrant_utm.zip"
-  end
+  config.vm.box = "utm/debian11"
 end
 ```
 

data/docs/_config.yml

@@ -2,12 +2,11 @@ title: Vagrant UTM
 description: >-
   vagrant_utm is a Vagrant plugin which adds UTM provider to Vagrant, 
   allowing Vagrant to control and provision machines via UTM's API
-baseurl: "/docs" # the subpath of your site, e.g. /blog
-# theme: just-the-docs
-
-url: "https://naveenrajm7.github.io/vagrant_utm"
+baseurl: "/vagrant_utm" # the subpath of your site, e.g. /blog
+url: "https://naveenrajm7.github.io" # the base hostname & protocol for your site, e.g. http://example.com
+repository: naveenrajm7/vagrant_utm # for github-metadata  
 github_username:  naveenrajm7
-repository: naveenrajm7/vagrant_utm
+
 
 # Build settings
 remote_theme: just-the-docs/just-the-docs@v0.8.2
@@ -73,4 +72,4 @@ back_to_top: true
 back_to_top_text: "Back to top"
 
 # Footer
-footer_content: "Copyright &copy; 2024 Naveenraj Muthuraj. Distributed by an <a href=\"https://github.com/naveenrajm7/vagrant_utm/tree/main/LICENSE.txt\">MIT license.</a>"
+footer_content: "Copyright &copy; 2024 Naveenraj Muthuraj. Distributed by an <a href=\"https://github.com/naveenrajm7/vagrant_utm/tree/main/LICENSE.txt\">MIT license.</a>"

data/docs/boxes/creating_utm_box.md

@@ -8,15 +8,23 @@ nav_order: 2
 
 As with [every Vagrant Provider](https://developer.hashicorp.com/vagrant/docs/providers/basic_usage), the Vagrant UTM provider has a custom box format that is required to work with Vagrant and the UTM plugin.
 
-{: .important }
-The UTM bundle (.utm file) is the box format for Vagrant UTM provider. 
-Because the current UTM API does not support importing utm file, we do not use vagrant box format (.box file).
-We currently use `utm://downloadVM?url=` to import VM to UTM.
+## UTM Vagrant box format
 
+UTM file (in macOS) is a directory containing Data/qcow2 (s), Data/efi_vars.fd and config.plist.
+Vagrant Box format will require additional metadata.json file. 
 
-{: .note }
-However, once UTM supports import, we should be able to package UTM files into box format and use the benefits of Vagrant boxes . For example, downloading the box once to spin up multiple VMs and using vagrant cloud to publish custom UTM boxes.
+Vagrant .box is a tar file
 
+The contents of a `utm/ubuntu-24.04` vagrant box.
+```bash
+$tar -tf ubuntu-24.04.box 
+Vagrantfile
+box.utm/Data/7FB247A3-DC9F-4A61-A123-0AEE1BEEC636.qcow2
+box.utm/Data/efi_vars.fd
+box.utm/config.plist
+box.utm/screenshot.png
+metadata.json
+```
 
 {: .warning } 
 This is a reasonably advanced topic that a beginning user of Vagrant does not need to understand. If you are just getting started with Vagrant, skip this and use an [available box](/utm_box_gallery.md). If you are an experienced user of Vagrant and want to create your own custom boxes, this is for you.
@@ -25,9 +33,16 @@ This is a reasonably advanced topic that a beginning user of Vagrant does not ne
 
 The virtual machine created in UTM can use any configuration you would like, but Vagrant has some hard requirements:
 
-* The second network interface (adapter 1 or index 1) must be a `Emulated VLAN` adapter. Vagrant uses this to connect the first time.
+* The first network interface (adapter 1 or index 0) must be `Shared Network`, which is recommended for new virtual machines. 
+
+We use 'Shared Network' as a NAT equivalent in Vagrant.
+
+* The second network interface (adapter 2 or index 1) must be a `Emulated VLAN` adapter. Vagrant uses this to connect the first time via forwarded ports.
+
+We use 'Emulated VLAN' to achieve port forwarding.
+
+
 
-* Use can use the first network interface (adapter 0 or index 0) to be `Shared Network`, which is recommended for new virtual machines. 
 
 Other than the above, you are free to customize the base virtual machine as you see fit.
 
@@ -46,25 +61,37 @@ Check the [UTM Guide on Guest Support](https://docs.getutm.app/guest-support/gue
 By satisfying the [general guidance on creating vagrant boxes](https://developer.hashicorp.com/vagrant/docs/boxes/base) and the above [Virtual Machine](#virtual-machine) requirements you can use your VM with Vagrant UTM plugin.
 
 Apart from manually building the boxes, you can also use the semi-automated way of building these boxes using [packer plugin for UTM](https://github.com/naveenrajm7/packer-plugin-utm).
-The packer plugin has a builder and a post processor, which uses an existing UTM file, adds Vagrant specific stuff and packs the UTM file as a zip so it can be used by UTM Vagrant plugin.
+The packer plugin has the following components:
+1. Builder
+  1. UTM - Use existing utm file 
+  2. ISO - Start from scratch using ISO files
+2. Post-processor
+  1. ZIP - Package UTM VM into zip file
+  2. Vagrant - Package UTM VM into vagrant box.
+
 
 Checkout [UTM Box Guide](https://github.com/naveenrajm7/utm-box/blob/main/HowToBuild/DebianUTM.md) to know how to build Box using packer.
 
-## Using your own UTM boxes
+## Using your own UTM VMs
+
+Do you have your own UTM VM that you would like to use with Vagrant 
 
-Due to the limitation of UTM API, the plugin can only take a url pointing to the zip file.
-So, you can use a local python server to host your UTM bundle in zip file
+1. Convert your utm file to box format
 
+    a. Make a directory  
+    b. Put utm vm file in it  
+    c. Tar the folder with .box extension
+
+2. Import the vagrant box 
 ```bash
-python3 -m http.server                                                                            
-Serving HTTP on :: port 8000 (http://[::]:8000/) ...
+vagrant box add --name custom/debian debian.box  
 ```
 
-Use in Vagrantfile
+3. Use in Vagrantfile
 ```ruby
 Vagrant.configure("2") do |config|
-  config.vm.provider :utm do |utm|
-    utm.utm_file_url = "http://localhost:8000/debian_vagrant_utm.zip"
-  end
+  config.vm.box = "custom/debian11"
 end
-```
+```
+
+You can also use [packer plugin for UTM](https://github.com/naveenrajm7/packer-plugin-utm) to build, package and publish your UTM VMs to HCP Vagrant registry and share it your teams or with the world.

data/docs/boxes/utm_box_gallery.md

@@ -1,117 +1,41 @@
 ---
-title: UTM box gallery
+title: UTM Vagrant box gallery
 # layout: default
 parent: UTM Box
 nav_order: 1
 ---
 
-# UTM Box Gallery
+# UTM Vagrant Box Gallery
 
 To work with Vagrant, a base VM (box) must have 
-[certain features](https://developer.hashicorp.com/vagrant/docs/boxes/base), like a ssh user for vagrant to connect.
+[certain features](https://developer.hashicorp.com/vagrant/docs/boxes/base), like an ssh user for vagrant to connect.
 
-To help you get started with Vagrant UTM provider, couple of pre-built VMs from the [UTM Gallery](https://mac.getutm.app/gallery/) are modified to work with Vagrant and are made available to use.
+To help you get started with Vagrant UTM provider, a couple of pre-built VMs that work with Vagrant and are published in [HCP Vagrant registry](https://portal.cloud.hashicorp.com/vagrant/discover/utm).
 
+{: .important}
+All the VMs provided are built from [UTM Gallery VMs](https://mac.getutm.app/gallery/) or ISO in an (semi) automated way using [packer plugin for UTM][packer plugin for UTM]. Please see the [UTM Box Guide][UTM Box Guide] on how these UTM Vagrant boxes were built using packer.
 
 * Debian 11 (Xfce):   
 ```ruby
-u.utm_file_url = https://github.com/naveenrajm7/utm-box/releases/download/debian-11/debian_vagrant_utm.zip 
+config.vm.box = "utm/debian11"
 ```
 
+* Ubuntu 24.04 :
+```ruby
+config.vm.box = "utm/ubuntu-24.04"
+```
+
+* Help build more boxes using [packer plugin for UTM][packer plugin for UTM]
 <!-- * ArchLinux ARM -->
 
 
 {: .new}
-To enable building reproducible and easily sharable UTM VM bundle a [packer plugin for UTM](https://github.com/naveenrajm7/packer-plugin-utm) has been developed.
-Please see the [UTM Box Guide](https://github.com/naveenrajm7/utm-box/blob/main/HowToBuild/DebianUTM.md) on how these UTM Vagrant boxes were built using packer.
-
-
-Check out [Creating UTM Box](/boxes/creating_utm_box.md) to build your own Vagrant compatible UTM box.
-
-## Corresponding VMs from UTM Gallery
-
-<div class="content">
-  <section class="gallery">
-      <!-- <div class="gallery-item">
-          <a href="{{ vm.url }}">
-              <h3>ArchLinux ARM</h3>
-              <h4><i class="fas fa-microchip"></i> ARM64 </h4>
-              <img src="{{ site.baseurl }}/assets/images/screens/archlinux-logo.png" alt="Screenshot" class="screenshot" />
-          </a>
-      </div> -->
-      <div class="gallery-item">
-        <a href="">
-            <h3>Debian 11 (Xfce)</h3>
-            <h4><i class="fas fa-microchip"></i> ARM64 </h4>
-            <img src="{{ site.baseurl }}/assets/images/screens/debian-11-xfce-arm64.png" alt="Screenshot" class="screenshot" />
-        </a>
-      </div>
-  </section>
-</div>
-
-<style>
-.gallery {
-  display: flex;
-  flex-flow: row wrap;
-  justify-content: center;
-  align-items: center;
-}
-
-.gallery .gallery-item {
-  padding: 5px;
-  width: 20em;
-}
-
-.gallery-item a {
-  text-decoration: none;
-  color: black;
-}
-
-.gallery h3, .gallery h4 {
-  text-align: center;
-  overflow: hidden;
-  text-overflow: ellipsis;
-  white-space: nowrap;
-}
-
-.gallery h3 {
-  font-size: 1.2em;
-}
-
-.gallery h4 {
-  margin: 10px 0 10px 0;
-  font-size: 0.8em;
-  font-weight: normal;
-}
+To enable building reproducible and easily sharable UTM VM bundle a [packer plugin for UTM][packer plugin for UTM] has been developed and open-sourced. 
 
-.gallery .image {
-  width: 20em;
-}
 
-.gallery .screenshot {
-  max-width: 100%;
-  height: auto;
-  display: block;
-  box-shadow: 0 1px 0 #ccc, 0 1px 0 1px #eee;
-  border-radius: 2px;
-  margin-left: auto;
-  margin-right: auto;
-  background: #DDD url('data:image/svg+xml,%3Csvg%20xmlns%3D%22http%3A%2F%2Fwww.w3.org%2F2000%2Fsvg%22%20width%3D%2244%22%20height%3D%2212%22%20viewBox%3D%220%200%2044%2012%22%3E%3Ccircle%20cx%3D%226%22%20cy%3D%226%22%20r%3D%224%22%20fill%3D%22%23eee%22%20%2F%3E%3Ccircle%20cx%3D%2222%22%20cy%3D%226%22%20r%3D%224%22%20fill%3D%22%23eee%22%20%2F%3E%3Ccircle%20cx%3D%2238%22%20cy%3D%226%22%20r%3D%224%22%20fill%3D%22%23eee%22%20%2F%3E%3C%2Fsvg%3E') 4px 4px no-repeat;
-  padding: 20px 0 0 0;
-  position: relative;
-}
 
-.gallery .placeholder {
-  padding-top: 75%;
-}
+Check out [Creating UTM Box](/creating_utm_box.md) to build your own compatible UTM Vagrant box.
 
-.gallery li {
-  padding: 5px 0 5px 0;
-}
 
-.gallery .button {
-  padding-bottom: 5px;
-  margin: 20px 0 20px 0;
-  font-size: 1.5em;
-}
-</style>
+[packer plugin for UTM]: https://github.com/naveenrajm7/packer-plugin-utm
+[UTM Box Guide]: https://github.com/naveenrajm7/utm-box/blob/main/HowToBuild/DebianUTM.md

data/docs/commands.md

@@ -9,7 +9,7 @@ nav_order: 2
 
 This page lists all the supported Vagrant commands which depend on the  UTM provider. Eg. `up`, `suspend`, `resume`, `halt`.
 
-Adds note to the command which are not yet available. Eg. `package`.
+Adds note to the command which are have some limitations. Eg. `snapshot`.
 
 The Vagrant commands that do not depend on provider are not listed and will continue to work. Eg. `global-status`
 
@@ -26,9 +26,7 @@ The Vagrant commands that do not depend on provider are not listed and will cont
 
 **Command: `vagrant box`**
 
-UTM provider uses .utm file as VM bundle .
-
-Box support is not yet available.
+UTM provider uses .utm file as VM bundle and supports box operations. 
 
 ## **Destroy**
 
@@ -46,9 +44,7 @@ Box support is not yet available.
 
 **Command: `vagrant package [name|id]`**
 
-Currently prompts to manually export (Share) the VM
-
-
+UTM 'Share' / export
 
 ## **Port**
 
@@ -70,7 +66,7 @@ Runs any configured [provisioners](https://developer.hashicorp.com/vagrant/docs
 
 **Command: `vagrant reload [name|id]`**
 
-The equivalent of running a [halt](https://developer.hashicorp.com/vagrant/docs/cli/halt) followed by an[up](https://developer.hashicorp.com/vagrant/docs/cli/up).
+The equivalent of running a [halt](https://developer.hashicorp.com/vagrant/docs/cli/halt) followed by an [up](https://developer.hashicorp.com/vagrant/docs/cli/up).
 
 
 
@@ -145,6 +141,14 @@ Import VM (if not created)
 
 These are the commands not available in vagrant but specific to UTM provider.
 
+## IP Address
+
+**Command: `vagrant ip-address [name|id]`**
+
+`utmctl ip-address`
+
+List all IP addresses associated with network interfaces on the guest.
+
 ## Disposable
 
 **Command: `vagrant disposable [name|id]`**

data/docs/configuration.md

@@ -17,10 +17,22 @@ config.vm.provider "utm" do |u|
 end
 ```
 
+## Checking for Guest Additions
+
+By default UTM plugin will check for the `qemu-guest-agent` when starting a machine, and will output a warning if the guest additions are not detected. You can skip the guest additions check by setting the check_guest_additions option:
+
+```ruby
+config.vm.provider "utm" do |u|
+  u.check_guest_additions = false
+end
+```
+
 ## Other customization
 
 ```ruby
 Vagrant.configure("2") do |config|
+  # Vagrant box 
+  config.vm.box = "utm/debian11"
   # Hostname inside the VM
   config.vm.hostname = "debian"
   # Ports to forward
@@ -29,13 +41,11 @@ Vagrant.configure("2") do |config|
   config.vm.provider "utm" do |u|
     # Name in UTM UI
     u.name = "debian"
-    # UTM VM file to import
-    u.utm_file_url = "http://localhost:8000/debian_vagrant_utm.zip"
     # CPU in cores
     u.cpus = 1
     # Memory in MB
     u.memory = 1024
-    # Notes for UTM VM (Appears in UI)
+    # Notes for UTM VM (Appears in UTM UI)
     u.notes = "Vagrant: For testing plugin development"
     # QEMU Directoy Share mode for the VM. 
     # Takes none, webDAV or virtFS

data/docs/features/synced_folders.md

@@ -13,8 +13,8 @@ After which the the host directory can be selected from UTM UI, and the guest di
 
 ```ruby
 Vagrant.configure("2") do |config|
+  config.vm.box = "utm/debian11"
   config.vm.provider :utm do |u|
-    u.utm_file_url = "http://localhost:8000/vm_utm.zip"
     # QEMU Directoy Share mode for the VM. 
     # Takes none, webDAV or virtFS
     u.directory_share_mode = "webDAV"

data/docs/index.md

@@ -18,10 +18,16 @@ allowing Vagrant to control and provision machines via UTM's API.
 
 ---
 
-[UTM] is a free, full featured system emulator and virtual machine host for iOS and macOS.
-The UTM provider currently supports UTM versions 4.5.x (except 4.5.0).
+{: .new}
+> UTM Vagrant plugin now supports [Vagrant boxes](https://developer.hashicorp.com/vagrant/docs/boxes)!   
+> Find UTM boxes at [HCP Vagrant registry](https://portal.cloud.hashicorp.com/vagrant/discover/utm). 
 
-[Vagrant] enables the creation and configuration of lightweight, reproducible, and portable development environments using Vagrantfile. The UTM provider plugin works with Vagrant version 2.4.1 .
+[UTM] is a free, full-featured system emulator and virtual machine host for iOS and macOS.  
+The UTM provider currently supports UTM versions 
+* 4.6.x   
+* 4.5.x (Obsolete, use plugin version 0.0.1)  
+
+[Vagrant] enables the creation and configuration of lightweight, reproducible, and portable development environments using Vagrantfile. The UTM provider plugin works with Vagrant version 2.4.1.
 
 
 Both UTM and Vagrant must be installed prior to using this plugin.
@@ -33,11 +39,11 @@ Browse the docs to learn more about how to use this plugin.
 
 ## Getting started
 
-Get started with Vagrant UTM plugin in 3 simple steps.  
+Get started with Vagrant UTM plugin in 2 simple steps.  
 Make sure both [Vagrant] and [UTM] are installed before your proceed.
 
-{: .warning}
-UTM Vagrant plugin is built around the existing UTM API. Some steps like Import, Snapshot are not straightforward. Please check [Known Issues](/known_issues.md) before using this plugin.
+{: .note}
+UTM Vagrant plugin is built around the existing UTM API. Some action like Snapshot are not straightforward. Please check [Known Issues](/known_issues.md) before using this plugin.
 
 
 ### Install
@@ -49,26 +55,34 @@ vagrant plugin install vagrant_utm
 
 ### Use
 
-Save the below config in your Vagrantfile. 
+#### Step 1
+Option 1: Create a Vagrantfile and initiate the box (OR)
+
+```
+vagrant init utm/debian11
+```
+
+Option 2: Open the Vagrantfile and replace the contents with the following
+
 ```ruby
 Vagrant.configure("2") do |config|
-  config.vm.provider :utm do |u|
-    u.utm_file_url = "https://github.com/naveenrajm7/utm-box/releases/download/debian-11/debian_vagrant_utm.zip"
-  end
+  config.vm.box = "utm/debian11"
 end
 ```
 
-### Run
+#### Step 2
+Bring up your virtual machine
 
-Bring up vagrant environment.
-```bash
+```
 vagrant up
 ```
 
+Now start using your machine!
 
+`vagrant ssh` to log into machine or forward ports to check your website or share folders and start developing.
 
 Check [Commands](commands.md) for all supported Vagrant commands.
-Check [Configuration](configuration.md) for more provider config options.
+Check [Configuration](configuration.md) for more UTM provider config options.
 
 
 ## About the project

data/docs/internals/utm_api.md

@@ -27,5 +27,4 @@ But, if we need to exchange complex data like json from UTM to plugin we use Jav
 All interactions with UTM should be possible with `utmctl` or `osascript`. But, due to the unavailablity of certain commands or features, we work around the issue by using direct shell command.  
 For Example:
 
-* Import `open -g utm://downloadVM?url=...` 
 * Snapshot `qemu-img snapshot ...`

data/docs/known_issues.md

@@ -8,14 +8,14 @@ nav_order: 7
 This plugin was built built around the existing UTM API.
 Hence there are things which are not ideal.
 
-1. vagrant up : Loads new VM by downloading zip file every time, and manually asks the user to confirm the download completion.   
-Draw back -  UTM does not support import API.
+1. ~~vagrant up : Loads new VM by downloading zip file every time, and manually asks the user to confirm the download completion.~~   
+~~Draw back -  UTM does not support import API.~~
 
-2. UUID : After importing VM , considers last VM in the list as the VM that was imported . So, if the intended VM is not last in the list , the plugin might customize other VM according to the Vagrantfile. 
-Draw back -  UTM import API should return UUID when imported.
+2. ~~UUID : After importing VM , considers last VM in the list as the VM that was imported . So, if the intended VM is not last in the list , the plugin might customize other VM according to the Vagrantfile.~~
+~~Draw back -  UTM import API should return UUID when imported.~~
 
-3. vagrant package: plugin just prints message to manually export the VM.
-Draw back -  UTM does not expose export API. (UTM already has 'Share')
+3. ~~vagrant package: plugin just prints message to manually export the VM.
+Draw back -  UTM does not expose export API. (UTM already has 'Share')~~
 
 4. Hide: Any plugin action will bring up the main UTM window. However, a properly built UTM box with no display will run headless.
 

data/lib/vagrant_utm/action/export.rb

@@ -3,19 +3,40 @@
 module VagrantPlugins
   module Utm
     module Action
-      # This action destroys the running machine.
+      # This action exports the virtual machine.
       class Export
         def initialize(app, _env)
           @app = app
         end
 
         def call(env)
-          # UTM 'Share' feature in UI will Export the virtual machine and all its data.
-          # Till 'Share' is exposed via API, show a message to manually export.
-          env[:ui].info I18n.t("vagrant_utm.actions.vm.export.manual_exporting",
-                               name: env[:machine].provider_config.name)
+          @env = env
+
+          raise Vagrant::Errors::VMPowerOffToPackage if \
+            @env[:machine].state.id != :stopped
+
+          export
+
           @app.call(env)
         end
+
+        def export
+          @env[:ui].info I18n.t("vagrant.actions.vm.export.exporting")
+          @env[:machine].provider.driver.export(utm_path) do |progress|
+            @env[:ui].rewriting do |ui|
+              ui.clear_line
+              ui.report_progress(progress.percent, 100, false)
+            end
+          end
+
+          # Clear the line a final time so the next data can appear
+          # alone on the line.
+          @env[:ui].clear_line
+        end
+
+        def utm_path
+          File.join(@env["export.temp_dir"], "box.utm")
+        end
       end
     end
   end

data/lib/vagrant_utm/action/import.rb

@@ -13,25 +13,35 @@ module VagrantPlugins
           import(env)
         end
 
-        def import(env)
-          machine = env[:machine]
-          config = machine.provider_config
-          driver = machine.provider.driver
-          utm_file_url = config.utm_file_url
+        def import(env) # rubocop:disable Metrics/AbcSize
+          env[:ui].info I18n.t("vagrant.actions.vm.import.importing",
+                               name: env[:machine].box.name)
 
-          env[:ui].info I18n.t("vagrant_utm.messages.importing_utm_file", name: utm_file_url)
+          # Import the virtual machine
+          utm_file = env[:machine].box.directory.join("box.utm").to_s
+          id = env[:machine].provider.driver.import(utm_file) do |progress|
+            env[:ui].rewriting do |ui|
+              ui.clear_line
+              ui.report_progress(progress, 100, false)
+            end
+          end
 
-          # Import the UTM VM file
-          driver.import(utm_file_url)
+          # Set the machine ID
+          env[:machine_id] = id
+          env[:machine].id = id unless env[:skip_machine]
 
-          # Set the UID of Vagrant machine to the UUID of the VM in UTM.
-          # UTM maintains UUID as primary key for VMs, but even the name works for all commands
-          # However, name is not unique.
+          # Clear the line one last time since the progress meter doesn't disappear
+          # immediately.
+          env[:ui].clear_line
 
-          # So we set the machine.id to UUID in next step after import.
-          # TODO: Set the machine.id to UUID after import returns the UUID (yet to be supported by UTM).
-          # machine.id = return value of import
+          # If we got interrupted, then the import could have been
+          # interrupted and its not a big deal. Just return out.
+          return if env[:interrupted]
 
+          # Flag as erroneous and return if import failed
+          raise Vagrant::Errors::VMImportFailure unless id
+
+          # Import completed successfully. Continue the chain
           @app.call(env)
         end