I'm not using Mojave yet, High Sierra and haven't upgraded. The disk (OWC 1Tb SSD) is formatted macOSX Extended (Journaled) (CoreStorage Logical Volume). I cannot comment WRT parallels V13, Mojave and APFS.
Seeing this thread is over 2 years old and just upgraded to Mojave (and APFS) - could it be related entirely to APFS?
Maybe parallels snapshot file structure is a very bad combination with APFS? but was ok with HFS+?
So I don't think so given my setup. I've been working through with Parallels tech support for several weeks now. And this is the sort of things that has been happening, see below (you don't have to read it all, you get the gist). We are at the point where I have bulk deleted all snapshots, taken a single snapshot, Disk Space Reclaim, turned on TRIM (although I am a bit sceptical about any performance degradation) and turned on smart guard. I will attempt to delete some snapshots this week to serif (after all that) it takes a long time and send a system report to parallels:
This ticket has been created in the Seconline support queue in order to coninue the ivnestigation of the issue you've reported on the Parallels forum:
https://forum.parallels.com/threads/snapshot-deletion-painfully-slow.341337/page-2#post-844149
The Engineering team already started the investigation based on the forum thread outlined above and to continue with it we need additional technical information from your side.
Just for the confirmation, the steps to reproduce the issue are as follows am I right?
1. Start Parallels Desktop, then launch Windows 10 virtual machine.
2. Manually start deleting a snapshot/a snapshot is being deleted by the SmartGuard feature. For both cases the process takes around two hours.
Additionaly, it would be great in you provide us with aswers to the following questions:
1. If you manually deleting a snapshot and it takes two hours is it a manually or SmartGuard created snapshot? Or there is no difference which snapshots to delete?
2. According to the already provided technical report there were two virtual machines running on the host at the same time. Both of them have SmartGuard feature enabled? If only one virtual machine is running, the process take the same amount of time?
3. If you attempt to delete a snapshot on stopped virtual machine, the time of the operation would be the same as on the running one or not?
To colect the technical data for the Engineering team do the following, please:
1. Open Parallels Desktop preferences (Right-click on Parallels Desktop icon in Dock > Preferences... or || icon in the top menu bar > Preferences).
2. Switch to the Advanced tab.
3. Enable "Use detailed log messages" option.
4. Start deleting a snapshot and after a period of time collect system-wide spindump (for the sake of the investigation it would be better to have at least a couple of them, the more the better):
- Launch Terminal ( Finder > Applications > Utilities > Terminal).
- Execute the following command:
sudo spindump
NOTE: No symbols will be shown due to security measures, so just hit the keys and use return/Enter.
-Wait until you receive the following output: Spindump analysis written to file /tmp/spindump.txt
5. Archive the files and attach it to your reply.
6. In addition to the spindumps, to analyze product processes and possibly find the source of the slowness of the snapshot deleting process we need a couple of technical reports collected during the process. To collect technical report: Click on || icon in the top menu bar > Help > Send Technical Data...
Best regards,
Ivan,
Just for the confirmation, the steps to reproduce the issue are as follows am I right?1. Start Parallels Desktop, then launch Windows 10 virtual machine. 2. Manually start deleting a snapshot/a snapshot is being deleted by the SmartGuard feature. For both cases the process takes around two hours.
Correct, it doesn't matter whether I am deleting manually or via smart guard it takes a very long time. The problem is/was you cannot schedule smart guard and because I started it around 1300, it would delete the snapshot in the middle of my working day. I know I can set the alarm for 3:00 am and get up and start it then, but that seems excessive.
Additionally, it would be great in you provide us with aswers to the following questions:
1. If you manually deleting a snapshot and it takes two hours is it a manually or SmartGuard created snapshot? Or there is no difference which snapshots to delete?
No difference as far as I recall.
2. According to the already provided technical report there were two virtual machines running on the host at the same time. Both of them have SmartGuard feature enabled? If only one virtual machine is running, the process take the same amount of time?
I have no idea. The second machine is no longer used (only to recover some data), the first machine was a clone of that machine. I recall having the same issue with that VM, but it's not used. It was coincidence if it was running when I created the log files.
3. If you attempt to delete a snapshot on stopped virtual machine, the time of the operation would be the same as on the running one or not?
I will need to try it (and I'm running out of snapshots to delete AND they are further up the snapshot chain, ie. closer to the actual VM). I'm deleting a non-smartguard snapshot with the VM NOT running.
After 15 minutes, about 10% and the progress bar doesn't seem to be moving at all.
In addition to the spindumps, to analyze product processes and possibly find the source of the slowness of the snapshot deleting process we need a couple of technical reports collected during the process. To collect technical report: Click on || icon in the top menu bar > Help > Send Technical Data...
First at the 20 minute mark (image not showing, but about 10%). I didn't enable Use detailed log messages and cannot STOP the snapshot deletion (which is going to take at least a couple of hours). I cannot see how to abort the snapshot deletion and I need to get some work done. I'll probably need to recover the PVM with time machine and try this deletion overnight.
And after several towing and froing:
Please clarify the following points:
1. According to the logs, there is com.paragon-software.lvm-for-mac kernel extension loaded on the Mac side and it's possible that its presence could affect the creation/deletion speed of snapshots.
Please check the behaviour when the com.paragon-software.lvm-for-mac kernel extension is unloaded.
The software was removed . KEXT files might be hanging around and did not get removed when the paragon software (Trial only) was trashed.
1. Launch Terminal ( Applications > Utilities > Terminal) 2. Execute the following command:
sudo kextunload -b com.paragon-software.lvm-for-mac
They have been physically deleted.
2. When the last time First Aid tool of Disk Utility has been used? If it wasn't used in a while, please perform it.
Recently, so that should not be a problem, but i have rerun it and everything coms up OK.
3. According to the first technical report the creation of the snapshot has taken around 40 minutes. Kindly collect a couple of spindumps during the creation of a snapshot next time.
Snapshot creation isn't an issue, as bad as deleting snapshots. It gets to the end of the progress bar in a minute and sits there for a while, but the total process takes only a few minutes (unlike delete).
Additionally, in you last email you've mentioned: "The delete took well over 1 hour, I went to bed after an hour and it was at 44%." I may presume that you're referring to the snapshot deletion, am I right?
Yes, that's the problem, not
creating snapshots.
And as the last part, perform the command you've used for testing with one addition, the second file name shouldn't be the same, e.g. "copy_Windows 10.iso". According to the previously provided command, the Windows 10.iso file has been copied into itself, e.g. time cp "Windows 10.iso" "copyWindows10.iso"
No, that was not the case: Windows10.iso was copied to Windows (SPACE) 10.iso.
Then:
While we were waiting for an update from your side I have had another discussion regarding your case with the Engineering team and I've received the following recommendation which could help to increase the speed of deleting snapshots.
Since you're developing inside the virtual machine and presumably compiling projects and due to the fact that TRIM isn't enabled in the virtual machine settings as a result with a high possibility, there are a lot of free information blocks being created as a result of compilations thus increasing the size of the virtual disk. E.g. the size of the disk is 100GBs and the actual information is only for 30 GBs there the rest are free blocks there were the files before/after compilations.
The recommendations are as follows:
1. Create a backup of the virtual machine and shut it down.
2. Merge all snapshots using the Terminal command:
prl_disk_tool merge --hdd /Users/kevin/Virtual\ Machines/Parallels/Parallels\ Windows\ 10 Guest\ Development\ XE10\ Community.pvm/Windows\ 10-0.hdd
If the command won't work, copy paste the first part of it as is 'prl_disk_tool merge --hdd' (without quotes) then add space and using Finder go to the folder /Users/kevin/Virtual Machines/Parallels/ then right-click on the virtual machine file > Show Package Contents, then drag and drop hdd file into the Terminal window.
3. Then perform disk space reclaim: In the Parallels Desktop Control Center press cogwheel button near the name of the virtual machine or right-click on the name > Configure
On the General tab perform reclaim and wait until the process is finished.
4. Then switch to the Hardware tab > Hard Disk and expand Advanced Settings drop-down menu and enable 'Enable TRIM' option.
5. Create a snapshot on a stopped virtual machine and then continue using SmartGuard feature.
Once you had time please follow these recommendations and reply us back with the results.
And now:
Thank you for waiting. I can confirm that we've received your last reply.
About the pictures you've seen in Manage Snapshots window, they were leftovers of the merge process. Merge command has merged available snapshots and left their thumbnails and descriptions. I'm sorry, I've missed that part in the previous email.
Frankly speaking, it's quite strange that you've received a notification what the virtual machine isn't located on the SSD drive although it's located on it.
This situation also worth sending to the Engineering team for investigation.
For that purpose we need a fresh technical report collected on the running virtual machine, this would be enough for this part of the investigation.
Additionally, a fresh technical report will contain all timings of the operations you've performed following our suggestions.
Regarding your request about the SmartGuard scheduler, I've added it to the existing feature request and informed the Engineering team.
Moreover we would like to hear the results of snapshots removal created by SmartGuard feature from you after performing our suggestions.
We're looking forward to hear from you soon. If we won't hear from you around the middle for the week we'll send you a short follow-up email.
Kevin