utmapp / utmapp/UTM

VirtioFS Mount Error: "Numerical result out of range" on M4 Mac (Apple Virtualization)

Open
#7,680 2 comments 4 reactions 0 assignees View on GitHub
Dominant language
Swift
Stars
35.5k
Forks
1.8k
Avg merge
5d 5h
Merged PRs (30d)
7

Description

Environment

UTM Version: 4.7.5 (118)

macOS Version: 26.4.1 (25E253)

Mac Chip: M4 (MacBook Air)

Guest OS: Debian GNU/Linux 13 (trixie)

Guest Kernel: Linux 6.12.74+deb13+1-arm64

Virtualization Backend: Apple Virtualization (not QEMU)

Description

When attempting to mount a shared directory via VirtioFS on a clean install of Debian 13 on M4 hardware, the mount succeeds at the command line but becomes inaccessible in the guest. Any attempt to access the mount point results in a "Numerical result out of range" error (ERANGE).

Steps to Reproduce

Create a new VM using Apple Virtualization.

Install Debian 13 (ARM64) with LVM (no encryption).

Configure a shared directory in UTM with the tag share.

Inside the guest, install virtiofsd and attempt to mount:
sudo mount -t virtiofs share /home/user/Public

Attempt to list files or open the directory in GNOME Files (Nautilus).

Expected Behavior

The directory should be readable and show files.

Actual Behavior

Terminal Error: ls: cannot access '/home/user/Public': Numerical result out of range

GUI Error: Error when getting information for file "/home/user/Public": Numerical result out of range

Diagnostic Logs

dmesg output shows that the driver is active but rejecting specific mount options like DAX, and potentially struggling with 64-bit inode mapping from the M4 host:

Plaintext
[ 1742.659654] virtio-fs: dax can't be enabled as filesystem device does not support it.
[ 2037.853780] virtio-fs: dax can't be enabled as filesystem device does not support it.
Additional Context

I have verified that virtiofsd is installed in the guest at /usr/libexec/virtiofsd.

Changing the tag names and re-adding the share does not resolve the "Out of range" error.

The issue appears related to Issue #7677, but specifically manifests as an ERANGE error on the new M4 storage controller/chipset.

Using a RAW/ASIF disk image via the USB interface works fine, suggesting the issue is isolated to the virtiofs communication layer between macOS and the 6.12 kernel.

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.