Error after moving VM files (new location of VM files not be correctly updated)

[ericaslakson]

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
After creating an instance of Ubuntu 22.04 from your arm64 isos, I installed it on my internal SSD. I was loading a very large database into PostgreSQL so I moved the VM files to an external drive (2TB m.2 nvme). After verifying functionality from the external drive my database loads continued dying. So I expanded the VM size in your gui. Then I verified functionality again but database loads still died. Then after noticing my external drive was not big enough anyway I moved VM files to another external larger drive (4TB), simply copying the VM files to the new drive and disconnected the original external drive. Then bringing up UTM said the VM files were missing, so attached original external drive and saved VM files to new external drive from inside UTM GUI. Then disconnected original external drive and brought up UTM ubuntu but database loads kept dying. Then I noticed the os had not expanded to fill the extra space I'd created in the VM. So I took advice from this link https://siytek.com/increase-utm-virtual-machine-disk-size/ and ran resize2fs method for Debian (note might be good to highlight this step somewhere in your documentation). After resize2fs I could see a larger size of '/' in ubuntu. I continued loading but then VM crashed with error shown here 'crash error.png'. I note in the UTM config screen that UTM lists the location of the VM files on the original external drive 'wrong path.png'. I believe that there is something wrong with UTM regarding path of VM not being updated when moving from one external drive to another external drive.

Any suggestions for recovering this VM?

Thx,

Eric
config.plist.zip

Configuration

• UTM Version: Version 4.6.3 (106)
• macOS Version: Sonoma 14.6.1
• Mac Chip (Intel, M1, ...): M1 Pro

Crash log
If the app crashed, you need a crash log. To get your crash log, open Console.app, go to Crash Reports, and find the latest entry for either UTM, QEMU, QEMUHelper, or qemu-*. Right click and choose Reveal in Finder. Attach the report here. None

Debug log
debug.log

For all issues related to running a VM, including crashes, you should attach a debug log. (This is unavailable for macOS-on-macOS VMs. Attach an excerpt of your system log instead.)
To get the Debug log: open UTM, and open the settings for the VM you wish to launch. Near the top of the QEMU page is Debug Log. Turn it on and save the VM. After you experience the issue, open the VM settings again and select Export Log... and attach it here.
debug.log

Upload VM
If your issue is related to a specific VM, please upload the config.plist from your VM's .utm directory. To get this, right-click the VM in UTM and choose "Show in Finder". Then right-click the selected file in Finder and choose "Show Package Contents". The config.plist file is now visible. Right-click it and choose "Compress". Attach the resulting config.plist.zip file here.
You can upload the entire .utm if needed, but note this includes your VM's drive image and may contain personal data. Since Github has an attachment size limit, you may want to upload to another service such as Google Drive. Link it here.
config.plist.zip

[osy]

You don't appear to have any screenshots attached. Also I don't see a crash log attached either. Your debug.log looks fine.

When you move a VM to a new drive outside of UTM's GUI, you can just double click it at the new location to open it in UTM. Then you can delete the original shortcut.