UTM icon indicating copy to clipboard operation
UTM copied to clipboard

VM disk size shows different values between main window and config pane

Open LostInCompilation opened this issue 3 years ago • 10 comments

Describe the issue EDIT: See comment down below for better screenshots and reported size by Finder.

After compressing a VM disk, the size of the disk is displayed differently between the main window and the VM's config windows. This is the first time I encountered this issue, it is the only VM where this error happens (Windows 11 ARM VM). Restarting UTM doesn't help.

Configuration

  • UTM Version: 4.0.9 (68)
  • macOS Version: macOS 13.0.1
  • Mac Chip: M1 Pro
Screenshot 2022-11-29 at 02 04 28

LostInCompilation avatar Nov 29 '22 01:11 LostInCompilation

Update: The drift gets bigger each time I use the VM. Currently the options dialog still shows about 19GB, while the preview pane is now at 30GB.

LostInCompilation avatar Dec 14 '22 22:12 LostInCompilation

It now happened with another VM (Debian).

LostInCompilation avatar Jan 06 '23 01:01 LostInCompilation

A bit more info: The size shown in the VM settings window is always a smaller one than the size shown in the UTM main window. The actual file size of the UTM file in Finder is the same as displayed in the UTM main window and is the bigger value of the two. I always click "Compress" when I'm done with the VM, so I think this only happens when using the compress feature.

LostInCompilation avatar Jan 06 '23 04:01 LostInCompilation

For better documentation, here are better screenshots and the actual size reported by Finder (from #5241). Those are just two examples, every VM has this inconsistency.

First VM (Finder shows 47.46GB)

234083932-dfba90b7-d56c-4e16-a23a-2bdd164de1a8 234083950-8c4a02f1-ea95-49af-aba9-6fd8ee895804

Second VM (Finder shows 3.32GB)

234084653-811725f7-5088-4ae4-b925-bd56f530ae12 234084663-590628c7-f6e3-411d-98c2-c31c52cb0b25

LostInCompilation avatar Apr 24 '23 18:04 LostInCompilation

An example QEMU Linux arm64 VM: (these are all from the same VM)

  • when I created it, UTM asked for drive "Size", I chose 20 GB
  • UTM: Edit VM / VirtIO Drive / "Size": 3.57 GB
  • UTM VM info shows "Size": 7.42 GB
  • Finder / Get Info / Size (on Disk): 6.77 GB
  • (Finder "Size" of the .utm: 8.22 GB)

(this is just one example, every "Size" is different in every VM)

rxhfcy avatar Sep 09 '23 19:09 rxhfcy

Update: The drift gets bigger each time I use the VM. Currently the options dialog still shows about 19GB, while the preview pane is now at 30GB.

@LostInCompilation can you check if you have a huge efi_vars.fd file inside the .utm package too?

(select the VM, Show in Finder, Show Package contents, inside "Data": send a screen shot of Finder showing the contents)

rxhfcy avatar Sep 12 '23 16:09 rxhfcy

@LostInCompilation can you check if you have a huge efi_vars.fd file inside the .utm package too?

(select the VM, Show in Finder, Show Package contents, inside "Data": send a screen shot of Finder showing the contents)

@LostInCompilation ...and can you also report the "size on disk" of efi_vars.fd (right click, Get Info, Size (on Disk)?

rxhfcy avatar Sep 13 '23 14:09 rxhfcy

@LostInCompilation can you check if you have a huge efi_vars.fd file inside the .utm package too?

(select the VM, Show in Finder, Show Package contents, inside "Data": send a screen shot of Finder showing the contents)

For those VM's where different sizes get reported between main and config window I have a big efi_vars.fd too.

Whats interesting is, that the difference in size reported by the two windows inside UTM is exactly the size of efi_vars.fd.

LostInCompilation avatar Sep 13 '23 19:09 LostInCompilation

I am experiencing the same issue. In addition, the guest's disk size does not match what I allocated.

  • Disk Size 50 GB image

  • Size in settings is different. : 19GB image

  • The efi_vars.fd file differs in size between system boot and power off 665KB vs 20GB, respectively.

image

Experiencing the storage issue since this is happening

jauharvp avatar Dec 04 '23 04:12 jauharvp

Still no solution? this makes the app virtually unusable

EDIT: are you sure u don't auto reclaim/compress the space after saving, when the disk is created, seems to be the issue and explains why the base disk is 16/40 gb and the new ones empty

desgraci avatar Apr 28 '24 16:04 desgraci