You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the issue*
For Linux (Debian) VM, data changes cannot be saved in normal mode, once disposable mode is used (of course, after exiting the disposable mode and return to normal mode).
Based on the log, I noticed that even I have exited the disposable mode, the qemu parameter still have the disable-ticketing=on. This is the possible reason for this issue.
The parameter should be removed once disposable mode is close but it doesen't. I have checked almost everything in the GUI but found nothing I can adjust for and related to this problem.
@uprprc777 I have the exact same problem/symptoms with UTM 4.1.5 (74) on macOS Monterey. I have done extensive testing and can reproduce this 100%. The VM I am using is a Windows 10 Insider Preview, but that probably doesn't matter.
I have found one single workaround, and that is to shut down and restart UTM. After that, if I start the VM in normal (non-disposable) mode it persists changes I make in it. Can you verify that this workaround works for you too?
PS: We should add that when the VM runs in this incorrectly "disposable mode", UTM does not display "Disposable mode" in the with title.
Describe the issue*
For Linux (Debian) VM, data changes cannot be saved in normal mode, once disposable mode is used (of course, after exiting the disposable mode and return to normal mode).
Based on the log, I noticed that even I have exited the disposable mode, the qemu parameter still have the
disable-ticketing=on
. This is the possible reason for this issue.The parameter should be removed once disposable mode is close but it doesen't. I have checked almost everything in the GUI but found nothing I can adjust for and related to this problem.
Configuration
Crash log
No crash.
Debug log
Upload VM
I have tried to create multiple linux (debian) VMs. And all of them have the same issues.
The text was updated successfully, but these errors were encountered: