UTM - Run Windows Virtual Machine on Mac

This blog is a step by step guide on how to run a Windows Virtual Machine on MacOS using UTM (Open Source Virtual Machine Tool). Also the settings needed to share Clipboard and Directory between Windows and MacOS.

Download and Install UTM application on MacOS from

https://mac.getutm.app/

Download Windows 11 iso file from Microsoft

https://www.microsoft.com/en-us/software-download/windows11

Download Windows Guest tool iso file

https://getutm.app/downloads/utm-guest-tools-latest.iso

Steps to create Windows 11 Virtual Machine

  1. Click Create a New Virtual Machine
  2. Click Virtualize
  3. Select Windows
  4. Set memory as 12288 MiB
  5. Set CPU Cores as 3
  6. Click Continue
  7. Tick Install Windows 10 or higher
  8. Click Browse and select Windows 11 iso file
  9. Tick Install drivers and SPICE tools
  10. Click Continue
  11. Set size at 64 GiB
  12. Click Continue
  13. Do not set Shared Directory Path now, we can do it after installation
  14. Click Continue
  15. Set Name as Windows
  16. Click Save

Steps to install Windows 11

  1. Click on Windows
  2. In first CD/DVD, select the Windows 11 iso file
  3. In second CD/DVD, select the utm-guest-tools iso file
  4. Click play button on Windows
  5. Press Enter key immediately to boot to boot from CD (iso) image
  6. Set Language to install as English (United Kingdom)
  7. Set Time and currenty format as English (United Kingdom)
  8. Click Next
  9. Set Keyboard as United Kingdom
  10. Click Next
  11. Enter Product key if you have Windows 11 key. This is optional as Windows 11 Home edition can work without license. However there will be some restriction on personalisation and customisation. It is legal and allowed to use Windows 11 without license key as long as only one Windows virtual machine is installed in the UTM per Macbook.
  12. Click I don't have a product key
  13. Select Windows 11 Home
  14. Click Next
  15. Click Accept
  16. Select Disk 0 Unallocated Space
  17. Click Next
  18. Wait for the installation to complete and restart
  19. During restart, do not press any key, otherwise it will once again boot from CD (iso)
  20. Wait for further installation to complete
  21. Wait for the restart
  22. Select country as United Kingdom and click Yes
  23. Select keyboard as United Kingdom and click Yes
  24. At second keyboard, click Skip
  25. Wait for restart
  26. Enter name as windows and click Next
  27. Enter a password and click Next
  28. Enter same password for confirmation and click Next
  29. Set security questions 1 to 3 and click Next
  30. Wait for the windows update to complete and wait for it to install the updates

Steps to install Windows Guest tool

This steps enables better screen resolution, clipboard sharing and directory sharing between MacOS (Host) and Windows 11 (Guest)

  1. Click the Windows screen
  2. Enter the password and click ->
  3. Open File Explorer
  4. Click CD Drive UTM Guest Tools
  5. Double click utm-guest-tools-*.exe file
  6. Finish the setup wizard
  7. Turn off Windows

Setup shared directory

  1. Turn off Windows
  2. Right click Windows and Select Edit
  3. Click Sharing
  4. Tick Enable Clipboard Sharing
  5. Select Directory Share Mode as SPICE WebDAV
  6. Click Browse and choose any directory on MacBook eg: Downloads
  7. Click Save
  8. Click play button on Windows

Access shared directory in File Explorer

Files Explorer -> This PC -> Spice client (Y:)

If Spice client (Y:) is not available, then do the following one off setup to mount SPICE webdav directory.

  1. Open Files Explorer
  2. Navigate to C:\Program Files\SPICE webdavd directory
  3. Double click map-drive.bat

Access the shared directory in Terminal

Start Menu -> Terminal -> Y:

Comments

Post a Comment

Popular posts from this blog

Export/Backup Ollama Model

The following commands help to export/backup the ollama models which allows to quick restore the models or setup an offline machine using file transfer. Pull a model from registry ollama pull llava:7b Export the model mkdir -p llava_7b_backup cd llava_7b_backup ollama show --modelfile llava:7b > Modelfile cat Modelfile | grep -E '^FROM' | cut -d ' ' -f 2 | xargs -I {} cp {} . cat Modelfile | grep '# FROM' | cut -d ' ' -f 3 | xargs -I {} echo 'ollama create {} -f Modelfile' > readme.txt sed -i '' -E 's/^FROM.*blobs/FROM ./g' Modelfile Import the model  cd llava_7b_backup ollama create llava:7b -f Modelfile Run the model ollama run llava:7b Remove the model ollama rm llava:7b
Read more

JSON with curl and jq

This blog post captures some quick commands to deal with JSON from servers (Http APIs) using curl and jq command line tools About Jq: https://stedolan.github.io/jq/ Install jq: Mac: brew install jq Ubuntu or Debian: sudo apt-get install jq Sample JSON content: Assume the following JSON content will be returned from  URL http://api.example.com/some-json-content {     "user_name": "User 123",     "some_other_field": {         "sub_field": "sub_value"     },     "array_field": [         {             "field1": "value1",             "field2": "value2"         },         {             "field1": "value3",             "field2": "value4"         }     ] } UR...
Read more

Import self signed in Linux for Chrome / Chromium headless testing

Chrome / Chromium browser offers headless mode, which is quite useful to run tests via Selenium WebDriver in CI servers. However under some circumstance your test will hit a server with self signed certificate or invalid certificate or expired certificate. This may happen for developers trying to write tests against a server started on localhost with self signed certificates or testers trying to write tests against non-production servers with expired certificates (invalid certificates). Chrome / Chromium browser ignores the SSL errors when running in non-headless mode. However in CI servers, then it should be running in headless mode and currently we cannot ignore the SSL errors for tests accessing non-localhost websites. This blogs explains the steps for import a certificate into Linux's trust store, which will make the Chrome / Chromium browser to trust the self signed certificate.  Please do not apply these steps in production servers as it will make server vulnerable to ...
Read more