You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Rewrite of QEMU support internals. Much of the code to support QEMU has been refactored into a new project, QEMUKit, which will make it easier to support QEMU changes as well as support for new platforms. This means that v4.3.1 may contain a lot of UI bugs as testing is needed to make sure the new internals match up with the existing UI. Please help us by reporting any such issue you stumble upon.
TPM 2.0 and Secure Boot This is required for Windows 11 updates to 22H2. To enable TPM on an existing virtual machine (only x86_64, i386, and ARM64 architectures are supported), open the VM settings, go to the QEMU page and select "UEFI Boot", "TPM 2.0 Device", and "Reset UEFI Variables." Any new VM created through the wizard will have TPM 2.0 and Secure Boot enabled by default if Windows 10+ support is checked.
Changes (v4.3.2)
The last update introduced two units per bus for IDE devices. However, some machines do not support this configuration, so now two units per bus will only be enabled for supported machines. Other machines will retain pre v4.3.1 behaviour.
Fixed some state tracking issues leading to various errors when a VM is quickly stopped and started again.
Fixed debug logging not working due to backend changes in v4.3.1
Fixed a crash when QEMU tries to output non-printable characters
Add support for SWTPM for TPM 2.0 emulation
Add Secure Boot firmware for ARM64. Only the Secure Boot firmwares have TPM 2.0 support built in, so when TPM 2.0 and UEFI are enabled, UTM will automatically select the Secure Boot firmware. By default the UTM platform keys and Microsoft key exchange keys are enrolled. You can manually set up your own keys from the UEFI menu.
Updated the EDK2 UEFI firmware to the 202305 release
Debug logs will no longer be deleted when a VM configuration is saved and debug log is not disabled
Fixed an issue where the mouse cursor stopped working due to backend changes in v4.3.1
Machines with IDE interface (i44FX/PIIX) will now support two units per bus. Previously, we mapped IDE devices to one unit per bus. This means on some machines, the limit was two devices maximum. Now, we map two units per IDE bus which should increase the limit to four devices. Existing VMs will not get this change automatically in order to maintain compatibility. You can choose to opt-in to this new mapping by pressing the “Update Interface” button on each IDE drive in the VM settings. (Error when using more than two IDE devices on ISAPC - bootindex=2: Bus 'ide.2' not found #5358)
Localization: Updated Japanese (thanks @MMP0 and @studio1a9)
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Highlights
Changes (v4.3.2)
Changes (v4.3.1)
Changes (v4.3.0)
ucomiss
instruction causes a crash in some applications (Crash when executingucomiss
instructions emulating an x86-64 CPU on an AArch64 host #5294)delete
command (Delete VM through utmctl #5290)Issues
Please check the full list on Github and help report any bug you find that is not listed.
Installation
This discussion was created from the release v4.3.2 (Beta).
Beta Was this translation helpful? Give feedback.
All reactions