Utm для mac os

Utm для mac os

In the main window, press the “+” button on the top toolbar next to the title. You have the option to browse the gallery (recommended for new users) or to create a new VM from scratch. If you choose to create from scratch, most users do not need to change any options except from the Information tab, the System tab, and the Drives tab. All the other tabs are for more advanced use cases and the options should be set to the recommended default.

Information

When creating a new VM from scratch, you will see the same screen as when modifying an existing VM’s configuration. In the Information tab, you should give your VM a Name and optionally assign an icon to identify your VM by. The name must be unique as it is also the name of the .utm package which contains all data corresponding to this VM.

You can also write any Notes that will be displayed in the home screen when the VM is selected.

System

In the System tab, you can configure the Architecture, System, and Memory. The architecture is the CPU and determines what operating systems you can run. The most common architecture is x86_64, which is used by modern Intel and AMD processors (most PCs) and is used by most versions of Windows and Linux.

When you change the architecture to a well-known one, other settings will change to the default recommended settings so in most cases you do not have to manually change any of the other settings (except Memory and Drives).

The System drop-down lets you fine tune the emulated system to be a specific model or device. Most users should not have to change this from the default.

You should not assign more memory than the amount of physical RAM on your computer or you may experience slowdowns or even crashes. It is recommended that you assign no more than half the amount of physical RAM if you do not want to significantly affect the performance of your Mac.

Most users should not touch the Advanced Settings, but there you can fine tune parts of the emulation.

The QEMU tab is only for advanced use cases and for debugging emulation issues. You can choose to enable debug logging and to export the last debug log (created when the VM starts). You can also export the full QEMU command generated by UTM for the current configuration. If you choose to Bypass Configuration, then all other configuration options (including attached drives) will be ignored! This option should only be used for debugging.

Drives

You can create and mount virtual drives for the VM in the Drives tab. Import Drive will let you select a file to mount and New Drive will let you create either an empty removable drive or an empty hard drive.

If you wish to mount an ISO disk image, it is recommended that you create a New Drive and check Removable. You can then select the ISO image from the home screen or while the VM is running. If you choose to Import the ISO, then you cannot change the mounted disk image while the VM is running.

If you choose to Import Drive, it is recommended that you import a QCOW2 formatted drive image. Most other common disk image formats are compatible with QEMU but you will not be able to suspend a running VM when you have non-removable non-QCOW2 images mounted.

If you create a New Drive you can choose the Interface to attach the drive to. Most users can leave the default here as only advanced use cases require changing the interface.

The listed order of the drives are the same order exposed to QEMU which can affect boot order. You can re-order drives by using the arrow buttons.

Читайте также:  Windows driver stopped working

Display

The Display tab provides options to showing the VM’s output. Full Graphics emulates a display card while Console Only emulates a serial console. Full Graphics is not supported for all architectures and if it is not supported, it will be grayed out.

In Full Graphics, the Emulated Display Card will be set to be recommended default. Most users should not change this. The Scaling options control what hardware scalers are used when resizing the VM window. Most users should not change this.

In Console Only mode, you can change aspects of the terminal display. The Resize Console Command is a string that is sent to the serial input when the Resize button is pressed while the VM is running. The command is different depending on the guest operating system, but should be used to inform the OS that the console size has changed and to render UI elements accordingly. The default command should work in most Linux distributions.

Input

The Input tab gives the option for Legacy mode which should only be enabled for ancient operating systems (such as DOS) which does not support USB. Invert Mouse Scroll can be used to invert the emulated scroll wheel.

Network

If networking is unsupported by the emulated architecture, these options will be disabled. Advanced Options allow you to configure the guest network subnet and does not need to be used in most cases.

Port Forward lets you forward ports from the guest subnet to your local (host) machine.

Sound

If sound is unsupported by the emulated architecture, these options will be disabled. Emulated Audio Card should be set to the recommended default and can be changed for advanced use cases.

Sharing

If SPICE Guest Tools are installed in the guest OS, clipboard sharing and directory sharing can be used. If the tools are not installed, these features will not work even if enabled. The shared directory can be specified in the home screen.

Managing virtual machines

From the home screen, you can re-order the VM list by dragging the VM entry around. A secondary click on a VM will open a menu of options such as Delete, Clone, and Edit. You can also show the VM’s package location in Finder.

When a VM is selected, the top right toolbar provides similar operations.

To Start a VM, you can press the small play button on the right of the VM entry or the large play button when the VM is selected.

Using a virtual machine

Once started, there are a few buttons in the toolbar for controlling the virtual machine.

Power

Powers off the VM with a force power off.

Suspend

Only works if all non-removable drives are QCOW2 drive images AND the current VM is not virtualized (the guest and host architecture are the same). This allows you to save the state of the VM and the next time you start it, it will resume from this point instead of booting up fresh.

Restart

Force restarts the VM.

Capture Mouse

Not available in console mode. Fully captures mouse and keyboard input and redirects it to the VM. To exit this mode, press Control+Option key at once.

Resize

Only available in console mode. Sends the Resize Console Command configured in the Display tab of the settings screen. This allows you to notify the guest operating system that the console size changed and that UI can be rendered correctly.

Disk Image

Opens the disk image menu which allows you to change or eject the removable disk image. Only drives marked Removable (in Drives settings) support this.

Shared Directory

If Shared Directory is enabled (in Sharing settings) and the SPICE Guest Tools are installed in the guest operating system, this allows you to change the shared directory to be accessed in the guest.

UTM Preferences

You can access the preferences with Cmd+, or from the UTM menu. This allows you to change global emulation options including the option to disable virtualization (automatically enabled if the guest and host architecture are the same).

Источник

UTM Virtual Machines 4+

Yuan Lu

Снимки экрана

Описание

UTM uses the popular QEMU system emulator securely in a sandboxed environment to protect your data from viruses and malware in the emulated operating system.

Читайте также:  Gfwlivesetup exe windows 10 ошибка установки

Run Windows® 10 for ARM or Ubuntu® for ARM fully virtualized for maximum performance. Run Windows® 7 or any older Intel/AMD system emulated with decent performance.

Designed for macOS Big Sur using the latest and greatest Apple technologies, UTM is built from the ground up with the Mac in mind.

— Run ARM64 operating systems such as Windows® for ARM and Ubuntu® ARM on your Apple Silicon Mac fully virtualized at near native speeds (*virtualization only available for Apple Silicon Macs)
— Run Intel/AMD operating system such as Windows® 7, Windows® XP, Ubuntu® Linux, and more on your Apple Silicon Mac (*emulated with limited performance on Apple Silicon Macs, fully virtualized on Intel Macs)
— Over 30 processors can be emulated by the QEMU backend including i386, x64, ARM32, ARM64, MIPS, PPC, and RISC-V for developers and enthusiasts
— Supports macOS Sandbox to protect your data from any viruses or malware infecting the emulated operating system (such as Windows®)
— Attach USB devices to your virtual machine
— Experimental: GPU accelerated OpenGL on Linux VMs
— Bridged and shared networking support
— Don’t know how to use QEMU? Confused at all the options QEMU provides? UTM provides an easy to understand UI for managing and configuring VMs that does not require knowledge of QEMU command line arguments

We are working hard to provide new features. Below are some things currently missing from UTM. We hope to support at least some of these features in the future.

— No direct mounting of external disks and drives, only mounting disk images is supported
— No drag & drop of files and data, only copy paste of text is supported with tools installed

Что нового

## New Features
* (macOS 11.3+ Only) **Bridged networking and shared networking support**. You can configure it in the Network settings for your VM.
* (macOS 11+ and iOS 13+) **GPU acceleration for OpenGL on Linux**. Use `virtio-ramfb-gl` or `virtio-vga-gl` display device and compatible Linux drivers (most modern Linux distros will have it already installed). Windows is not supported because there is currently no virtio-gpu driver for Windows that supports 3D acceleration. Note that newly created VMs will default to a «GPU Supported» display device on supported architectures but existing VMs must manually change the display device in Display settings. GPU acceleration is still an experimental feature, so it may not work in some situations (including many 3D use cases).
* **EFI Boot**. By default new VMs created for pc, q35, and virt* machines will have EFI enabled. In previous versions, EFI is only enabled for virt* machines. Due to compatibility with boot, existing pc and q35 VMs will NOT have EFI enabled and must be manually turned on in Settings -> System -> Advanced Configuration -> UEFI Boot. This may also require you to re-install the bootloader on your VM. As part of this change, EFI variables will also be properly handled (on both ARM and x86 VMs). Note that if you’ve configured a custom pflash device for your VM, the new UEFI Boot option will take no effect (same as before).
* **QEMU v6.1.0** is now used for the backend.

## Changes
* Fix crash when setting custom VM icon (#2387) (thanks @ktprograms)
* Disable Port Forwarding feature for bridged networking (thanks @conath)
* Fixed memory leak (#2720)
* Fix layout issues in settings on macOS Monterey (#2644)
* Fix capturing of hotkeys (such as Cmd+Tab) (#2677)
* Disable port forwarding options for shared & bridged networking
* Refactored non-OpenGL rendering code, fixing some random crashes seen in TestFlight reports.
* Windows BSOD on boot/setup due to `PAGE_FAULT_IN_NONPAGED_AREA` (#2721)
* Settings no longer crash when an error occurs while saving a new VM

Оценки и отзывы

It’s great

But life without 3D acceleration is uncomfortable

Конфиденциальность приложения

Разработчик Yuan Lu указал, что в соответствии с политикой конфиденциальности приложения данные могут обрабатываться так, как описано ниже. Подробные сведения доступны в политике конфиденциальности разработчика.

Сбор данных не ведется

Разработчик не ведет сбор данных в этом приложении.

Конфиденциальные данные могут использоваться по-разному в зависимости от вашего возраста, используемых возможностей или других факторов. Подробнее

Информация

английский, корейский, традиционный китайский, упрощенный китайский

Источник

UTM Virtual Machines 4+

Run other operating systems

Yuan Lu

Screenshots

Description

UTM uses the popular QEMU system emulator securely in a sandboxed environment to protect your data from viruses and malware in the emulated operating system.

Читайте также:  Где находятся файлы загрузчика windows 10

Run Windows® 10 for ARM or Ubuntu® for ARM fully virtualized for maximum performance. Run Windows® 7 or any older Intel/AMD system emulated with decent performance.

Designed for macOS Big Sur using the latest and greatest Apple technologies, UTM is built from the ground up with the Mac in mind.

— Run ARM64 operating systems such as Windows® for ARM and Ubuntu® ARM on your Apple Silicon Mac fully virtualized at near native speeds (*virtualization only available for Apple Silicon Macs)
— Run Intel/AMD operating system such as Windows® 7, Windows® XP, Ubuntu® Linux, and more on your Apple Silicon Mac (*emulated with limited performance on Apple Silicon Macs, fully virtualized on Intel Macs)
— Over 30 processors can be emulated by the QEMU backend including i386, x64, ARM32, ARM64, MIPS, PPC, and RISC-V for developers and enthusiasts
— Supports macOS Sandbox to protect your data from any viruses or malware infecting the emulated operating system (such as Windows®)
— Attach USB devices to your virtual machine
— Experimental: GPU accelerated OpenGL on Linux VMs
— Bridged and shared networking support
— Don’t know how to use QEMU? Confused at all the options QEMU provides? UTM provides an easy to understand UI for managing and configuring VMs that does not require knowledge of QEMU command line arguments

We are working hard to provide new features. Below are some things currently missing from UTM. We hope to support at least some of these features in the future.

— No direct mounting of external disks and drives, only mounting disk images is supported
— No drag & drop of files and data, only copy paste of text is supported with tools installed

What’s New

## New Features
* (macOS 11.3+ Only) **Bridged networking and shared networking support**. You can configure it in the Network settings for your VM.
* (macOS 11+ and iOS 13+) **GPU acceleration for OpenGL on Linux**. Use `virtio-ramfb-gl` or `virtio-vga-gl` display device and compatible Linux drivers (most modern Linux distros will have it already installed). Windows is not supported because there is currently no virtio-gpu driver for Windows that supports 3D acceleration. Note that newly created VMs will default to a «GPU Supported» display device on supported architectures but existing VMs must manually change the display device in Display settings. GPU acceleration is still an experimental feature, so it may not work in some situations (including many 3D use cases).
* **EFI Boot**. By default new VMs created for pc, q35, and virt* machines will have EFI enabled. In previous versions, EFI is only enabled for virt* machines. Due to compatibility with boot, existing pc and q35 VMs will NOT have EFI enabled and must be manually turned on in Settings -> System -> Advanced Configuration -> UEFI Boot. This may also require you to re-install the bootloader on your VM. As part of this change, EFI variables will also be properly handled (on both ARM and x86 VMs). Note that if you’ve configured a custom pflash device for your VM, the new UEFI Boot option will take no effect (same as before).
* **QEMU v6.1.0** is now used for the backend.

## Changes
* Fix crash when setting custom VM icon (#2387) (thanks @ktprograms)
* Disable Port Forwarding feature for bridged networking (thanks @conath)
* Fixed memory leak (#2720)
* Fix layout issues in settings on macOS Monterey (#2644)
* Fix capturing of hotkeys (such as Cmd+Tab) (#2677)
* Disable port forwarding options for shared & bridged networking
* Refactored non-OpenGL rendering code, fixing some random crashes seen in TestFlight reports.
* Windows BSOD on boot/setup due to `PAGE_FAULT_IN_NONPAGED_AREA` (#2721)
* Settings no longer crash when an error occurs while saving a new VM

Ratings and Reviews

It’s great

But life without 3D acceleration is uncomfortable

App Privacy

The developer, Yuan Lu , indicated that the app’s privacy practices may include handling of data as described below. For more information, see the developer’s privacy policy.

Data Not Collected

The developer does not collect any data from this app.

Privacy practices may vary based on, for example, the features you use or your age. Learn More

Information

English, Korean, Simplified Chinese, Traditional Chinese

Источник

Оцените статью