Network Unreachable for ports.ubuntu.com and cannot connect to snap store in UTM Ubuntu VM

[Shvetang]

Describe the issue

Facing this error when trying to test the mirror location on UTM trying to virtualize the ubuntu 24.04.1 live server for ARM (mirror location does not work)

Notes:
The host macOS has a stable internet connection.
The issue persists across multiple tries of building the and different mirror locations
Check out the window of the message

Ign:3 http://ports.ubuntu.com/ubuntu-ports noble-backports InRelease
Err:1 http://ports.ubuntu.com/ubuntu-ports noble InRelease
  Cannot initiate the connection to ports.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable)
  Cannot initiate the connection to ports.ubuntu.com:80 (2620:2d:4000:1::16). - connect (101: Network is unreachable)
  Could not connect to ports.ubuntu.com:80 (185.125.190.36), connection timed out
  Could not connect to ports.ubuntu.com:80 (185.125.190.39), connection timed out
E: Failed to fetch http://ports.ubuntu.com/ubuntu-ports/dists/noble/InRelease
  Cannot initiate the connection to ports.ubuntu.com:80 (2620:2d:4000:1::19). - connect (101: Network is unreachable)

Another problem is that it is unable to connect to the snap store so it is unable to download Firefox and thunderbird, etc

Configuration

• UTM Version: 4.6.3(106)

• macOS Version: Sequoia 15.1.1

• Mac Chip (Intel, M1, ...): M1

[camilla37]

I had a very similar issue while trying to run Linux with QEMU backend and MacOS with Apple Virtualization backend at the same time. In fact, when I am running MacOS with Apple Virtualization, sometimes I cannot even start a VM with Linux with QEMU backend because it cannot create a virual network interface for the QEMU VM.

Can you try running your Ubuntu VM alone without any other VMs open to see if your error persists?

[Shvetang]

This is actually the only VM I have at the moment
Also, this persists across different wifi connections all of which work perfectly well

[osy]

Hi, please provide config.plist and/or debug.log as indicated in the issue template when you filed the issue. We cannot triage without even the most basic info such as if this is virtualization or emulation and what architecture if it is emulation.