UTM Failed to lock byte 100 when starting with external disk image on SMB share

BEFORE SUBMITTING YOUR ISSUE, PLEASE LOOK AT THE PINNED ISSUES AND USE THE SEARCH FUNCTION TO MAKE SURE IT IS NOT ALREADY REPORTED. ALWAYS COMMENT ON AN EXISTING ISSUE INSTEAD OF MAKING A NEW ONE.

Describe the issue
I have an external USB drive added. The disk image file is stored on a samba share from my home server. When I start the VM, it immediately shows the error mentioned. There is a patch that may fix the issue when turning of file locking here: https://github.com/qemu/qemu/commit/eb43ea16dcb7e6ab01db321b5edac3e593556e7d If you do use this patch, how can I turn locking off as they mention?

Configuration

UTM Version: 4.1.1
macOS Version: 13.5.2
Mac Chip (Intel, M1, ...): M1

Crash log
No crash

Debug log
debug.log

Upload VM
config.plist.zip

Sep 30 '23 12:09 phirestalker

Turns out this is definitely about the file being on a samba share. I copied the file to a local external disk and the error does not happen.

Oct 02 '23 23:10 phirestalker

This issue happens to me as well on macOS; not only on SMB shares, but also on NFS shares. The error is shown below: Screenshot 2023-11-20 at 7 42 43 PM

However, this issue only appears on UTM versions 4.4 and above. I ran the same VMs on UTM v4.3.5 over SMB with no such issue.

My system configuration is as follows: UTM: v4.4.3 macOS: Sonoma 14.1.1 Chip: Apple M2

Nov 20 '23 15:11 lvek4096

This issue happens to me as well on macOS; not only on SMB shares, but also on NFS shares. The error is shown below:

However, this issue only appears on UTM versions 4.4 and above. I ran the same VMs on UTM v4.3.5 over SMB with no such issue.

My system configuration is as follows: UTM: v4.4.3 macOS: Sonoma 14.1.1 Chip: Apple M2

Did you find a fix? I am having same problem...

Nov 23 '23 11:11 simplyAwizard

This issue happens to me as well on macOS; not only on SMB shares, but also on NFS shares. The error is shown below: However, this issue only appears on UTM versions 4.4 and above. I ran the same VMs on UTM v4.3.5 over SMB with no such issue. My system configuration is as follows: UTM: v4.4.3 macOS: Sonoma 14.1.1 Chip: Apple M2

Did you find a fix? I am having same problem...

No luck... The issue still persists and I am unable to find a fix for it.

Nov 24 '23 20:11 lvek4096

FWIW: I encountered this issue on a Mac that did not have the latest update installed (Sonoma 14.2.1). Updating to the latest OS managed to resolve the issue.

Mac OS: 14.2.1 UTM: 4.4.5 Mac Chip: M2

I am using QEMU 7.2 ARM Virtual Machine to run Ubuntu 20.04.6 for a robotics class.

Jan 05 '24 00:01 maason-kao

FWIW: I encountered this issue on a Mac that did not have the latest update installed (Sonoma 14.2.1). Updating to the latest OS managed to resolve the issue.

Still happening for me in macOS Sonoma 14.2.1:

macOS: Sonoma 14.2.1 chip: Apple M2 Max UTM: 4.4.5 VM: Windows 11 QEMU 7.2 ARM

Error: QEMU error: QEMU exited from an error: qemu-aarch64-softmmu: -drive if=none,media=cdrom,id=drive5C178731-7D35-4F6F-B05B-3D22044D7C44,file=/[PATH/TO/WINDOWS_ISO/ON/SMB-MOUNTED/VOLUME],readonly=on: Failed to lock byte 100: Operation not supported

The error is only happening in this VM. I have another Linux VM that works fine.

Jan 05 '24 16:01 rushimusmaximus

To resolve the QEMU error while installing Kali Linux on my Mac M1 using UTM, I created and used a local disk image instead of the direct ISO file. This method successfully bypassed the error and allowed a smooth installation. (Create a New Disk Image)

Jan 07 '24 08:01 dogukansahil

I met same issue "Failed to lock byte 100" on mac when I try install Windows 10 via Win10_22H2_Chinese_Simplified_x64v1.iso. Then I right clicked the iso image file in finder, and chose open menu option to try magic authorize, and luckily it helps.

Jan 31 '24 02:01 caltonzhou

This issue happens to me as well on macOS; not only on SMB shares, but also on NFS shares. The error is shown below: However, this issue only appears on UTM versions 4.4 and above. I ran the same VMs on UTM v4.3.5 over SMB with no such issue. My system configuration is as follows: UTM: v4.4.3 macOS: Sonoma 14.1.1 Chip: Apple M2

Did you find a fix? I am having same problem...

No luck... The issue still persists and I am unable to find a fix for it.

you can fix that by ejecting the CD/DVD

Feb 09 '24 11:02 CelineHarakee

Ejecting ISO Image from desktop worked for me. The problem dissapeared.

Mar 10 '24 14:03 Yulian302

Ejecting the ISO from the Mac Desktop was indeed the successful action! thanks!

Apr 20 '24 20:04 mark88008

you can fix that by ejecting the CD/DVD

Ejecting worked well!!!! Thanks so much!

May 07 '24 12:05 mercy-holdiness

I didn't mount the image, but still got the error. I needed the iso image to boot, so I converted it:

hdiutil convert ./ubuntu-24.04-live-server-arm64.iso -format UDRW -o ./ubuntu-24.04.img
mv ./ubuntu-24.04.img.dmg ./ubuntu-24.04.img

and then mount it as Disk Image:

That worked for me.

May 22 '24 10:05 mietzen

I resolved the same issue by moving the .iso file to desktop.

Jun 02 '24 05:06 alireza-abolhasani

Ejecting .iso image helped 👍

Jun 02 '24 19:06 filippofilip95

I didn't mount the image, but still got the error. I needed the iso image to boot, so I converted it:
hdiutil convert ./ubuntu-24.04-live-server-arm64.iso -format UDRW -o ./ubuntu-24.04.img
mv ./ubuntu-24.04.img.dmg ./ubuntu-24.04.img

It worked in the end, but I got the below error. So in case someone runs into it, here is the solution:

$ hdiutil convert ./hoge.iso -format UDRW -o ./hoge.img
hdiutil: convert failed Resource Temporarily Unavailable error
$ hdiutil attach ./hoge.iso

If you get any errors after executing attach, restart your computer.

Jun 29 '24 07:06 a-ide

I moved the .iso out of the iCloud shared/cloud space and this stopped the issue.

Jul 11 '24 15:07 simontheu