Skip to content
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.

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

debian vm data changes not save in normal mode (not disposable mode) #5025

Closed
uprprc777 opened this issue Feb 15, 2023 · 1 comment
Closed
Milestone

Comments

@uprprc777
Copy link

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

  • UTM Version: 4.1.5
  • macOS Version: 13.2
  • Mac Chip : M1 (MacBook Pro 13-inch 2020)

Crash log
No crash.

Debug log

Running:  -L /Applications/UTM.app/Contents/Resources/qemu -S -spice "unix=on,addr=/Users/***REDACTED***/Library/Group Containers/WDNLXAD4W8.com.utmapp.UTM/50E3C36F-DB24-4814-AB4E-246A487A70ED.spice,disable-ticketing=on,image-compression=off,playback-compression=off,streaming-video=off,gl=on" -chardev spiceport,id=org.qemu.monitor.qmp,name=org.qemu.monitor.qmp.0 -mon chardev=org.qemu.monitor.qmp,mode=control -nodefaults -vga none -device virtio-net-pci,mac=9A:8F:F5:55:03:5B,netdev=net0 -netdev vmnet-bridged,id=net0,ifname=en0 -device virtio-ramfb-gl -cpu host -smp cpus=4,sockets=1,cores=4,threads=1 -machine virt -accel hvf -drive if=pflash,format=raw,unit=0,file=/Applications/UTM.app/Contents/Resources/qemu/edk2-aarch64-code.fd,readonly=on -drive if=pflash,unit=1,file=/Users/***REDACTED***/VMGUEST/Debian.utm/Data/efi_vars.fd -m 4096 -device intel-hda -device hda-duplex -device nec-usb-xhci,id=usb-bus -device usb-tablet,bus=usb-bus.0 -device usb-mouse,bus=usb-bus.0 -device usb-kbd,bus=usb-bus.0 -device qemu-xhci,id=usb-controller-0 -chardev spicevmc,name=usbredir,id=usbredirchardev0 -device usb-redir,chardev=usbredirchardev0,id=usbredirdev0,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev1 -device usb-redir,chardev=usbredirchardev1,id=usbredirdev1,bus=usb-controller-0.0 -chardev spicevmc,name=usbredir,id=usbredirchardev2 -device usb-redir,chardev=usbredirchardev2,id=usbredirdev2,bus=usb-controller-0.0 -device usb-storage,drive=drive1A5AFD8C-F683-4049-8AF0-66D69E3785B2,removable=true,bootindex=0,bus=usb-bus.0 -drive if=none,media=cdrom,id=drive1A5AFD8C-F683-4049-8AF0-66D69E3785B2,readonly=on -device virtio-blk-pci,drive=drive0E0B1A3E-D03D-46FF-BDEA-5E94D3EBF56A,bootindex=1 -drive if=none,media=disk,id=drive0E0B1A3E-D03D-46FF-BDEA-5E94D3EBF56A,file=/Users/***REDACTED***/VMGUEST/Debian.utm/Data/0E0B1A3E-D03D-46FF-BDEA-5E94D3EBF56A.qcow2,discard=unmap,detect-zeroes=unmap -device virtio-serial -device virtserialport,chardev=vdagent,name=com.redhat.spice.0 -chardev spicevmc,id=vdagent,debug=0,name=vdagent -name Debian -snapshot -uuid 50E3C36F-DB24-4814-AB4E-246A487A70ED -device virtio-rng-pci
qemu-aarch64-softmmu: warning: Spice: playback:0 (0x15b016940): setsockopt failed, Operation not supported on socket
qemu-aarch64-softmmu: warning: Spice: record:0 (0x15b0169e0): setsockopt failed, Operation not supported on socket
gl_version 30 - es profile enabled
WARNING: running without ARB/KHR robustness in place may crash

Upload VM
I have tried to create multiple linux (debian) VMs. And all of them have the same issues.

@rawtaz
Copy link

rawtaz commented Feb 25, 2023

@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.

@osy osy added this to the v4.2 milestone Feb 26, 2023
@osy osy closed this as completed in 8de800f Mar 4, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants