8000 QEMU error: QEMU exited from an error: Is another process using the image · Issue #5830 · utmapp/UTM · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

QEMU error: QEMU exited from an error: Is another process using the image #5830

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
DanMelbourne opened this issue Oct 25, 2023 · 1 comment
Closed

QEMU error: QEMU exited from an error: Is another process using the image #5830

DanMelbourne opened this issue Oct 25, 2023 · 1 comment
Milestone
v4.5

Comments

@DanMelbourne
Copy link
DanMelbourne commented Oct 25, 2023 •
edited
Loading

Describe the issue
After upgrading from 4.4.2 to 4.4.3 I have been unable to reopen my VM due to this error message. Has persisted with upgrade to UTM Version 4.4.4 (92) as well.

QEMU error: QEMU exited from an error: Is another process using the image [/Users/dan/Library/Containers/com.utmapp.UTM/Data/Documents/Home Assistant OS.utm/Data/haos_generic-aarch64-11.0.qcow2]?

I've rebooted the Mac so it can't be a stray process. Must be something in the VM file itself or in UTM's settings. Is there some kind of lock file for VMs I can delete?

Configuration

  • UTM Version: 4.4.4 (92)
  • macOS Version: Sonoma 14.0
  • Mac Chip (Intel, M1, ...): M1

Debug log
This seems to be the relevant part of the debug log...

(qemu-aarch64-softmmu:40149): Spice-DEBUG: 09:30:42.776: ../server/char-device.c:797:red_char_device_start: char device 0x1418c83a0
qemu-aarch64-softmmu: -drive if=none,media=disk,id=driveB6F8F7D3-30C7-484A-9858-8D861F34C600,file=/Users/dan/Library/Containers/com.utmapp.UTM/Data/Documents/Home Assistant OS.utm/Data/haos_generic-aarch64-11.0.qcow2,discard=unmap,detect-zeroes=unmap: Failed to get "write" lock
Is another process using the image [/Users/dan/Library/Containers/com.utmapp.UTM/Data/Documents/Home Assistant OS.utm/Data/haos_generic-aarch64-11.0.qcow2]?

Here's the full debug.log: debug.log

Upload VM

Here's the config.plist config.plist.zip
@mitsukiyouko555
Copy link
mitsukiyouko555 commented Dec 25, 2023 •
edited
Loading

I'm getting the same issue.. any luck with this so far? @DanMelbourne

I noticed this issue after the latest sonoma update.. it was working fine before :(

Chip: Apple M1 Pro
MacOS: Sonoma 14.2.1 (23C71)

I've tried uninstalling and reinstalling UTM twice, rebooted, tried to open both my windows and my Kali linux VM and both are having this error (including a backup that i downloaded from my dropbox) so I know it is not the vms themselves that have the issue.

I would imagine this is something within the UTM core app...

2023-12-24_19-09

Aside from that, UTM the app, takes like a min or two to open from when i clicked on it - much slower than usual.

At one point, 2 UTM's showed up in my dock even though I only opened one. I suspect there is a second one running in the bg that I can't see and that's making it think that there's another thing opening the file..

I also ran into this error: "UI error: Could not connect: Connection refused".

Interestingly, as I am typing this, the windows vm now works, but I'm still getting both of the above issues with my Kali.

image

Debug Log:
UTM Debug Log.txt

Op.. the issue is back for my windows vm too :(

@osy osy added this to the v4.5 milestone Feb 26, 2024
@osy osy closed this as completed in 1a42cc1 Mar 28, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
v4.5
Development

No branches or pull requests
3 participants
@mitsukiyouko555 @DanMelbourne @osy
0