Virtual machines are currently unable to boot when configured with 'Bridged' network mode on systems equipped with the new Apple M5 Pro chip. This problem has been identified using UTM virtualization software, specifically version 4.7.5 (118).
The issue manifests as the VM sitting on the loading screen immediately after attempting to start, without crashing. Debug logs are not generated due to the failure occurring before the system reaches that point. The problem was replicated using ubuntu-24.04.4-live-server-arm64.iso.
While 'Bridged' mode is non-functional, VMs successfully boot when the network mode is set to 'Host Only' or 'Extended'. This indicates the problem is specific to the 'Bridged' networking implementation on the M5 Pro architecture within the current UTM version.
This limitation affects developers and users who rely on bridged networking for their virtualized environments on the latest Apple M5 Pro hardware. It necessitates using alternative network configurations or awaiting a fix from UTM or macOS to restore full functionality.
✨ This summary was generated by AI from the outlets' reporting listed below. It is not independently verified and may contain errors — check the original sources. How BrevFeed works →
One email each morning: the day's tech stories, clustered across outlets and summarized. No account needed.
One email a day. Unsubscribe in one click, any time.
Spend a few minutes, get the whole day. Every topic's top stories in one hands-free rundown — listen, watch, or read the transcript.
▶ Play today's briefNew every morning, and the back catalogue is archived by date.
Virtual machines running on Apple M5 Pro machines using UTM version 4.7.5 cannot boot when the network mode is set to 'Bridged'. This issue prevents users from utilizing a common network configuration for their VMs on the new hardware.